Bug 587229
| Summary: | inconsistent lock state | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Rik Theys <rik.theys> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 13 | CC: | anton, dougsland, gansalmon, itamar, jonathan, kernel-maint, rik.theys |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-06-27 15:57:14 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: | |||
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |
Description of problem: kernel messages show the following trace: ================================= [ INFO: inconsistent lock state ] 2.6.33.2-57.fc13.x86_64 #1 --------------------------------- inconsistent {HARDIRQ-ON-W} -> {IN-HARDIRQ-W} usage. swapper/0 [HC1[1]:SC0[0]:HE0:SE1] takes: (&(&tu->qlock)->rlock){?.+...}, at: [<ffffffffa01588c8>] snd_timer_user_tinterrupt+0x3a/0x179 [snd_timer] {HARDIRQ-ON-W} state was registered at: [<ffffffff8107efd5>] __lock_acquire+0x33b/0xd2c [<ffffffff8107faa2>] lock_acquire+0xdc/0x102 [<ffffffff8147a353>] _raw_spin_lock+0x36/0x69 [<ffffffffa0158788>] snd_timer_user_ccallback+0x6e/0xb9 [snd_timer] [<ffffffffa015932f>] snd_timer_notify1+0x99/0x143 [snd_timer] [<ffffffffa0159556>] _snd_timer_stop+0x17d/0x18e [snd_timer] [<ffffffffa015969e>] snd_timer_stop+0x1b/0x53 [snd_timer] [<ffffffffa015afc9>] snd_timer_user_ioctl+0x6eb/0x784 [snd_timer] [<ffffffff8112d108>] vfs_ioctl+0x32/0xa6 [<ffffffff8112d688>] do_vfs_ioctl+0x490/0x4d6 [<ffffffff8112d724>] sys_ioctl+0x56/0x79 [<ffffffff81009c72>] system_call_fastpath+0x16/0x1b irq event stamp: 20215892 hardirqs last enabled at (20215891): [<ffffffff8101194c>] mwait_idle+0x79/0x95 hardirqs last disabled at (20215892): [<ffffffff81009aea>] save_args+0x6a/0x70 softirqs last enabled at (20215888): [<ffffffff81057bde>] __do_softirq+0x1b7/0x1cd softirqs last disabled at (20215875): [<ffffffff8100abdc>] call_softirq+0x1c/0x30 other info that might help us debug this: 2 locks held by swapper/0: #0: (snd_pcm_link_rwlock){.-.-..}, at: [<ffffffffa016d2a5>] snd_pcm_period_elapsed+0x84/0x52a [snd_pcm] #1: (&(&substream->self_group.lock)->rlock){-.-...}, at: [<ffffffffa016d2bd>] snd_pcm_period_elapsed+0x9c/0x52a [snd_pcm] stack backtrace: Pid: 0, comm: swapper Not tainted 2.6.33.2-57.fc13.x86_64 #1 Call Trace: <IRQ> [<ffffffff8107dcae>] valid_state+0x17f/0x192 [<ffffffff8101579c>] ? save_stack_trace+0x2f/0x4c [<ffffffff8107e59b>] ? check_usage_forwards+0x0/0x87 [<ffffffff8107dddb>] mark_lock+0x11a/0x235 [<ffffffff8107ef61>] __lock_acquire+0x2c7/0xd2c [<ffffffff8107dcee>] ? mark_lock+0x2d/0x235 [<ffffffff8107faa2>] lock_acquire+0xdc/0x102 [<ffffffffa01588c8>] ? snd_timer_user_tinterrupt+0x3a/0x179 [snd_timer] [<ffffffffa0159c19>] ? snd_timer_interrupt+0x27e/0x2f0 [snd_timer] [<ffffffff8147a353>] _raw_spin_lock+0x36/0x69 [<ffffffffa01588c8>] ? snd_timer_user_tinterrupt+0x3a/0x179 [snd_timer] [<ffffffff8107caae>] ? lock_release_holdtime+0x34/0xe3 [<ffffffffa01588c8>] snd_timer_user_tinterrupt+0x3a/0x179 [snd_timer] [<ffffffffa0159c2e>] snd_timer_interrupt+0x293/0x2f0 [snd_timer] [<ffffffffa016d6dd>] snd_pcm_period_elapsed+0x4bc/0x52a [snd_pcm] [<ffffffff8107ca78>] ? trace_hardirqs_off+0xd/0xf [<ffffffff81072258>] ? cpu_clock+0x43/0x5e [<ffffffffa01e144e>] azx_interrupt+0xa6/0x136 [snd_hda_intel] [<ffffffff810ad5b8>] handle_IRQ_event+0x53/0x119 [<ffffffff810af3ef>] handle_edge_irq+0xe6/0x132 [<ffffffff8100c4c3>] handle_irq+0x88/0x91 [<ffffffff8147fe9c>] do_IRQ+0x5c/0xc3 [<ffffffff8147af13>] ret_from_intr+0x0/0x16 <EOI> [<ffffffff81011955>] ? mwait_idle+0x82/0x95 [<ffffffff8101194c>] ? mwait_idle+0x79/0x95 [<ffffffff81008c34>] cpu_idle+0xaf/0xe9 [<ffffffff814720ce>] start_secondary+0x201/0x242 Version-Release number of selected component (if applicable): kernel 2.6.33.2-57.fc13.x86_64 How reproducible: don't know Steps to Reproduce: 1. 2. 3. Actual results: trace in kernel messages Expected results: no trace Additional info: