Bug 753785 - [abrt] kernel: BUG: sleeping function called from invalid context at kernel/mutex.c:85: TAINTEDProprietary Module
Summary: [abrt] kernel: BUG: sleeping function called from invalid context at kernel/m...
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 15
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:813383786
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-14 13:58 UTC by David Kovalsky
Modified: 2014-03-31 23:46 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-14 14:20:49 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (1.53 KB, text/plain)
2011-11-14 13:58 UTC, David Kovalsky
no flags Details

Description David Kovalsky 2011-11-14 13:58:04 UTC
abrt version: 1.1.18
architecture: x86_64
cmdline: not_applicable
comment: I'll eventually report back if I figure out how to reproduce this
component: kernel
executable: kernel
kernel: 2.6.40.6-0.fc15.x86_64
package: kernel
reason: BUG: sleeping function called from invalid context at kernel/mutex.c:85
release: Fedora release 15 (Lovelock)
tainted: 1
time: 1321277302
uid: 0

backtrace
-----
BUG: sleeping function called from invalid context at kernel/mutex.c:85
in_atomic(): 0, irqs_disabled(): 1, pid: 7056, name: pm-suspend
Pid: 7056, comm: pm-suspend Tainted: P            2.6.40.6-0.fc15.x86_64 #1
Call Trace:
 [<ffffffff81047514>] __might_sleep+0xeb/0xf0
 [<ffffffff814878f9>] mutex_lock+0x24/0x4a
 [<ffffffff8148858a>] ? _raw_spin_lock_irqsave+0x12/0x2f
 [<ffffffff810adcaf>] irq_reserve_irqs+0x3a/0x85
 [<ffffffff810affee>] irq_set_chip+0x58/0x62
 [<ffffffff810b0370>] ? handle_fasteoi_irq+0x9b/0x9b
 [<ffffffff810b04a0>] irq_set_chip_and_handler_name+0x1e/0x37
 [<ffffffff81023e35>] arch_setup_hpet_msi+0xc0/0xce
 [<ffffffff81027a19>] hpet_setup_msi_irq+0x19/0x31
 [<ffffffff81027df5>] hpet_set_mode+0x111/0x15f
 [<ffffffff81027e57>] hpet_msi_set_mode+0x14/0x16
 [<ffffffff8107cd64>] clockevents_set_mode+0x20/0x4d
 [<ffffffff8107d493>] tick_notify+0x337/0x37c
 [<ffffffff8147fab8>] ? printk+0x51/0x53
 [<ffffffff8148b93e>] notifier_call_chain+0x37/0x63
 [<ffffffff810748e0>] raw_notifier_call_chain+0x14/0x16
 [<ffffffff8107caab>] clockevents_notify+0x3a/0xf9
 [<ffffffff810788bc>] timekeeping_resume+0xca/0xd8
 [<ffffffff812f87ec>] syscore_resume+0x6b/0xb3
 [<ffffffff8108997f>] suspend_devices_and_enter+0x14d/0x1d9
 [<ffffffff81089aeb>] enter_state+0xe0/0x137
 [<ffffffff81089166>] state_store+0xaf/0xc5
 [<ffffffff8123822b>] kobj_attr_store+0x17/0x19
 [<ffffffff811803c0>] sysfs_write_file+0x111/0x14d
 [<ffffffff8112744d>] vfs_write+0xac/0xf3
 [<ffffffff8112763c>] sys_write+0x4a/0x6e
 [<ffffffff8148ed02>] system_call_fastpath+0x16/0x1b

How to reproduce
-----
1. Nothing really interesting, just booting my Lenovo W510 and surfing the web
2.
3.

Comment 1 David Kovalsky 2011-11-14 13:58:08 UTC
Created attachment 533531 [details]
File: backtrace

Comment 2 Josh Boyer 2011-11-14 14:20:49 UTC
If you can hit this without whatever proprietary module you have loaded, please reopen.


Note You need to log in before you can comment on or make changes to this bug.