Bug 458483 - [Realtime][Kernel] BUG: workqueue leaked lock or atomic:
[Realtime][Kernel] BUG: workqueue leaked lock or atomic:
Status: CLOSED WONTFIX
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: realtime-kernel (Show other bugs)
1.1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Steven Rostedt
http://rhts.redhat.com/cgi-bin/rhts/t...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-08-08 15:36 EDT by Jeff Burke
Modified: 2012-01-09 16:44 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-01-09 16:44:34 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jeff Burke 2008-08-08 15:36:34 EDT
Description of problem:
While running the kernel tests for 2.6.24.7-75.el5rttrace the kernel panic'd on boot. i386, hp-dl585g2-01.rhts.bos.redhat.com, RHEL5-Server-U2

Version-Release number of selected component (if applicable):
2.6.24.7-75.el5rttrace

How reproducible:
Unknown

Steps to Reproduce:
1. Install RHEL5.2 i386 on hp-dl585g2-01.rhts.bos.redhat.com
2. Install 2.6.24.7-75.el5rttrace
3. Reboot into trace kernel
  
Actual results:
BUG: workqueue leaked lock or atomic: khelper/0xc0644a07/115
    last function: 0x0
Pid: 115, comm: khelper Not tainted 2.6.24.7-75.el5rttrace #1
 [<c043ea99>] leak_check+0x66/0x6c
 [<c0644a07>] ? preempt_schedule+0x8/0x68
 [<c043eb8a>] run_workqueue+0xeb/0x1a9
 [<c043e50b>] ? __call_usermodehelper+0x0/0x52
 [<c043f6ea>] ? worker_thread+0x0/0xcb
 [<c043f7aa>] worker_thread+0xc0/0xcb
 [<c0442326>] ? autoremove_wake_function+0x0/0x3d
 [<c0442254>] kthread+0x40/0x68
 [<c0442214>] ? kthread+0x0/0x68
 [<c0404edf>] kernel_thread_helper+0x7/0x10
 =======================
---------------------------
| preempt count: c0644a07 ]
| 7-level deep critical section nesting:
----------------------------------------
.. [<c064419a>] .... __schedule+0x2c/0x822
.....[<c0644b6b>] ..   ( <= schedule+0xea/0x109)
.. [<c064661e>] .... __spin_lock+0x15/0x2c
.....[<c0644297>] ..   ( <= __schedule+0x129/0x822)
.. [<c064697f>] .... __spin_trylock+0x15/0x58
.....[<c04246bf>] ..   ( <= double_lock_balance+0x27/0x5c)
.. [<c064679c>] .... __spin_lock_irqsave+0x1e/0x38
.....[<c04708e9>] ..   ( <= ftrace_record_ip+0x24d/0x273)
.. [<00000000>] .... 0x0
.....[<00000000>] ..   ( <= 0x0)
.. [<00000000>] .... 0x0
.....[<00000000>] ..   ( <= 0x0)
.. [<00000000>] .... 0x0
.....[<00000000>] ..   ( <= 0x0)

Expected results:
System should boot normally

Additional info:

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