linux-kernel - RE: data corruption with nvidia chipsets and IDE/SATA drives (k8 cpu errata needed?)

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]

Message-ID: <DBFABB80F7FD3143A911F9E6CFD477B00E48D54B@hqemmail02.nvidia.com>
Date:	Tue, 16 Jan 2007 13:54:31 -0800
From:	"Allen Martin" <AMartin@...dia.com>
To:	"Chris Wedgwood" <cw@...f.org>,
	"Christoph Anton Mitterer" <calestyo@...entia.net>
Cc:	"Robert Hancock" <hancockr@...w.ca>,
	<linux-kernel@...r.kernel.org>, <knweiss@....de>, <ak@...e.de>,
	<andersen@...epoet.org>, <krader@...ibm.com>,
	"Lonni Friedman" <lfriedman@...dia.com>,
	"Linux-Nforce-Bugs" <Linux-Nforce-Bugs@...dia.com>
Subject: RE: data corruption with nvidia chipsets and IDE/SATA drives (k8 cpu errata needed?)

> I'd like to here from Andi how he feels about this?  It seems like a
> somewhat drastic solution in some ways given a lot of hardware doesn't
> seem to be affected (or maybe in those cases it's just really hard to
> hit, I don't know).
> 
> > Well we can hope that Nvidia will find out more (though I'm not too
> > optimistic).
> 
> Ideally someone from AMD needs to look into this, if some mainboards
> really never see this problem, then why is that?  Is there errata that
> some BIOS/mainboard vendors are dealing with that others are not?

NVIDIA and AMD are ivestigating this issue, we don't know what the
problem is yet.
-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information.  Any unauthorized review, use, disclosure or distribution
is prohibited.  If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------
-
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/