System hang problem
Devendra Gupta
I am using Fedora 11 (2.6.29.6-217.2.3.fc11.x86_64) , Sometime when I boot system it get hanged at login screen, nothing works except power button. I have discussed this problem in IRC also but could not find solution. All this started after fedora 11 installation, fedora 10 was fine. Sometimes when I restart system after hang I get a message kernel oops occurred. My system hangs while starting blender also. I have Dell Inspiron 1525 laptop. I have made copies of some system file after recent system hang, I don't know to interpret these files now so I have attached them. If you find some solution for my problem please help me.
--
Thanks & Regards
Devendra Kumar Gupta
Sharad Birmiwal
> Hello Friends!
> I am using Fedora 11 (2.6.29.6-217.2.3.fc11.x86_64)
> , Sometime when I boot system it get hanged at login screen, nothing works
> except power button. I have discussed this problem in IRC also but could not
Does the capslock button also not work when your system freezes? Have
you tried using vesa video driver? Try that and see if your system
locks up or not.
Also, what is the kernel oops message you get when you reboot?
SB
Sharad Birmiwal
> you tried using vesa video driver? Try that and see if your system
> locks up or not.
No wait. You seem to be using vesa driver only? Can you attach the
output of glxinfo when you have X running?
Sharad Birmiwal
You are using "intel" video driver. Try using "vesa" instead.
SB
Devendra Gupta
Thanks & Regards
Devendra Kumar Gupta
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCS d- s: a-- C++@>$ UBL*@>$ P+>+ L+++@>+++$ E>-- !W++@>++$ !N o? K-- w>$ O-- !M !V PS PE Y PGP>--$ !t 5 !X !R tv b DI D G>$ e>$ h-- r- y++@
------END GEEK CODE BLOCK------
Sharad Birmiwal
> Caps lock is also not working, actually when system hangs caps lock
> indicator start blinking, even alt+ctrl+f1 (or f2, f3...), ctrl+alt+del also
I was under the impression earlier that there might be some problem
with the video driver, especially 'cause it is triggered often when
you boot your system. But when you say that your caps lock indicator
blinks, that means there is most likely a kernel panic at that point.
Steps I'd suggest are checking your RAM for faults (use Ubuntu's CD?
it has memcheck), hard-disk for errors (run badblocks? but that's
unlikely and can be easily traced in your system logs which I'm too
lazy to check), may be some other system fault?
I know you'll argue that everything was fine with FC10 but I'll
suggest that you eliminate this possibility.
SB
Devendra Gupta
I was under the impression earlier that there might be some problem
On Thu, Aug 13, 2009 at 4:19 PM, Devendra Gupta<dev2...@gmail.com> wrote:
> Caps lock is also not working, actually when system hangs caps lock
> indicator start blinking, even alt+ctrl+f1 (or f2, f3...), ctrl+alt+del also
with the video driver, especially 'cause it is triggered often when
you boot your system. But when you say that your caps lock indicator
blinks, that means there is most likely a kernel panic at that point.
Steps I'd suggest are checking your RAM for faults (use Ubuntu's CD?
it has memcheck), hard-disk for errors (run badblocks? but that's
unlikely and can be easily traced in your system logs which I'm too
lazy to check), may be some other system fault?
I have already done memtest through live Ubuntu cd and there was no error. I haven't run badblocks, Actually I don't know about this test but I am going to do it after googling it. I have also tried reinstalling the fedora 11 completely but nothing happened then I migrated to 64 bit fedora 11 but still no progress.
I know you'll argue that everything was fine with FC10 but I'll
suggest that you eliminate this possibility.
Yes there is no need to argue about fedora 10.
SB
Sharad Birmiwal
> completely but nothing happened then I migrated to 64 bit fedora 11 but
> still no progress.
badblocks checks for bad blocks on your hard disk. Run it from a live
cd environment (without mounting your harddrive) as
$ badblocks /dev/hda
It takes a lot of time and it will only print block # of bad blocks?
(remember to replace /dev/hda with your hard drive).
Since you have spent the energy trying 64 bit FC 11, might I suggest
reverting back to FC10 to simply make sure that it's not a hardware
problem?
Sharad
Devendra Gupta
badblocks checks for bad blocks on your hard disk. Run it from a live
> to do it after googling it. I have also tried reinstalling the fedora 11
> completely but nothing happened then I migrated to 64 bit fedora 11 but
> still no progress.
cd environment (without mounting your harddrive) as
$ badblocks /dev/hda
Thanks, I have sda device so I need to run #badblocks /dev/sda , as I read some switches in the man pages like s,v,n so can I run #badblocks -nvs /dev/sda ?
It takes a lot of time and it will only print block # of bad blocks?
(remember to replace /dev/hda with your hard drive).
Since you have spent the energy trying 64 bit FC 11, might I suggest
reverting back to FC10 to simply make sure that it's not a hardware
problem?
OK , if the problem persists I'll do this.
Sharad
Sharad Birmiwal
> some switches in the man pages like s,v,n so can I run #badblocks -nvs
> /dev/sda ?
Sure. I've had two hdd replacements before and I simply used badblocks
to check for errors. The switches seem fine (you should know what -n
does though).
BTW, I am just guessing there might be a problem with your hdd. Your
logs don't really indicate anything to that effect though. Did you
have an ext4 filesystem with FC10 as well?
SB
Sharad Birmiwal
9051:Aug 10 19:16:46 localhost kernel: ------------[ cut here ]------------
9052-Aug 10 19:16:46 localhost kernel: kernel BUG at
drivers/gpu/drm/i915/i915_gem.c:2241!
9053-Aug 10 19:16:46 localhost kernel: invalid opcode: 0000 [#1] SMP
9054-Aug 10 19:16:46 localhost kernel: last sysfs file:
/sys/devices/virtual/rfkill/rfkill0/state
9055-Aug 10 19:16:46 localhost kernel: CPU 0
Looks like a case of problem with video driver (i915). Try using
"vesa" that should fix your problem but that would mean you haven't
have 3D acceleration.
Sharad
Devendra Gupta
Sure. I've had two hdd replacements before and I simply used badblocks
> Thanks, I have sda device so I need to run #badblocks /dev/sda , as I read
> some switches in the man pages like s,v,n so can I run #badblocks -nvs
> /dev/sda ?
to check for errors. The switches seem fine (you should know what -n
does though).
I am doing partition wise checking means I run #badblocks -nvs /dev/sda1 and after this next sda2 and so on , because when I run #badblocks -nvs /dev/sda the o/p was
root@bt:~# badblocks -nvs /dev/sda
/dev/sda is apparently in use by the system; it's not safe to run badblocks!
please tell me why this error come, I havn't mounted any partitions and running the test through live backtrack CD.
currenty its scanning sda2.
BTW, I am just guessing there might be a problem with your hdd. Your
logs don't really indicate anything to that effect though. Did you
have an ext4 filesystem with FC10 as well?
SB
--
Thanks & Regards
Devendra Kumar Gupta
Devendra Gupta
yes, there may be some problem with video driver because when I run 3D application like blender system hangs but this hang is different , it don't show the fedora screen and don't blink capslock too.
How to use "vesa" , so vesa dont have 3D acceleration?
Sharad
Sharad Birmiwal
> root@bt:~# badblocks -nvs /dev/sda
> /dev/sda is apparently in use by the system; it's not safe to run badblocks!
That's probably because the live CD environment enables swap. Disable
it with swapoff and try again, i.e., if you now really want to check
your hdd for errors.
SB
Sharad Birmiwal
> application like blender system hangs but this hang is different , it don't
> show the fedora screen and don't blink capslock too.
> How to use "vesa" , so vesa dont have 3D acceleration?
You will have to google for this but you need to create xorg.conf in
/etc/X11 which is the config file for your X11 server. You can say
there which video driver to use. vesa is a generic one which works on
all(?) hardware but provides no acceleration.
These days, when X server starts, it autodetects your hardware (mouse,
keyboard, monitor, videocard) and loads the appropriate modules
automatically but if xorg.conf exists in /etc/X11, the server uses
that file.
SB
Devendra Gupta
yes I am unmounting swap.
SB
Devendra Gupta
You will have to google for this but you need to create xorg.conf in
> yes, there may be some problem with video driver because when I run 3D
> application like blender system hangs but this hang is different , it don't
> show the fedora screen and don't blink capslock too.
> How to use "vesa" , so vesa dont have 3D acceleration?
/etc/X11 which is the config file for your X11 server. You can say
there which video driver to use. vesa is a generic one which works on
all(?) hardware but provides no acceleration.
I am googling about this and I have completed the badblocks test , there was no bad block found. Now I need to use the vesa driver. I have already collected some information from IRC and surfing. Your guidance was very well and informative and I thank you again. T
These days, when X server starts, it autodetects your hardware (mouse,
keyboard, monitor, videocard) and loads the appropriate modules
automatically but if xorg.conf exists in /etc/X11, the server uses
that file.
SB
--
Thanks & Regards
Devendra Kumar Gupta
Devendra Gupta
I have selected vesa driver through GUI utility in system > administration > display , This utility has made a backup file and updated /etc/X11/xorg.conf . After rebooting the system it hanged again before gdm screen . This time I could not see the gdm even after rebooting several times. So I logged in through single usermode by passing 1 as a parameter in the kernel line. After doing this I have restored the /etc/X11/xorg.conf file through the backup file made by the above utility. Now I can see the GUI log in screen and system continues to hang randomly during boot process.. I also tried the tips written in some fedora docs to find similar problem and added myself in the cc list of the similar bugs in Bugzilla too.
I have tried https://fedoraproject.org/wiki/Common_F11_bugs#intel-misc-gfx
I will share the further information about this problem, When I was in OSSCamp some of my friends suggested me to leave fedora and use ubuntu . They were saying that its not compatible with dell laptop. But I'll try to go in the deep of this problem till the solution.
Sharad
Sharad Birmiwal
SB
Devendra Gupta
Can you attach the working xorg.conf file please?
It is attached.
SB