Bug 428768

Summary: Ooops: Unable to handle kernel NULL pointer dereference
Product: [Fedora] Fedora Reporter: Chris Sorisio <chris.sorisio>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 8CC: quantumburnz
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-10-22 21:43:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Ooops Text
none
CPU & PCI Info none

Description Chris Sorisio 2008-01-15 01:32:11 UTC 
Ooops:  Unable to handle kernel NULL pointer dereference at 0000000000000008\

Version-Release number of selected component (if applicable):

Firefox is version 3 beta 2.

How reproducible:

Seems to happen randomly.  Sometimes when coming out of sleep mode, sometimes
when clicking on a tab in Firefox.  Sometimes, it "just happens."

Additional info:

See attachments for Ooops message and lspci.
Comment 1 Chris Sorisio 2008-01-15 01:32:11 UTC 
Created attachment 291665 [details]
Ooops Text
Comment 2 Chris Sorisio 2008-01-15 01:35:40 UTC 
Created attachment 291666 [details]
CPU & PCI Info
Comment 3 Chuck Ebbert 2008-01-17 23:53:59 UTC 
(In reply to comment #1)
> Created an attachment (id=291665) [edit]
> Ooops Text
> 

Proprietary modules (vmnet etc.) are loaded.
There were earlier errors where processes were found with bad page state and
were killed.

So this oops is pretty much useless. Bad page state is sometimes caused by
failing hardware -- has memtest86 been run overnight on this system?
Comment 4 Christopher D. Stover 2008-10-22 21:43:15 UTC 
The information we've requested above is required in order
to review this problem report further and diagnose or fix the
issue if it is still present.  Since it has been thirty days or
more since we first requested additional information, we're assuming
the problem is either no longer present in the current Fedora release, or
that there is no longer any interest in tracking the problem.

Setting status to "CLOSED: INSUFFICIENT_DATA".  If you still
experience this problem after updating to our latest Fedora
release and can provide the information previously requested,
please feel free to reopen the bug report.

Thank you in advance.