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, 04 Mar 2009 19:11:01 +0900
From:	Tejun Heo <tj@...nel.org>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	the arch/x86 maintainers <x86@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...e.hu>,
	pgnet.trash@...il.com
Subject: Re: [PATCH 2.6.29-rc7 2/2] x86: disallow DAC for MCP51 PCI bridge

Alan Cox wrote:
> On Wed, 04 Mar 2009 11:39:15 +0900
> Tejun Heo <tj@...nel.org> wrote:
> 
>> MCP51 corrupts DAC transfers.  Disallow it.  Reported by pgnet on
>> bnc#463829.
> 
> So you have a single piece of evidence as I read it - from a single
> board that represents system with a very common chipset and no supporting
> errata information from the vendor.
> 
> That bug could easily be a faulty motherboard or dodgy connector or a
> specific hardware compatibility issue between two specific components. I
> don't think that can be considered sufficient evidence for adding
> sledgehammer sized workarounds that harm everyone elses performance and
> cripples such systems for certain kinds of work (eg video)
> 
> Insufficient evidence and google searches and other bug searches don't
> seem to be turning up any parallel cases so for the moment At the very
> least someone needs to reproduce the hardware configuration and see the
> same problem, and then repeat with a different DAC enabled card.
> 
> I don't believe this patch should go in ... yet. More information/testing
> is needed.

x86 is blacklisting DAC for everything VIA. :-)

* MCP51 is a very old chipset at this point (it's circa 2005).  Not
  many machine would be running with >4GB memory to begin with.

* Given the above and scarcity of DAC on most end user machines
  (nothing on MCP51 does DAC by default), lack of reports isn't too
  surprising.

* The board doesn't have a 64bit connector.  It can't be dodgy
  connector and sil24 is known to behave well with DAC.  The failure
  being specific to the particular machine doesn't seem likely.

I'll ping nvidia about it but I think your bar is too high.

Thanks.

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