Bug 743453 - kernel 3.1.0-0.rc8.git0.0.fc17.x86_64 gets sleeping function called from invalid context at kernel/rwsem.c:21 after failed paging request
Summary: kernel 3.1.0-0.rc8.git0.0.fc17.x86_64 gets sleeping function called from inva...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
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-10-05 00:26 UTC by Michal Jaegermann
Modified: 2012-02-02 16:51 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-02 16:51:14 UTC
Type: ---

Attachments (Terms of Use)
dmesg from boot with two oopses (65.23 KB, text/plain)
2011-10-05 00:27 UTC, Michal Jaegermann 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Michal Jaegermann 2011-10-05 00:26:04 UTC 
Description of problem:

While booting, and apparently triggered by udev, I got first

BUG: unable to handle kernel paging request at ffffffff8005af41

immediately followed by:

BUG: sleeping function called from invalid context at kernel/rwsem.c:21
in_atomic(): 0, irqs_disabled(): 1, pid: 425, name: udevd

Full dmesg is attached.

Version-Release number of selected component (if applicable):
kernel-3.1.0-0.rc8.git0.0.fc17.x86_64

How reproducible:
I do not know.  I do not recall seeing something like that yet.
Comment 1 Michal Jaegermann 2011-10-05 00:27:10 UTC 
Created attachment 526351 [details]
dmesg from boot with two oopses
Comment 2 Josh Boyer 2011-11-08 00:10:16 UTC 
Have you seen this with a recent rawhide kernel?  Either the final 3.1 release, or a 3.2 pre-release?
Comment 3 Michal Jaegermann 2011-11-10 22:24:09 UTC 
(In reply to comment #2)
> Have you seen this with a recent rawhide kernel?  Either the final 3.1 release,
> or a 3.2 pre-release?

I do not think so although I cannot be absolutely sure.  On rare occasions I had failures to boot with recent rawhide kernels.  Every time a lockup was so complete that I did not have any real information from those incidents and the second try invariably worked.  It is quite possible that these are rather related to bug 537697 (but this one may also have some common points with that old one).
Comment 4 Josh Boyer 2012-02-02 16:51:14 UTC 
I'm going to close this out for now.  If you see this particular error again on a 3.3 kernel, please reopen or open a new bug with the relevant details.
Note You need to log in before you can comment on or make changes to this bug.