PDA

View Full Version : Fedora crashing randomly



dgrafix
25th May 2008, 02:08 PM
I have a problem on one of my laptops. the mouse curser starts moving really slowly/jumpy and the pc grinds to a halt.

-Have got plenty of ram (700+mb)
-no hdd activity during this
-Cannot ctrl-alt-f1 to re-login & kill whatever it is,
-seems to happen when codeblocks is running but cannot confirm this.

Never crashed a linux 100% before, have always been able to ctrl-alt-f1 and kill off the offender

Any ideas what could cause this?

bradlongo
25th May 2008, 03:19 PM
I've never heard of ctrl-alt-f1 but you can use ps -A to see all the programs/processes currently running. Try using kill [process #] or killall [process name] to 'kill the offender.' Also killall -v will tell you if the signal was sent sucessfully. Although its not in the man pages someone once told me killall -9 [process] means die now and it stops it hard.

In addition what is in /var/log, and what does dmesg give you?

rehcla
25th May 2008, 08:24 PM
Hi dgrafix!

I have the same behavior of Fedora 9 on one of my laptops...
Particular it is an Acer Aspire 5020 with an ATI Radeon 700 Mobility!
On my main Thinkpad Z61m Fedora 9 runs flawlessly!

So could you give us more explicit information about your hardware???

Greetings,

rehcla

mbokil
25th May 2008, 10:19 PM
I've never heard of ctrl-alt-f1
This command will bring you to terminal shell screen. You can then run ps -ef | grep <my_process> to find it and kill it with kill -9 <process_id>. You can then return to your former screen by pressing Alt+F7.

Linux, as in the OS, is probably not crashing but X.org video server. Ctrl+Alt+BackSpace will also restart X Server. I have had X Server crash on Fedora 9 several times. I think version 1.5 has more memory leaks. If you watch X Server it will increase in size to around 75 MB. The older X didn't do this.

rehcla
25th May 2008, 11:57 PM
Hi mbokil!

Changing to a console via crt+alt+F* or restart the Xserver via crt+alt+Backspace is not possible because the system is not responding...
All I can do is cold reset the Laptop!
Tomorrow I will ssh into the Aspire and investigate further!

Greetins,

rehcla

ebelog
26th May 2008, 12:25 AM
So you can connect to the laptop with an SSH session even when it's otherwise frozen?

Running top should tell you if there are any processes using up all of the memory or CPU, and you can hopefully kill them off in the ssh session.

Think about the software that you most recently installed. Try disabling or uninstalling the programs one at a time to see if you can find one that may be causing an issue with your X windows session.

mbokil
26th May 2008, 12:36 AM
Rehcla, I think your crashing problem is a genuine kernel panic with Fedora 9. I haven't seen it happen in a long time, but today my Fedora 9 box locked up and X couldn't even be restarted. I was in the middle of converting a directory of wav files into mp3 using Lame encoder. I tried it three times and both times Fedora 9 locked up. I will have to submit a stack track to kernel.org.

dgrafix
26th May 2008, 08:39 AM
I've never heard of ctrl-alt-f1 but you can use ps -A to see all the programs/processes currently running. it gives you a text based login to allow you to ps -e kill any apps that are chewing up the xserver. However in this case nothing is possible.

I have the same problem as rehcla.
Nothing works, ctrl+alt+BS, crtl+alt+F1. Mouse chuggs around the screen as if the cpu/kernel are busy and then eventually freezes too.


Rehcla, I think your crashing problem is a genuine kernel panic with Fedora 9 A genuine kernel crash! Never had one on linux before, in 3 years of use! Hope this is not a sign of things to come :eek:

edit: one interesting thing i noticed, Rehcla mentioned a mobility 700 mine is also a radeon mobility M6 or 300 i think, using the free driver and is running with direct rendering (fglrx wont work, the card is quite an old one)

rehcla
26th May 2008, 02:10 PM
dgrafix wrote:

