[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <48E27E23.20400@keyaccess.nl>
Date: Tue, 30 Sep 2008 21:29:39 +0200
From: Rene Herman <rene.herman@...access.nl>
To: Linus Torvalds <torvalds@...ux-foundation.org>
CC: Bjorn Helgaas <bjorn.helgaas@...com>,
Jesse Barnes <jbarnes@...tuousgeek.org>,
Len Brown <lenb@...nel.org>, Frans Pop <elendil@...net.nl>,
"Rafael J. Wysocki" <rjw@...k.pl>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-pci@...r.kernel.org, linux-acpi@...r.kernel.org,
Adam Belay <abelay@....edu>, Avuton Olrich <avuton@...il.com>,
Karl Bellve <karl.bellve@...ssmed.edu>,
Willem Riede <wriede@...de.org>,
Matthew Hall <mhall@...omputing.net>,
Sam Ravnborg <sam@...nborg.org>
Subject: Re: [patch 2/2] PNP: don't check disabled PCI BARs for conflicts
in quirk_system_pci_resources()
On 30-09-08 19:21, Linus Torvalds wrote:
> It looks like both of these will fall afoul of the fact that ACPI
> currently seems to _expect_ to be called in the old order, ie I get some
> oops in acpi_irq_penalty_init() apparently because it knew that it got
> called later (thanks to being called from pci_acpi_init in the
> arch-specific directory), and knew that the other ACPI subsys setup
> routines had been done before.
Yes, I also get that oops but other than that, both link order versions
you sent out work -- ie, booting with acpi=noirq gets me to a functional
system with the quirk having run for PNP0c02 (acpi=off disables all of
PNP0c02) and doing its job.
For some reason only some of your messages seem to be making it into my
inbox (in order, at least) but either of these that is:
http://lkml.org/lkml/2008/9/30/242
http://lkml.org/lkml/2008/9/30/261
With the attached on top, all's working fine for me.
Rene.
View attachment "quirk_system_pci_resources.diff" of type "text/plain" (2097 bytes)
Powered by blists - more mailing lists