From: Dave Jones <davej@redhat.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: serial8250 lockdep report from 2.6.21-rc7
Date: Mon, 23 Apr 2007 13:07:42 -0400 [thread overview]
Message-ID: <20070423170742.GA9823@redhat.com> (raw)
=================================
[ INFO: inconsistent lock state ]
2.6.20-1.3094.fc7 #1
---------------------------------
inconsistent {hardirq-on-W} -> {in-hardirq-W} usage.
swapper/0 [HC1[1]:SC0[0]:HE0:SE1] takes:
(&port_lock_key){++..}, at: [<c0558f96>] serial8250_interrupt+0x4a/0xe0
{hardirq-on-W} state was registered at:
[<c044021d>] __lock_acquire+0x448/0xba9
[<c0440d70>] lock_acquire+0x56/0x6f
[<c060ffd1>] _spin_lock+0x2b/0x38
[<c055893b>] serial8250_backup_timeout+0x6d/0xe8
[<c042c972>] run_timer_softirq+0x121/0x189
[<c0429dfb>] __do_softirq+0x6f/0xe2
[<c0407a64>] do_softirq+0x61/0xd0
[<ffffffff>] 0xffffffff
irq event stamp: 332718
hardirqs last enabled at (332717): [<c0403dde>] default_idle+0x3e/0x59
hardirqs last disabled at (332718): [<c0406054>] common_interrupt+0x24/0x40
softirqs last enabled at (332708): [<c0429e68>] __do_softirq+0xdc/0xe2
softirqs last disabled at (332691): [<c0407a64>] do_softirq+0x61/0xd0
other info that might help us debug this:
1 lock held by swapper/0:
#0: (&irq_lists[i].lock){+...}, at: [<c0558f61>] serial8250_interrupt+0x15/0xe0
stack backtrace:
[<c0406832>] show_trace_log_lvl+0x1a/0x2f
[<c0406df1>] show_trace+0x12/0x14
[<c0406e75>] dump_stack+0x16/0x18
[<c043ed13>] print_usage_bug+0x141/0x14b
[<c043f402>] mark_lock+0xa2/0x419
[<c044018e>] __lock_acquire+0x3b9/0xba9
[<c0440d70>] lock_acquire+0x56/0x6f
[<c060ffd1>] _spin_lock+0x2b/0x38
[<c0558f96>] serial8250_interrupt+0x4a/0xe0
[<c045699a>] handle_IRQ_event+0x1a/0x46
[<c0457a8a>] handle_fasteoi_irq+0x7d/0xb6
[<c0407b84>] do_IRQ+0xb1/0xd9
next reply other threads:[~2007-04-23 17:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-23 17:07 Dave Jones [this message]
2007-04-23 20:32 ` serial8250 lockdep report from 2.6.21-rc7 Jiri Kosina
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070423170742.GA9823@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.