From: Dominik Brodowski <devel@brodo.de>
To: Pavel Machek <pavel@suse.cz>
Cc: ACPI mailing list <acpi-devel@lists.sourceforge.net>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [ACPI] 2.5.10+ acpi0419 breakage
Date: Sun, 28 Apr 2002 23:30:24 +0200 [thread overview]
Message-ID: <02042823302401.01233@sonnenschein> (raw)
In-Reply-To: <20020428110630.GA702@elf.ucw.cz> <02042822313402.00870@sonnenschein> <20020428215046.A275@elf.ucw.cz>
Hi Pavel,
On Sunday, 28. April 2002 21:50, Pavel Machek wrote:
> I don't know. How can I find out if it has IOAPIC.
<snip>
> ACPI: Using PIC for interrupt routing
either from this line [reliably when using pciirq.12 from
http://www.brodo.de/english/pub/acpi/pci_irq/ on], or a dmesg | grep IOAPIC
should show something... your system uses a PIC, though.
<snip>
> acpi_bus-0288 [296] acpi_bus_get_device : Error getting context for
> object [c3eef698] pci_root-0201 [295] acpi_pci_get_link_for_: Invalid IRQ
> router
A problem either in the ACPI tables, in the parsing code or in the
higer-level stuff. Probably the first... but could you please re-try the next
acpi-release, and if it doesn't work then, re-send this bug report? The
function the error occurs in is completely re-written, so things might
(hopefully) change. Thanks.
> > Could you please try the pciirq.9.acpi.diff or -even better- pciirq.12,
> > available at
> > http://www.brodo.de/english/pub/acpi/pci_irq/
> >
> > The assignation of non-dynamic IRQs is somewhat broken (by me :-( in
> > acpi-20020419, I suspect your systems are affected by that bug. Sorry for
> > that.
>
> Will try if I have time.
Thanks - or wait for the next acpi-release.
Dominik
prev parent reply other threads:[~2002-04-28 21:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-28 11:06 2.5.10+ acpi0419 breakage Pavel Machek
2002-04-28 20:31 ` [ACPI] " Dominik Brodowski
2002-04-28 19:50 ` Pavel Machek
2002-04-28 21:30 ` Dominik Brodowski [this message]
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=02042823302401.01233@sonnenschein \
--to=devel@brodo.de \
--cc=acpi-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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.