public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Andi Kleen <ak@suse.de>
Cc: discuss@x86-64.org, torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [discuss] Re: Please pull x86-64 bug fixes
Date: Thu, 05 Oct 2006 13:43:56 -0400	[thread overview]
Message-ID: <4525445C.6060901@garzik.org> (raw)
In-Reply-To: <200610051931.23884.ak@suse.de>

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.


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

AFAICS it's a buggy check, since it continues to needlessly blacklist 
working boxes.

My proposal is quite simple:  "something that works" -- the current 
solution obviously does not.

	Jeff



  reply	other threads:[~2006-10-05 17:44 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-05 17:10 Please pull x86-64 bug fixes Andi Kleen
2006-10-05 17:17 ` Jeff Garzik
2006-10-05 17:31   ` [discuss] " Andi Kleen
2006-10-05 17:43     ` Jeff Garzik [this message]
2006-10-05 17:53       ` Andi Kleen
2006-10-05 19:29         ` Jeff Garzik
2006-10-05 19:42           ` Andi Kleen
2006-10-05 20:02             ` Jeff Garzik
2006-10-05 20:10               ` Andi Kleen
2006-10-05 22:45               ` Linus Torvalds
2006-10-05 22:52                 ` Andi Kleen
2006-10-05 23:07                   ` Linus Torvalds
2006-10-05 23:21                     ` Andi Kleen
2006-10-05 23:36                     ` Jeff Garzik
2006-10-06  0:57                     ` Jeff Garzik
2006-10-06  1:29                       ` Linus Torvalds
2006-10-06 11:03                 ` Arjan van de Ven
2006-10-06 16:07                   ` Linus Torvalds
2006-10-06 16:19                     ` Arjan van de Ven
2006-10-06 22:01                     ` Rafael J. Wysocki
2006-10-06 22:31                       ` Duran, Leo
2006-10-06 23:06                         ` Jeff Garzik
2006-10-07  5:23                           ` Arjan van de Ven
2006-10-07  2:20                         ` Linus Torvalds
2006-10-08 20:59                           ` Duran, Leo
2006-10-08 22:42                             ` Linus Torvalds
2006-10-05 22:00         ` Alan Cox
2006-10-05 21:44           ` Andi Kleen
2006-10-06 11:14             ` Alan Cox
2006-10-16 12:21               ` Andi Kleen
2006-10-05 17:21 ` Linus Torvalds
2006-10-05 17:27   ` [discuss] " Andi Kleen
2006-10-05 22:59     ` Linus Torvalds
2006-10-05 23:05       ` Andi Kleen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4525445C.6060901@garzik.org \
    --to=jeff@garzik.org \
    --cc=ak@suse.de \
    --cc=discuss@x86-64.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox