From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>,
drzeus-wbsd@drzeus.cx, wbsd-devel@list.drzeus.cx
Subject: wbsd: IRQ handler type mismatch
Date: Mon, 05 Feb 2007 21:16:59 -0600 [thread overview]
Message-ID: <45C7F32B.1060402@shaw.ca> (raw)
I'm seeing this on bootup on my laptop with recent kernels (currently
2.6.20-rc6-mm3):
Floppy drive(s): fd0 is 1.44M
IRQ handler type mismatch for IRQ 6
current handler: wbsd
[<c0451fe7>] setup_irq+0x194/0x1ac
[<e0ad7189>] floppy_hardint+0x0/0xc0 [floppy]
[<c045207b>] request_irq+0x7c/0x98
[<e0a5c67c>] init_module+0x546/0xe15 [floppy]
[<c05ffe85>] _spin_unlock_irq+0x5/0x7
[<c0442410>] __link_module+0x0/0x10
[<c0442410>] __link_module+0x0/0x10
[<c0443d6c>] sys_init_module+0x1781/0x18c8
[<c04dbf10>] blk_init_queue+0x0/0x8
[<c04734f6>] vfs_read+0xa6/0x152
[<c0404e26>] sysenter_past_esp+0x5f/0x85
[<c0600000>] error_code+0x68/0x84
=======================
floppy0: Unable to grab IRQ6 for the floppy driver
It looks like wbsd is being loaded first, which being a nice PnP device
sees that IRQ 6 is available and grabs it. Then the we try to load the
floppy module (which is hard-coded to use IRQ 6) which fails because
wbsd already owns IRQ6 (which is fine, there's no floppy controller
anyway). The mismatch is occurring because wbsd passes IRQF_SHARED
whereas floppy doesn't. I assume one of the two is likely wrong. Should
wbsd really be passing IRQF_SHARED here? This is an LPC device which
uses ISA-style edge triggered interrupts, is it safe to try and share an
interrupt with this chip anyway?
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next reply other threads:[~2007-02-06 3:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-06 3:16 Robert Hancock [this message]
2007-02-06 7:01 ` wbsd: IRQ handler type mismatch Pierre Ossman
2007-02-06 11:30 ` [PATCH] kernel: shut up the IRQ mismatch messages (Re: wbsd: IRQ handler type mismatch) Alan
2007-02-06 19:29 ` Andrew Morton
2007-02-06 19:46 ` Alan
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=45C7F32B.1060402@shaw.ca \
--to=hancockr@shaw.ca \
--cc=drzeus-wbsd@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=wbsd-devel@list.drzeus.cx \
/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.