I have a problem on one of my laptops. the mouse curser starts moving really slowly/jumpy...

So I went into the Acer via ssh and found the folling regarding the touchpad:


kernel: psmouse.c: TouchPad at isa0060/serio4/input0 lost synchronization, throwing 2 bytes away.
kernel: psmouse.c: TouchPad at isa0060/serio4/input0 lost synchronization, throwing 2 bytes away.
kernel: psmouse.c: TouchPad at isa0060/serio4/input0 lost synchronization, throwing 4 bytes away.
kernel: psmouse.c: TouchPad at isa0060/serio4/input0 lost synchronization, throwing 1 bytes away.
kernel: psmouse.c: TouchPad at isa0060/serio4/input0 lost synchronization, throwing 3 bytes away.
kernel: psmouse.c: TouchPad at isa0060/serio4/input0 lost synchronization, throwing 3 bytes away.
kernel: psmouse.c: TouchPad at isa0060/serio4/input0 lost synchronization, throwing 3 bytes away.
kernel: psmouse.c: TouchPad at isa0060/serio4/input0 lost synchronization, throwing 3 bytes away.
kernel: psmouse.c: TouchPad at isa0060/serio4/input0 lost synchronization, throwing 3 bytes away.
kernel: psmouse.c: TouchPad at isa0060/serio4/input0 lost synchronization, throwing 4 bytes away.
kernel: psmouse.c: TouchPad at isa0060/serio4/input0 lost synchronization, throwing 4 bytes away.
kernel: psmouse.c: TouchPad at isa0060/serio4/input0 lost synchronization, throwing 3 bytes away.
kernel: psmouse.c: TouchPad at isa0060/serio4/input0 lost synchronization, throwing 2 bytes away.

So now we know why the mouse cursor behaves like that!

Bug submitted:
https://bugzilla.redhat.com/show_bug.cgi?id=448400

rehcla

dgrafix
27th May 2008, 10:15 AM
Hmm, thats probably not good either.

However, in my case its a complete kernel lockout. Nothing works, not the keyboard, emergency terminal (ctrl+alt+f1) nothing.

dbrenner
27th May 2008, 11:16 PM
I am having the same or very similar problem. Cursor moves slow, cntl+alt+bkspc and cntrl_alt+F1
not responding. Hold power button until laptop turns off is the only way to get it back.
ATI Radeon Mobility M6 LY graphics. Dell Latitude C610.
Xorg radeon driver.

What I found:
The hang only happens after the Xserver is started the 2nd time.
I discovered I could boot single and then init 5 and the Xserver did not hang.
When booting directly to run level 5 rhgb (red hat graphical boot) starts the Xserver during boot.
The Xserver is then shutdown and restarted for user login. (2nd time Xserver is started)

I edited the grub.conf file and removed the rhgb reference.
Now the system boots to level 5 (without rhgb) and starts X. (1st time Xserver is started)
I can login as root or a user and use the system all day without the hang.
If I logout (which restarts the Xserver) and log back in the system will usually hang within several minutes.

I suspect something is not being cleaned/reset properly when the Xserver exits.

Until someone finds a fix for this, I will not logout or I will just do a shutdown.
Of course I will still play around with thhis looking for a solution.

spiked3
28th May 2008, 04:01 PM
I too am having these problems severily. I tried removing the rhgb as suggested above but it did not help. I have also tried noapic and nolapic, no success. The lock happens at random times although it seems to more often when im draggin a window or moving a scrollbar or something related. I can reproduce it quickly by playing in blender (very video card intense I would imagine) and my gut guess is something to do with video accleration.
dbrenner - can you/would you try blender and see if you can still 'run all day'?
rhcla - my guess is the lost synchronization is probably due to some other spin loop problem - should your bug report be modified to mention the total lockup (and up the severity)?

KKJensen
28th May 2008, 04:19 PM
I've got the same prob....Acer Aspire 3610 with Intel 915 graphics...1.5GB RAM

