From: "Randy.Dunlap" <rddunlap@osdl.org>
To: ganesh.venkatesan@intel.com, jesse.brandeburg@intel.com,
netdev@oss.sgi.com
Subject: e100 badness (2.6.10-rc1-mm2)
Date: Mon, 01 Nov 2004 20:24:25 -0800 [thread overview]
Message-ID: <41870BF9.6060207@osdl.org> (raw)
Hi Ganesh, Jesse --
I see this in 2.6.10-rc1-mm2:
Badness in enable_irq at kernel/irq/manage.c:112
[<c0106e09>] dump_stack+0x1e/0x20
[<c013f7ab>] enable_irq+0xaa/0x114
[<c02b0498>] e100_up+0x130/0x23f
[<c02b164a>] e100_open+0x26/0x6e
[<c0396896>] dev_open+0x6e/0x7c
[<c0397e05>] dev_change_flags+0x56/0x126
[<c03d2426>] devinet_ioctl+0x60b/0x6cd
[<c03d4261>] inet_ioctl+0x81/0xae
[<c038ddbc>] sock_ioctl+0x1d3/0x2d6
[<c0172970>] sys_ioctl+0x179/0x21d
[<c0105f5d>] sysenter_past_esp+0x52/0x71
I think that it happens because (in e100_up()),
disable_irq() is called before request_irq() is called.
If there are no other interrupt handlers on the same irq,
then desc->depth is cleared to 0 by setup_irq() [called
from request_irq()].
Then the following enable_irq() is confused by
desc->depth == 0.
--
~Randy
next reply other threads:[~2004-11-02 4:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-02 4:24 Randy.Dunlap [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-02 5:05 e100 badness (2.6.10-rc1-mm2) Venkatesan, Ganesh
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=41870BF9.6060207@osdl.org \
--to=rddunlap@osdl.org \
--cc=ganesh.venkatesan@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=netdev@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).