Red Hat Bugzilla – Bug 806072
Null pointer dereference at 0000000000000004 in skb_head_state+0x27/0x100
Last modified: 2012-05-14 14:03:53 EDT
Created attachment 572076 [details] Screenshoot ot the error message with stacktrace Description of problem: When I came back to my computer after about half an hour, I have found it frozen displaying the message in the screenshoot. The general structure is following: BUG: Unable to handle kernel null pointer dereference at 0000000000000004 IP: [<ffffffff8154fad7>] skb_head_state+0x27/0x100 PDG: 106941067 PUD 1089a4067 PMD 0 list of loaded modules register content stack content stack trace starting with call to __kfree_skb and ending with call to gs_change then it says that Kernel panic - not syncing - fatal exception in interrupt Version-Release number of selected component (if applicable): uname -a Linux private 3.3.0-0.rc5.git3.1.fc18.x86_64 #1 SMP Wed Feb 29 21:26:31 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux How reproducible: I do not know, it happened only once. Before, I have been suspending the system to disc for a few days every day and working mostly with PostgreSQL, web browsers, LibreOffice and SageMath, but that is probably irrelevant. Steps to Reproduce: Hope the stacktrace in the screenshoot may tell you Actual results: Kernel panic Expected results: No kernel panic
had that machine been hibernated at all ?
> had that machine been hibernated at all ? I have hibernated and resumed the machine several times before, as I wrote in the bugreport.
ok, this is probably a symptom of the random memory corruption problem we've been chasing.
[Mass hibernate bug update] Dave Airlied has found an issue causing some corruption in the i915 fbdev after a resume from hibernate. I have included his patch in this scratch build: http://koji.fedoraproject.org/koji/taskinfo?taskID=3940545 This will probably not solve all of the issues being tracked at the moment, but it is worth testing when the build completes. If this seems to clear up the issues you see with hibernate, please report your results in the bug.