[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m1ps8qzpte.fsf@ebiederm.dsl.xmission.com>
Date: Sat, 03 Feb 2007 18:14:53 -0700
From: ebiederm@...ssion.com (Eric W. Biederman)
To: "Adam Kropelin" <akropel1@...hester.rr.com>
Cc: "Auke Kok" <auke-jan.h.kok@...el.com>,
"Adrian Bunk" <bunk@...sta.de>,
"Linus Torvalds" <torvalds@...ux-foundation.org>,
"Andrew Morton" <akpm@...ux-foundation.org>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
<jgarzik@...ox.com>, <alan@...rguk.ukuu.org.uk>,
"Allen Parker" <parker@...hunt.com>, <jesse.brandeburg@...el.com>,
<gregkh@...e.de>, <linux-pci@...ey.karlin.mff.cuni.cz>,
<netdev@...r.kernel.org>
Subject: Re: 2.6.20-rc7: known regressions (v2) (part 1)
"Adam Kropelin" <akropel1@...hester.rr.com> writes:
>> Can I get the corresponding lspci -xxx output. I suspect the BIOS
>> did not program the hypertransport MSI mapping capabilities correctly.
>> All it has to do is set the enable but still, occasionally BIOS
>> writers miss the most amazing things.
>
> Here you go. This is from 2.6.20-rc7.
Thanks. Conclusion. I could not find bit 16 (the enable bit) set in any of
your hypertransport msi mapping capabilities.
So MSI interrupts won't work until someone enables your chipset
to transform them into hypertransport interrupts.
Ideally it is a BIOS issue, but it may be the kind of thing we can
fix up with quirks in the kernel.
Eric
-
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