From: Adam Belay <ambx1@neo.rr.com>
To: Wes Janzen <superchkn@sbcglobal.net>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.0-test3-mm3 reserve IRQ for isapnp
Date: Wed, 20 Aug 2003 22:33:44 +0000 [thread overview]
Message-ID: <20030820223344.GA10163@neo.rr.com> (raw)
In-Reply-To: <3F440387.5090902@sbcglobal.net>
On Wed, Aug 20, 2003 at 06:25:59PM -0500, Wes Janzen wrote:
> So sad... Ever since I started with kernel 2.5.69, the kernel has been
> properly reserving IRQ 5 for ISA, as set in my BIOS.
The reserve IRQ feature in your BIOS should not effect the linux kernel.
It is strictly internal to your BIOS. Therefore if linux assigns
resources it probably won't reserve irq 5. This problem may be the
result of a change in the way linux assigns resources.
>
> Unfortunately for me, it looks like 2.6.0-test3-mm3 is like 2.4.18 and
In what kernel version did you first see this problem?
> ignores my BIOS settings, so it locks up trying to ativate my SB16 on
> boot (since IRQ 5 is used for IDE). Oddly it doesn't spit out any
> warnings, just locks up after "pnp: Device 00:01.03 activated".
I'd imagine this is the result of the resource conflict, presumably with
your ide controller. More information would be needed. I'd like to see
/proc/interrupts, dmesg, and lspci -vv (when the sb driver is not loaded).
Also, are you using acpi? If so, try the kernel parameter pci=noacpi and
also try disabling acpi completely.
Thanks,
Adam
next prev parent reply other threads:[~2003-08-21 2:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-20 23:25 2.6.0-test3-mm3 reserve IRQ for isapnp Wes Janzen
2003-08-20 22:33 ` Adam Belay [this message]
2003-08-21 4:26 ` Wes Janzen
2003-08-21 9:57 ` 2.6.0-test3-mm3 reserve IRQ for isapnp (2.6.0-test3-mm3 <sigh>) Wes Janzen
2003-08-21 10:23 ` Thomas Schlichter
2003-08-21 12:01 ` Wes Janzen
2003-08-21 14:47 ` Thomas Schlichter
2003-08-21 23:30 ` Wes Janzen
2003-08-21 5:55 ` 2.6.0-test3-mm3 reserve IRQ for isapnp Wes Janzen
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=20030820223344.GA10163@neo.rr.com \
--to=ambx1@neo.rr.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=superchkn@sbcglobal.net \
/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