public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>, Pavel Machek <pavel@ucw.cz>,
	Thomas Gleixner <tglx@linutronix.de>, "H. Anvin" <hpa@zytor.com>,
	Arjan van de Ven <arjan@infradead.org>,
	Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: [rfc] hw resource debugging checks (was: Re: x86 git tree broken (bisected))
Date: Sun, 13 Apr 2008 11:19:21 +0200	[thread overview]
Message-ID: <20080413091921.GD28693@elte.hu> (raw)
In-Reply-To: <86802c440804130118n669db8d1rf37551550955a084@mail.gmail.com>


* Yinghai Lu <yhlu.kernel@gmail.com> wrote:

> =====> just sent out one patch to work around that

yep, just applied that one.

> also BIOS is sick to allocate overlapping MMIO to the same link..
> 
> node 0 link 0: io port [1000, ffffff]
> TOM: 0000000080000000 aka 2048M
> node 0 link 0: mmio [e0000000, efffffff]
> node 0 link 0: mmio [a0000, bffff]
> node 0 link 0: mmio [80000000, ffffffff]
> bus: [00,ff] on node 0 link 0
> 
> never thought that BIOS could be so sick.
>  ===> already have one work around, need more test next week.

great!

basically any and all sickness should be assumed both by the hardware 
and by the BIOS, _and_ by Linux architecture code as well as it passes 
stuff to the generic driver layers. So as resources get set up we should 
have resilience all the way and should be on the lookout for signs of 
bugs - because breakages are so hard to track down in this area if they 
go unnoticed during setup.

	Ingo

  reply	other threads:[~2008-04-13  9:20 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-10 19:59 x86 git tree broken Rafael J. Wysocki
2008-04-10 20:13 ` Ingo Molnar
2008-04-10 20:25   ` Rafael J. Wysocki
2008-04-10 20:29     ` Ingo Molnar
2008-04-10 20:38       ` Ingo Molnar
2008-04-10 22:28         ` Rafael J. Wysocki
2008-04-11 19:26           ` x86 git tree broken (bisected) Rafael J. Wysocki
2008-04-11 20:23             ` Rafael J. Wysocki
2008-04-11 20:29               ` Rafael J. Wysocki
2008-04-11 20:26             ` Yinghai Lu
2008-04-11 20:51               ` Rafael J. Wysocki
2008-04-11 21:11                 ` Yinghai Lu
2008-04-11 21:21                   ` Rafael J. Wysocki
2008-04-11 21:31                     ` Yinghai Lu
2008-04-13  8:24                 ` Yinghai Lu
2008-04-13  8:41                   ` Yinghai Lu
2008-04-13 16:14                     ` Rafael J. Wysocki
2008-04-14  9:02                       ` Ingo Molnar
2008-04-13 16:12                   ` Rafael J. Wysocki
2008-04-13 18:07                     ` Yinghai Lu
2008-04-13 18:47                       ` Rafael J. Wysocki
2008-04-13 18:53                         ` Yinghai Lu
2008-04-13 18:54                         ` Yinghai Lu
2008-04-13 22:00                     ` Yinghai Lu
2008-04-13 22:10                       ` Rafael J. Wysocki
2008-04-13 22:32                         ` Yinghai Lu
2008-04-13 23:41                           ` Rafael J. Wysocki
2008-04-13 23:45                             ` H. Peter Anvin
2008-04-14  0:09                               ` Rafael J. Wysocki
2008-04-14  0:12                                 ` H. Peter Anvin
2008-04-14  0:19                           ` Rafael J. Wysocki
2008-04-14  1:42                             ` Yinghai Lu
2008-04-14  9:16                               ` Ingo Molnar
2008-04-14 18:08                                 ` Yinghai Lu
2008-04-14 20:21                               ` Rafael J. Wysocki
2008-04-14 21:06                                 ` Yinghai Lu
2008-04-14 21:09                                   ` Rafael J. Wysocki
2008-04-14 21:36                                     ` Yinghai Lu
2008-04-13  7:51               ` Ingo Molnar
2008-04-13  7:59                 ` Yinghai Lu
2008-04-13  7:58             ` [rfc] hw resource debugging checks (was: Re: x86 git tree broken (bisected)) Ingo Molnar
2008-04-13  8:18               ` Yinghai Lu
2008-04-13  9:19                 ` Ingo Molnar [this message]
2008-04-13  9:39               ` [rfc] hw resource debugging checks Andi Kleen
2008-04-13 17:53                 ` Arjan van de Ven
2008-04-13 18:19                 ` Yinghai Lu
2008-04-13 18:29                   ` Andi Kleen
2008-04-13 19:29                     ` Yinghai Lu
2008-04-14  3:52                       ` Arjan van de Ven
2008-04-14  5:01                         ` Yinghai Lu
2008-04-14 14:12                           ` Arjan van de Ven
2008-04-14 18:11                             ` Yinghai Lu
2008-04-13 15:48               ` [rfc] hw resource debugging checks (was: Re: x86 git tree broken (bisected)) Arjan van de Ven
2008-04-10 20:51 ` x86 git tree broken Ingo Molnar
2008-04-10 22:27   ` Rafael J. Wysocki
2008-04-11  6:43     ` Ingo Molnar

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=20080413091921.GD28693@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=gregkh@suse.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    --cc=tglx@linutronix.de \
    --cc=yhlu.kernel@gmail.com \
    /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