[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 12 Dec 2007 13:12:04 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Alan Cox <alan@...rguk.ukuu.org.uk>
CC: Rene Herman <rene.herman@...il.com>,
"David P. Reed" <dpreed@...d.com>, Pavel Machek <pavel@....cz>,
Andi Kleen <andi@...stfloor.org>,
"linux-os (Dick Johnson)" <linux-os@...logic.com>,
David Newall <david@...idnewall.com>,
Paul Rolland <rol@...917.net>,
Krzysztof Halasa <khc@...waw.pl>, linux-kernel@...r.kernel.org,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, rol@...be.net
Subject: Re: More info on port 80 symptoms on MCP51 machine.
Alan Cox wrote:
> On Wed, 12 Dec 2007 21:58:25 +0100
> Rene Herman <rene.herman@...il.com> wrote:
>
>> On 12-12-07 21:26, Rene Herman wrote:
>>
>>> On 12-12-07 21:07, David P. Reed wrote:
>>>> Someone might have an in to nVidia to clarify this, since I don't. In
>>>> any case, the udelay(2) approach seems to be a safe fix for this machine.
>> By the way, _does_ anyone have a contact at nVidia who could clarify? Alan
>> maybe? I'm quite curious what they did...
>
> I don't. Nvidia are not the most open bunch of people on the planet. This
> doesn't appear to be a chipset bug anyway but a firmware one (other
> systems with the same chipset work just fine).
>
> The laptop maker might therefore be a better starting point.
One wonders if it does some SMM trick to capture port 0x80 writes and
attempt to haul them off for debugging; it almost sounds like some kind
of debugging code got let out into the field.
-hpa
--
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