Bug 809644 - [abrt] kernel: BUG: unable to handle kernel NULL pointer dereference at (null)
Summary: [abrt] kernel: BUG: unable to handle kernel NULL pointer dereference at ...
Keywords:
Status: CLOSED DUPLICATE of bug 808603
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 16
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:dfee64b4b64af9e335cd913e4d2...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-03 22:30 UTC by Brian Harrington
Modified: 2014-03-04 00:33 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-04 22:35:36 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (4.28 KB, text/plain)
2012-04-03 22:30 UTC, Brian Harrington 		no flags Details
View All

Description Brian Harrington 2012-04-03 22:30:31 UTC 
libreport version: 2.0.8
abrt_version:   2.0.7
cmdline:        BOOT_IMAGE=/vmlinuz-3.3.0-8.fc16.x86_64 root=/dev/mapper/vg_krakenssd-lv_root ro rd.lvm.lv=vg_krakenssd/lv_root rd.md=0 rd.luks.uuid=luks-1e8da1a5-de87-4435-af1a-b4cdfe4bfe82 KEYTABLE=us quiet SYSFONT=latarcyrheb-sun16 rhgb LANG=en_US.UTF-8 rd.lvm.lv=vg_krakenssd/lv_swap rd.dm=0
comment:        Wireless was not working.  Attempted to remove i2400m_usb  (rmmod i2400m_usb ) and the kernel had an oops, crashed, and (semi) gracefully recovered (the entire system did not panic).  Wireless still unavailable though.
kernel:         3.3.0-8.fc16.x86_64
reason:         BUG: unable to handle kernel NULL pointer dereference at           (null)
time:           Tue 03 Apr 2012 06:28:35 PM EDT

backtrace:      Text file, 4384 bytes
Comment 1 Brian Harrington 2012-04-03 22:30:35 UTC 
Created attachment 575000 [details]
File: backtrace
Comment 2 Stanislaw Gruszka 2012-04-04 22:35:36 UTC 

*** This bug has been marked as a duplicate of bug 808603 ***
Note You need to log in before you can comment on or make changes to this bug.