Bug 758460 - [abrt] kernel: BUG: unable to handle kernel NULL pointer dereference at 00000200
Summary: [abrt] kernel: BUG: unable to handle kernel NULL pointer dereference at 00000200
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 16
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:1650ee0e7dcd96ec965eaf8f969...
: 759286 759663 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-29 20:50 UTC by Felipe Contreras
Modified: 2012-02-02 18:38 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-02 18:38:55 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (2.04 KB, text/plain)
2011-11-29 20:50 UTC, Felipe Contreras 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.