Bug 726850 - kernel 3.0.0-1.fc16 crashes with "unable to handle kernel paging request" and locks up
Summary: kernel 3.0.0-1.fc16 crashes with "unable to handle kernel paging request" and...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-29 22:55 UTC by Michal Jaegermann
Modified: 2011-09-12 20:13 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-09-12 20:13:32 UTC
Type: ---

Attachments (Terms of Use)
call trace from a kernel 3.0.0-1.fc16.x86_64 crash (2.75 KB, text/plain)
2011-07-29 22:55 UTC, Michal Jaegermann 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Michal Jaegermann 2011-07-29 22:55:09 UTC 
Created attachment 515947 [details]
call trace from a kernel 3.0.0-1.fc16.x86_64 crash

Description of problem:

Kernel-3.0.0-1.fc16.x86_64 crashed with


BUG: unable to handle kernel paging request at ffffffff8014a3a6
IP: [<ffffffff8014a3a6>] 0xffffffff8014a3a5
PGD 1a05067 PUD 1a09063 PMD 0 
Oops: 0010 [#1] SMP 
CPU 0 

For code I got "Bad RIP value".  The whole collected trace is attached.

As a result the whole machine locked up but not before recording oops in log files.  No such luck with abrtd which did not get anything.

At the time of this crash 'yum update' was quite busy with rebulding assorted rpm packages from retrieved deltas.  No other visible activity was happening at that moment.  That may be not related but it is difficult not to wonder.  On every boot I am seeing dire warnings about locking in disks handling code like those recorded in bug 537697.


Version-Release number of selected component (if applicable):
kernel-3.0.0-1.fc16.x86_64

How reproducible:
So far this was an unusual event.
Comment 1 Josh Boyer 2011-09-06 15:36:17 UTC 
Have you seen this again on a 3.1-rcX kernel?
Comment 2 Michal Jaegermann 2011-09-06 16:37:23 UTC 
(In reply to comment #1)
> Have you seen this again on a 3.1-rcX kernel?

No.  That particular crash was a one time event - does not matter which kernel version.

OTOH dire warnings about possible deadlock, those from bug 537697 and follow up comments, are a "standard staple" even if usually nothing seems to happen.  No idea if these are even remotely related.
Comment 3 Josh Boyer 2011-09-12 20:13:32 UTC 
I'm going to close this one out.  If it occurs again, please let us know.
Note You need to log in before you can comment on or make changes to this bug.