It seems to happen more often for me when I have an external wireless mouse plugged in.

Also, if I try and fire up MS Excel (via crossover) too quickly after boot it will freeze the same way. (I had one of those 'important' files that HAD to be worked on quickly....what a nightmare that was)

I've scoured /var/log/messeges and dmesg but I don't see any errors except something about pulseaudio...but my sound works fine (except one pop sound during the boot).

stevea
28th May 2008, 04:43 PM
I suggest youse guys try to provide each other with a little diagnostic info instead of just shouting "me too" on the thread. I don't have the problem so I can't be much direct help.

PLEASE report which fedora you are using (f8, f9 ...), the exact kernel rev (uname -r), and since it is very likely that some driver is involved type "lsmod" and save the result before the crash. It may be some naughty interaction between a driver and some specific hardware so an "lspci" output may help too.

When you reboot check the logs too.

You seem to suspect the X11 vid drivers, so by all means report which vid driver, try switching vid drivers back to vesa, or else try running at run level 3 (no X11) and see if the problem recurs.

Dbrenner makes a good case that his problem is related to X11 (so I assume he is on F9 w/ the newer xorg release). Quite possible it has a bug, but that shouldn't cause a kernel crash unless a buggy driver is involved.

The mouse drivers are mostly built-in (not loaded as modules) so it might be interesting to see if switching the mouse type from din connector to USB (or back) makes a difference.

KKJensen
28th May 2008, 05:27 PM
Clarification: F9...all updates done. Problem never happened in F8. Haven't checked the '2nd xwindows restart' for repeatability.

kernel: 2.6.25.3-18.fc9.i686

drivers from lsmod (all default drivers for integrated intel stuff...only ndiswrapper for bcm4318 wlan added):


Module Size Used by
ip6t_REJECT 7552 2
nf_conntrack_ipv6 15864 6
ip6table_filter 6400 1
ip6_tables 14736 1 ip6table_filter
nf_conntrack_netbios_ns 6144 0
ipt_REJECT 6784 2
xt_tcpudp 6656 10
nf_conntrack_ipv4 11396 6
xt_state 5888 12
nf_conntrack 49748 4 nf_conntrack_ipv6,nf_conntrack_netbios_ns,nf_connt rack_ipv4,xt_state
iptable_filter 6528 1
ip_tables 13840 1 iptable_filter
x_tables 15236 6 ip6t_REJECT,ip6_tables,ipt_REJECT,xt_tcpudp,xt_sta te,ip_tables
bridge 46104 0
bnep 14464 2
rfcomm 34576 4
l2cap 22272 16 bnep,rfcomm
bluetooth 47588 5 bnep,rfcomm,l2cap
ndiswrapper 159380 0
fuse 41116 5
sunrpc 151412 3
dm_mirror 26116 0
dm_multipath 18056 0
dm_mod 49236 2 dm_mirror,dm_multipath
ipv6 221660 20 ip6t_REJECT,nf_conntrack_ipv6
snd_intel8x0m 16780 0
battery 14084 0
ac 8068 0
snd_seq_dummy 6660 0
snd_intel8x0 30492 3
snd_ac97_codec 94368 2 snd_intel8x0m,snd_intel8x0
ac97_bus 5504 1 snd_ac97_codec
video 20368 0
snd_seq_oss 30364 0
snd_seq_midi_event 9600 1 snd_seq_oss
snd_seq 48448 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
output 6656 1 video
8139too 23936 0
8139cp 20864 0
mii 8192 2 8139too,8139cp
i915 84484 7
snd_seq_device 10124 3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss 42496 0
snd_mixer_oss 16768 1 snd_pcm_oss
snd_pcm 67076 4 snd_intel8x0m,snd_intel8x0,snd_ac97_codec,snd_pcm_ oss
iTCO_wdt 13476 0
iTCO_vendor_support 6916 1 iTCO_wdt
button 10000 0
acer_wmi 12596 0
snd_timer 21640 2 snd_seq,snd_pcm
i2c_i801 11920 0
drm 145508 8 i915
wmi 9640 1 acer_wmi
snd 48312 17 snd_intel8x0m,snd_seq_dummy,snd_intel8x0,snd_ac97_ codec,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_o ss,snd_mixer_oss,snd_pcm,snd_timer
serio_raw 8708 0
i2c_algo_bit 8964 1 i915
i2c_core 20628 4 i915,i2c_i801,drm,i2c_algo_bit
pcspkr 6272 0
joydev 12608 0
soundcore 9288 1 snd
snd_page_alloc 11400 3 snd_intel8x0m,snd_intel8x0,snd_pcm
sr_mod 17064 0
sg 31028 0
cdrom 32796 1 sr_mod
ata_generic 8964 0
ata_piix 20100 3
pata_acpi 8192 0
libata 126688 3 ata_generic,ata_piix,pata_acpi
sd_mod 25624 4
scsi_mod 120820 4 sr_mod,sg,libata,sd_mod
ext3 108424 2
jbd 40852 1 ext3
mbcache 10116 1 ext3
uhci_hcd 22928 0
ohci_hcd 22276 0
ehci_hcd 32268 0


