[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47645963.9060202@zytor.com>
Date: Sat, 15 Dec 2007 14:46:59 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Allen Martin <AMartin@...dia.com>
CC: Alan Cox <alan@...rguk.ukuu.org.uk>,
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.
Allen Martin wrote:
>
> Nothing inside the chipset should be decoding port 80 writes. It's
> possible this board has a port 80 decoder wired onto the board that's
> misbehaving. I've seen other laptop boards with port 80 decoders
> wired onto the board, even if the 7 segment display is only populated
> on debug builds.
>
> We use PCI port 80 decoders internally for debugging quite often, so
> if there were some chipset issue related to port 80 it would have
> showed up a long time ago, and this is the first I've heard of
> hangs related to port 80 writes.
>
Presumably you have programmable decoders to trigger SMI? If not, then
they're probably doing the equivalent in a SuperIO chip or similar.
-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