Description of problem: I have started to encounter thin problem since I've upgraded to 2.6.19 kernel, so I suspect it may be the cause. The problem is that the freeze is not reproducible, it just happens from time to time. I have tried Nikon D70 camera set in mass storage mode and Kingston Data Traveler 512 MB. Version-Release number of selected component (if applicable): 2.6.19-1.2895.fc6 How reproducible: occasionally Steps to Reproduce: 1. boot the system 2. plug or unplug the usb device Actual results: system freezes Expected results: no freeze Additional info: I'd very happily submit additional information, just need directions how to do so. Here are the last lines of /var/log/messages: Feb 1 12:42:53 fclaptop kernel: usb 5-4: new high speed USB device using ehci_hcd and address 4 Feb 1 12:42:53 fclaptop kernel: usb 5-4: configuration #1 chosen from 1 choice Feb 1 12:42:54 fclaptop kernel: audit(1170333774.189:32): avc: denied { write } for pid=1913 comm="mount.ntfs-3g" name="fuse" dev=tmpfs ino=1613 scontext=system_u:system_r:mount_t:s0 tcontext=system_u:object_r:fixed_disk_device_t:s0 tclass=chr_file
I don't know if it's related, but the system freezes as well when going to suspend-to-ram and also randomly without any particular reason. This definitely was not happening with the previous kernel. Cheers.
Well, with the current kernel, the random freezes have somehow vanished but the other two issues remain. After reading Keith Packard's blog entry, I suspect it may be a kernel panic. Is there any way I could get to console/logs/whatever AFTER the freeze to figure out what has really happened? Cheers.
Try netconsole. google for netconsole linux
I'll be plugging devices while not in X from this point on, so if it is a kernel panic, I'll see it.
I agree with Chuck, netconsole is more helpful for bugfixing, for several reasons. 1. I saw cases when X affected things. 2. You have to edit /etc/sysconfig/syslog and add "-c 8" to KLOGD_OPTIONS if you want to see everything. 3. If the box wedges well enough, you won't be able to scroll back and our tracebacks are getting pretty long. 4. It's better for me to have a text dump attached than a JPEG of console (although either is better than nothing). Don't needinfo bugs, they fall off developer's lists if you it. I think I better take this. USB storage is one of the more used and more reliable parts of our USB stack, this is very peculiar...
I agree that it is strange, too bad that it is so non-reproducible. I'll investigate the netconsole then.
Bummer, it needs another pc to output the log to. I don't have access to any atm. I'll try other methods then.
Created attachment 148547 [details] Appropriate part of /var/log/messages I reproduced it with X active, and somehow managed to “melt” the system using SysRq magic and setting the keyboard to XLATE mode. I have attached the /var/log/messages output.
Oh, this is good. This is substantial... although captured purely by a miracle. Usually /var/log/messages is useless. Mental note: this may be related to bug 230322 (please do not dup!).
Julian, please try 2.6.19-1.2911.6.4.fc6. There's a small chance that what you are seing is the improper IRQ migration.
Well, it really looks like the problem is solved. I'll close this bug now, but due to general non-reproducibility, I'll reopen it should the lockup happen again. Cheers.
Bummer. It still happens from time to time with 2.6.20-1.2933.fc6. I'll attach the log soon (it's a wee different now).
Created attachment 152555 [details] Yet another miraculously captured log
Created attachment 155322 [details] Output of dmesg showing the soft lockup error message
Comment on attachment 155322 [details] Output of dmesg showing the soft lockup error message This was on a Dell Core 2 Duo machine running in 64-bit mode after upgrading the kernel to 2.6.20-1.2948.fc6 . Seems references to my USB memory dongle often cause this error.
Taking into consideration the randomness of a random soft lockup, I'm tempted to say this was fixed, as I haven't experienced a lockup for quite a while. Should we close this, Erkki?
Umm, Erkki is not CCed. I am closing the bug then.