Bug 220826

Summary:	Kernel BUG at kernel/rwsem.c:20 after resume
Product:	[Fedora] Fedora	Reporter:	Michael Young <m.a.young>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6	CC:	wtogami
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	2.6.19-1-2895.fc6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-01-29 14:46:30 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:

Description Michael Young 2006-12-27 16:20:58 UTC

I have noticed that when I resume after suspending or hibernating I get the bug
report
swsusp: Restoring Highmem
BUG: sleeping function called from invalid context at kernel/rwsem.c:20
in_atomic():0, irqs_disabled():1
 [<c04051db>] dump_trace+0x69/0x1af
 [<c0405339>] show_trace_log_lvl+0x18/0x2c
 [<c04058ed>] show_trace+0xf/0x11
 [<c04059ea>] dump_stack+0x15/0x17
 [<c0439482>] down_read+0x12/0x20
 [<c04315e1>] blocking_notifier_call_chain+0xe/0
x29 
 [<c05a9d7c>] cpufreq_resume+0x118/0x135
 [<c0551964>] __sysdev_resume+0x20/0x53
 [<c0551aa7>] sysdev_resume+0x16/0x47
 [<c0555c8b>] device_power_up+0x5/0xa
 [<c044239c>] swsusp_suspend+0x74/0x90
 [<c0442832>] pm_suspend_disk+0x43/0xc9
 [<c0441995>] enter_state+0x53/0x176
 [<c0441b3d>] state_store+0x85/0x99
 [<c04a638a>] subsys_attr_store+0x1e/0x22
 [<c04a647d>] sysfs_write_file+0xa7/0xce
 [<c046fa51>] vfs_write+0xa8/0x159
 [<c047007e>] sys_write+0x41/0x67
 [<c0404013>] syscall_call+0x7/0xb
DWARF2 unwinder stuck at syscall_call+0x7/0xb
Leftover inexact backtrace:
 =======================
The machine seems to function okay after the resume, though sometimes freezes,
in one case with some corruption of rendering on the screen.
I have seen this with several kernels including 2.6.18-1.2849.fc6,
2.6.18-1.2868.fc6 and 2.6.18-1.2869.fc6
This seems related to bug 201508, but still occurs even thoguh that bug is
supposed to be fixed. This is with processor Mobile Intel(R) Pentium(R) 4 - M
CPU 2.00GHz and GeForce4 440 Go graphics card.

Comment 1 Michael Young 2007-01-29 14:46:30 UTC

The backtrace seems to have gone away in the current kernel 2.6.19-1-2895.fc6