From: Dominik Brodowski <devel@brodo.de>
To: josh@stack.nl
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] 2.5.8: ACPI: PCI IRQ remapping goes wrong.
Date: Sun, 21 Apr 2002 21:34:25 +0200 [thread overview]
Message-ID: <02042121333100.02835@sonnenschein> (raw)
Jos:
Using IO[S]APIC and ACPI_BOOT is broken in 2.5.8 and the acpi-patches
acpi-20020404 and acpi-20020419. The ACPI SMP booting code is re-worked, and
so this problem should be resolved soon. FYI, acpi-20020419 informs you of
this in a nice kernel panic.
Dominik
On 2002-04-20 8:23:22 Jos Hulzink wrote:
> My SCSI card didn't work anymore, my NIC was unable to connect and my SB
> Live! didn't work anymore. I thought 2.5.8 was a huge mess :)
>
> Anyway: ACPI sets up IRQ remapping to IRQs > 15, but all PCI devices claim
> the old =< 15 IRQ's. My guess is that the ACPI code doesn't update the pci
> irq data.
>
> If it matters: The system I talk about is a dual PII 333, on an Intel LX
> chipset. 2.5.6 did boot fine.
>
> Jos
next reply other threads:[~2002-04-21 19:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-21 19:34 Dominik Brodowski [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-20 8:23 [BUG] 2.5.8: ACPI: PCI IRQ remapping goes wrong Jos Hulzink
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=02042121333100.02835@sonnenschein \
--to=devel@brodo.de \
--cc=josh@stack.nl \
--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