linux-kernel - Re: More info on port 80 symptoms on MCP51 machine.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 12 Dec 2007 21:58:25 +0100
From:	Rene Herman <rene.herman@...il.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
CC:	"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>,
	"H. Peter Anvin" <hpa@...or.com>, 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.

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...

Summary:

Unless after booting with "acpi=off", outputs to port 0x80 (the legacy way 
to delay I/O) reliably, but not immediately, hang MCP51 machines. Outputs to 
port 0xed do not indicating it's a not a generic bus abort problem.

Rene.
--
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/