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: <200610051953.23510.ak@suse.de>
Date:	Thu, 5 Oct 2006 19:53:23 +0200
From:	Andi Kleen <ak@...e.de>
To:	Jeff Garzik <jeff@...zik.org>
Cc:	discuss@...-64.org, torvalds@...l.org, linux-kernel@...r.kernel.org
Subject: Re: [discuss] Re: Please pull x86-64 bug fixes

On Thursday 05 October 2006 19:43, Jeff Garzik wrote:
> Andi Kleen wrote:
> > On Thursday 05 October 2006 19:17, Jeff Garzik wrote:
> > 
> >> Does this fix the following issue:
> >>
> >> PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved
> >> PCI: Not using MMCONFIG.
> >>
> >> 100% of my x86-64 boxes, AMD or Intel, print this message.  And 100% of 
> >> them work just fine with MMCONFIG.
> > 
> > No. 
> > 
> > But it isn't really a issue. Basically everything[1] will work fine anyways.
> > 
> > [1]  Only thing you're missing AFAIK is PCI Extended Error Reporting.
> 
> Not really true, I have some cards which have >256 bytes of config space.

Yes for advanced error handling (which we only support in a few drivers
right now) I'm not aware of any card that uses it for anything else. Do you 
have evidence of that?

> >> I think this rule is far too drastic for real life.
> > 
> > If you have a better proposal please share. I tried a few others, but none
> > of them could handle all the buggy Intel 9x5 boards that hang on any
> > mmconfig access (so the "try the first few busses" check already hangs)
> > 
> > Originally I thought
> > DMI blacklisting would work, but it's on too many systems for that
> > (and Linus rightfully hated it anyways). ACPI checks also didn't work.
> > I don't know of any others.
> 
> It's a bit disappointing, since I keep getting brand new boxes with 
> brand new BIOSen, but keep hitting this rule.

A lot of new boxes are actually buggy due to a common Intel reference
BIOS bug. There are also a couple of other quirks there.

I suppose it'll only become better once Windows starts using MCFG.
 
> My proposal is quite simple:  "something that works" -- the current 
> solution obviously does not.

If you have a patch that works with all known BIOS bugs (including Mac Mini,
a random Intel 975 board and a Asus AMD K8 board with PCI Express) please share it.

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