Bug 758460

Summary: [abrt] kernel: BUG: unable to handle kernel NULL pointer dereference at 00000200
Product: [Fedora] Fedora Reporter: Felipe Contreras <felipe.contreras>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:1650ee0e7dcd96ec965eaf8f969789e669f9e5e8
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-02 18:38:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Felipe Contreras 2011-11-29 20:50:35 UTC 
libreport version: 2.0.7
abrt_version:   2.0.6
cmdline:        BOOT_IMAGE=/vmlinuz-3.1.2-1.fc16.i686.PAE root=/dev/mapper/annwn-root ro rd.lvm.lv=annwn/root rd.dm=0 KEYTABLE=us rd.lvm.lv=annwn/swap SYSFONT=latarcyrheb-sun16 rd.md=0 rd.luks=0 LANG=en_US.UTF-8 selinux=0
kernel:         3.1.2-1.fc16.i686.PAE
reason:         BUG: unable to handle kernel NULL pointer dereference at 00000200
time:           Tue 29 Nov 2011 10:46:08 PM EET

backtrace:      Text file, 2091 bytes

comment:
:No idea.
:
:Seemed to have happened some time after I unplugged an external USB drive by mistake.

event_log:
:2011-11-29-22:49:24> Submitting oops report to http://submit.kerneloops.org/submitoops.php
:2011-11-29-22:50:28  Kernel oops has not been sent due to Couldn't connect to server
:2011-11-29-22:50:28* (exited with 1)
Comment 1 Felipe Contreras 2011-11-29 20:50:39 UTC 
Created attachment 538232 [details]
File: backtrace
Comment 2 Dave Jones 2011-11-30 16:18:40 UTC 
This is almost certainly memory corruption of some kind. A single bit got flipped.
I recommend trying memtest86 for a while.

If it's not bad hardware, there's really not enough context for us to do much here.
Comment 3 Felipe Contreras 2011-12-01 21:56:14 UTC 
(In reply to comment #2)
> This is almost certainly memory corruption of some kind. A single bit got
> flipped.
> I recommend trying memtest86 for a while.
> 
> If it's not bad hardware, there's really not enough context for us to do much
> here.

Seems to have happened again: bug #759286. It's strange that it's exactly the same backtrace. This time it happened while booting, and probably it was the same for this one.
Comment 4 Felipe Contreras 2011-12-03 00:13:15 UTC 
Yeap, seems to happen every time I boot now.
Comment 5 Josh Boyer 2011-12-03 15:33:43 UTC 
*** Bug 759286 has been marked as a duplicate of this bug. ***
Comment 6 Josh Boyer 2011-12-03 15:33:53 UTC 
*** Bug 759663 has been marked as a duplicate of this bug. ***
Comment 7 Felipe Contreras 2012-02-02 18:38:26 UTC 
I haven't seen this any more.