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, 24 Feb 2010 21:30:33 +0800
From:	"Huang, Shane" <Shane.Huang@....com>
To:	"Robert Hancock" <hancockrwd@...il.com>,
	"Yuhong Bao" <yuhongbao_386@...mail.com>
CC:	<greg@...ah.com>, <linux-kernel@...r.kernel.org>,
	<linux-ide@...r.kernel.org>, <tj@...nel.org>,
	"Huang, Shane" <Shane.Huang@....com>
Subject: RE: SB600 64-bit DMA BIOS misconfiguration (formerly RE: [PATCH 2.6.34] ehci-hcd: add option to enable 64-bit DMA support)

Hi Robert and Yuhong,

> >> it doesn't work. Based on the libata experience with AHCI which has
a
> >> similar 64-bit feature flag, there are some controllers that didn't
do
> >> it properly, but not many (only ATI SB600 it appears, and only on
> >> certain boards, as it seems it was a BIOS configuration issue).
> > It seems it was solved by a DMI whitelist, but if it is a BIOS
configuration issue, I think it would be better if it could be detected
directly
> instead by reading the configuration directly from the device and
correcting it if possible. Is that possible?
> 
> That would likely be the ideal solution, but only AMD would likely
> have the info needed to do that, if it's possible..

Yes, I did see SB600 64 bit DMA issue on several SB600 platforms,
especially the SATA controller and HD audio controller.
But we do not know the root cause, which seems to be BIOS related
after debug. So far what I know is:

1. The 64bit DMA issue only appears on few SB600 platforms, while
We do NOT see it on SB700, SB800 and our own SB600 reference boards.

2. According to the debug to ASUS M2A-VM SATA controller, some
BIOS change between version 1404 and 1501 lead to the issue:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commi
t;h=58a09b38cfcd700b796ea07ae3d2e0efbb28b561

3. I do not get any related SB600 errata or known issue confirmation
from our HW team, we do not think it is HW issue.

So I do not have too much suggestion but one:
If you have any contact window to ASUS, is it possible for you to
ask ASUS to check the difference between 1404 and 1501?
We might get clue from the change list.


Thanks,
Shane


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

Powered by Openwall GNU/*/Linux Powered by OpenVZ