[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <44F9532C.2020802@goop.org>
Date: Sat, 02 Sep 2006 02:47:24 -0700
From: Jeremy Fitzhardinge <jeremy@...p.org>
To: Jeff Garzik <jeff@...zik.org>
CC: Greg KH <gregkh@...e.de>, Andrew Morton <akpm@...l.org>,
Matthias Hentges <oe@...tges.net>,
linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org,
Venkatesh Pallipadi <venkatesh.pallipadi@...el.com>,
linux-ide@...r.kernel.org,
"Eric W. Biederman" <ebiederm@...ssion.com>
Subject: Re: 2.6.18-rc5-mm1
Jeff Garzik wrote:
>>
>> Reverting them makes the machine work, with basically the same effect
>> as disabling CONFIG_PCI_MSI: no MSI interrupts appear in
>> /proc/interrupts, and e1000 & libata are using IO-APIC-fasteoi. So,
>> a reasonable result for now.
>
> Did you re-enable CONFIG_PCI_MSI, after reverting the patches?
Yes. Er. Hm, perhaps not, it didn't build:
CC drivers/pci/htirq.o
drivers/pci/htirq.c: In function 'ht_create_irq':
drivers/pci/htirq.c:126: error: 'PCI_CAP_ID_HT' undeclared (first use in this function)
drivers/pci/htirq.c:126: error: (Each undeclared identifier is reported only once
drivers/pci/htirq.c:126: error: for each function it appears in.)
I'll try again with CONFIG_HT_IRQ disabled...
J
--
VGER BF report: H 0
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists