Bug 726850

Summary: kernel 3.0.0-1.fc16 crashes with "unable to handle kernel paging request" and locks up
Product: [Fedora] Fedora Reporter: Michal Jaegermann <michal>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: gansalmon, itamar, jonathan, jwboyer, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-09-12 20:13:32 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
call trace from a kernel 3.0.0-1.fc16.x86_64 crash none

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.