I've been watching the logs and the freeze happens 'quick' enough that the mouse stutters once or twice and stops. No system beeps, no entries in a log. At first I thought it might be overheating as I have small kids so I close the laptop lid...it's a 1.4Ghz Celeron so it doesn't heat much. Then I thought it was my mouse (which seemed weird that a usb device as simple as a mouse could cause a crash) but it turned out to be the mouse's batteries needed swapping.

You see where this is going? Those of us that don't know exactly what has changed or where the root of a problem might be don't really know where to look or what is the most useful or obvious information to be posting. I've always assumed that if I am using the native drivers and do all the updates that it puts me on some kind of common ground with other people...and hopefully make it easier to identify.

Thanks for the tips on better technical posting. Now we just need to find some kind of an error to report...without a log of some sort it's all hearsay.

Is it just me or is just about every crashing computer an Acer?

spiked3
28th May 2008, 05:35 PM
Well apparetnly this has been a problem for a long time. At least in my case some info from march 2007 seemed to have helped.

http://ubuntuforums.org/showthread.php?t=316924&page=2

The problem is described in ubuntu although I'm running F9, but with an ATI card that seems to be the common thread.

I was able to ssh in and it was indeed Xorg going 100% along with hald-addon-stor. Killing hald-addon-stor did not help, but killing Xorg did.

When Xorg restarted I got a balloon pop up saying it wanted to send a kernel dump to kerneloops, which I allowed. I poked around in every log I know of and there was 0 error messages, so the kerneloops may have just been the result of the kill signal I used (i dont remember which but it wasnt 15, 15 did not kill Xorg). There are 0 error messages in any of the logs, after reboot or after kill.

It seems to me that the problem is common and old enough it should be better understood by now.

rehcla
29th May 2008, 08:04 PM
The problems vanished from the Acer since I did the updates today...
Now everything runs fine and stable!!!

Greetings,

rehcla

dbrenner
29th May 2008, 08:26 PM
The updates I applied today DID NOT resolve my problem.
No time to look at it further until Sunday.

rehcla
30th May 2008, 12:31 PM
Hi

Sorry guys, I was to hasty with that!
The problem with the cursor reappeared after rebooting the System again!!!
But the random freeze of the system is gone...
Just when I try to halt or reboot the system (by Commandline or from Gnome) the system freezes immediately...

I did an update from updates-testing for kernel-2.6.25.4-30 and xorg-x11-drv-ati ,
but the symptoms are the same :confused:

Greetings,

rehcla

KKJensen
30th May 2008, 01:28 PM
I still get freezes at unreproducible times so I might back up and use F8 again...I've got other issues with browsing networks and logging into a windows server 2003 domain that are affecting what I can get done at work.