From: "Miles Lane" <miles.lane@gmail.com>
To: "Andrew Morton" <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>,
"Jeff Garzik" <jgarzik@pobox.com>
Subject: 2.6.23-rc1-mm2 + cpufreq patch -- inconsistent {in-hardirq-W} -> {hardirq-on-W} usage.
Date: Thu, 2 Aug 2007 19:53:32 -0700 [thread overview]
Message-ID: <a44ae5cd0708021953q79d03484k3c191bfe4894cd9a@mail.gmail.com> (raw)
I am running Ubuntu Gutsy with latest updates.
When I run "/etc/init.d/networking stop" with my custom kernel, I get:
=================================
[ INFO: inconsistent lock state ]
2.6.23-rc1-mm2 #21
---------------------------------
inconsistent {in-hardirq-W} -> {hardirq-on-W} usage.
ifconfig/8982 [HC0[0]:SC0[0]:HE1:SE1] takes:
(&tp->lock){++..}, at: [<f8b9d65a>] rtl8139_interrupt+0x22/0x377 [8139too]
{in-hardirq-W} state was registered at:
[<c0144837>] __lock_acquire+0x430/0xbca
[<c0145047>] lock_acquire+0x76/0x9d
[<c031ffe0>] _spin_lock+0x23/0x32
[<f8b9d65a>] rtl8139_interrupt+0x22/0x377 [8139too]
[<c0154b44>] handle_IRQ_event+0x1a/0x4f
[<c0155c6c>] handle_fasteoi_irq+0x7d/0xb6
[<c0109a5a>] do_IRQ+0xaf/0xd9
[<ffffffff>] 0xffffffff
irq event stamp: 1501
hardirqs last enabled at (1501): [<c0173232>] kfree+0xc7/0xdb
hardirqs last disabled at (1500): [<c01731d2>] kfree+0x67/0xdb
softirqs last enabled at (1480): [<c02cf082>] dev_deactivate+0x87/0xa0
softirqs last disabled at (1478): [<c031fffa>] _spin_lock_bh+0xb/0x37
other info that might help us debug this:
1 lock held by ifconfig/8982:
#0: (rtnl_mutex){--..}, at: [<c031ed95>] mutex_lock+0x1c/0x1f
stack backtrace:
[<c01080ab>] show_trace_log_lvl+0x12/0x25
[<c0108a9e>] show_trace+0xd/0x10
[<c0108bac>] dump_stack+0x16/0x18
[<c0143374>] print_usage_bug+0x107/0x114
[<c0143bdd>] mark_lock+0x1e9/0x400
[<c01448ab>] __lock_acquire+0x4a4/0xbca
[<c0145047>] lock_acquire+0x76/0x9d
[<c031ffe0>] _spin_lock+0x23/0x32
[<f8b9d65a>] rtl8139_interrupt+0x22/0x377 [8139too]
[<c015506f>] free_irq+0xc9/0xf2
[<f8b9ef56>] rtl8139_close+0xac/0x14a [8139too]
[<c02c2135>] dev_close+0x4e/0x6b
[<c02c128a>] dev_change_flags+0x9f/0x152
[<c03015f2>] devinet_ioctl+0x209/0x506
[<c0301f5a>] inet_ioctl+0x86/0xa4
[<c02b8211>] sock_ioctl+0x1a9/0x1c7
[<c017ffca>] do_ioctl+0x22/0x67
[<c0180258>] vfs_ioctl+0x249/0x25c
[<c0180297>] sys_ioctl+0x2c/0x45
[<c0106f02>] sysenter_past_esp+0x6b/0xb5
=======================
eth2: link down
reply other threads:[~2007-08-03 2:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=a44ae5cd0708021953q79d03484k3c191bfe4894cd9a@mail.gmail.com \
--to=miles.lane@gmail.com \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®