Hide Forgot
Created attachment 502438 [details] Trace Description of problem: After what was described in #709979 I continued to work and finally hibernated the system without any further problems. Upon thawing today, I got this bug trace after the whole thawing process was up, system switched to SMP again and found its network interface, ie, this was the last thing logged in dmesg. Version-Release number of selected component (if applicable): 2.6.38.6-27.fc15.x86_64.debug #1 How reproducible: Unknown. Steps to Reproduce: Not sure... possibly 1. Boot 2. Login and suspend/hibernate to get into trace #709979 or #709544 3. Hibernate again 4. Thaw Actual results: BUG trace Expected results: No trace Additional info: This is on a Dell Latitude E4300, 6GB RAM, Intel GM45 with an SP9600 CPU. This laptop seems to hang into ACPI ( "ACPI: While loop taking a really long time. loop_count=..." ) after some number of hibernation/thaw cycles and/or throw random oops traces during hibernation/thaw that I was unable to save so far. Hence I run a debug kernel and hope to catch something more in my logs just before that happens. This INFO trace is such a catch.
Created attachment 502440 [details] dmesg buffer
Soon after the bug, I start to get a series of EXT4-fs error (device sda2): ext4_lookup:1043: inode #922613: comm updatedb: deleted inode referenced: 2887008 I guess I should reboot now or risk my fs completely trashed... Before somebody suggests it, the laptop passes DELL bios diagnostics w/o any problem and I've left memtest86+ running for over 5h checking those 6gb of memory with no problem reported.
Also some few EXT4-fs error (device sda2): ext4_ext_check_inode:428: inode #2887217: comm updatedb: bad header/extent: invalid magic - magic 80e3, entries 121, max 32995(0), depth 171(171) lines were thrown in between the above-mentioned errors.
In the end the messages stopped as soon as the updatedb cron task ended, so I dared not rebooting and continued my work. Hibernated the laptop in the afternoon and resumed in the evening to get one more BUG trace, BUG dentry (Not tainted): Poison overwritten a little time after working with the laptop. File trace3 attached.
Created attachment 502652 [details] trace3: BUG dentry (Not tainted): Poison overwritten
Next hibernation/thaw cycle, another bug trace right after resume completed: BUG selinux_inode_security (Not tainted): Redzone overwritten Complete trace in file trace4.
Created attachment 503122 [details] trace4: BUG selinux_inode_security (Not tainted): Redzone overwritten
And then, while hibernating again, yet another trace, this time a WARNING, right after preparing the hibernation image. WARNING: at fs/dcache.c:154 __d_free+0x31/0x5b() The process continued after that. System was later resumed successfully and is still running without anything else reported so far. Complete trace in file trace5. If anybody can look over these I'd be more than happy to provide any other information you need and/or test whatever you'd like.
Created attachment 503125 [details] trace5: WARNING: at fs/dcache.c:154 __d_free+0x31/0x5b()
Alright, awhile later, upon launching firefox, I got a soft lockup. Inspecting /var/log/messages I saw I had also hit a BUG in i915_gem.c right before the lockup. trace6: kernel BUG at drivers/gpu/drm/i915/i915_gem.c:3252! trace7: BUG: soft lockup - CPU#0 stuck for 67s! [firefox:20985] I had to hard boot my laptop this time (which led to such extensive fsck errors that I thought I had almost trashed my fs...), so these should be the last traces attached here, unless somebody requires something more of me. Thanks for your time!
Created attachment 503133 [details] trace6: kernel BUG at drivers/gpu/drm/i915/i915_gem.c:3252!
Created attachment 503134 [details] trace7: BUG: soft lockup - CPU#0 stuck for 67s! [firefox:20985]
Fedora 15 has reached it's end of life as of June 26, 2012. As a result, we will not be fixing any remaining bugs found in Fedora 15. In the event that you have upgraded to a newer release and the bug you reported is still present, please reopen the bug and set the version field to the newest release you have encountered the issue with. Before doing so, please ensure you are testing the latest kernel update in that release and attach any new and relevant information you may have gathered. Thank you for taking the time to file a report. We hope newer versions of Fedora suit your needs.