From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Chris Rankin <rankincj@yahoo.com>
Cc: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: Linux 2.6.17: IRQ handler mismatch in serial code?
Date: Mon, 19 Jun 2006 19:47:06 +0100 [thread overview]
Message-ID: <20060619184706.GH3479@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20060619180658.58945.qmail@web52908.mail.yahoo.com>
On Mon, Jun 19, 2006 at 07:06:58PM +0100, Chris Rankin wrote:
> I have just booted Linux 2.6.17 on an old 350 MHz PII, and have
> discovered this message in the boot log:
>
> setup_irq: irq handler mismatch
> <c0131a86> setup_irq+0x10d/0x11a <c01f3889> serial8250_interrupt+0x0/0x107
> <c0131b00> request_irq+0x6d/0x89 <c01f34ba> serial8250_startup+0x2d6/0x42b
> <c01f01e1> uart_startup+0x64/0x121 <c01f0401> uart_open+0x163/0x3a2
> <c01e214f> tty_open+0x175/0x2bc <c0152fb1> chrdev_open+0x160/0x17c
> <c0152e51> chrdev_open+0x0/0x17c <c014b093> __dentry_open+0xe0/0x1cf
> <c014b1e6> nameidata_to_filp+0x19/0x28 <c014b220> do_filp_open+0x2b/0x31
> <c014b30c> do_sys_open+0x3c/0xa9 <c014b3a6> sys_open+0x16/0x18
> <c0102adb> syscall_call+0x7/0xb
This seems to be an invalid situation - you appear to have an _ISA_
NE2000 card using IRQ3, trying to share the same interrupt as a
serial port.
ISA interrupts aren't sharable without additional hardware support
or specific software support in the Linux kernel interrupt
architecture.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2006-06-19 18:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 18:06 Linux 2.6.17: IRQ handler mismatch in serial code? Chris Rankin
2006-06-19 18:47 ` Russell King [this message]
2006-06-19 19:40 ` Chris Rankin
2006-06-19 19:44 ` Russell King
2006-06-20 1:00 ` Adam Belay
2006-06-20 7:50 ` Chris Rankin
2006-06-19 19:45 ` Mark Lord
2006-06-19 21:06 ` Alan Cox
2006-06-19 21:52 ` Mark Lord
2006-06-19 22:21 ` Alan Cox
[not found] <6pwmi-8mW-1@gated-at.bofh.it>
[not found] ` <6px8R-Y7-43@gated-at.bofh.it>
[not found] ` <6pxV5-2ci-13@gated-at.bofh.it>
[not found] ` <6pz12-3Rg-67@gated-at.bofh.it>
[not found] ` <6pzX4-5jE-19@gated-at.bofh.it>
[not found] ` <6pA6B-5K8-33@gated-at.bofh.it>
2006-06-20 14:39 ` Bodo Eggert
2006-06-20 18:03 ` Russell King
2006-06-20 23:20 ` Bodo Eggert
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=20060619184706.GH3479@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=rankincj@yahoo.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