public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Yinghai Lu <yinghai.lu@sun.com>,
	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: [rfc] hw resource debugging checks (was: Re: x86 git tree broken (bisected))
Date: Sun, 13 Apr 2008 09:58:45 +0200	[thread overview]
Message-ID: <20080413075845.GJ20332@elte.hu> (raw)
In-Reply-To: <200804112126.29455.rjw@sisk.pl>


* Rafael J. Wysocki <rjw@sisk.pl> wrote:

> > > btw., Xorg works fine here on a comparable AMD system - but i use 
> > > a rather new distro (Fedora 8) which has Xorg 7.2.
> > 
> > My system is an OpenSUSE 10.3 and it has Xorg 7.2 as well.
> > 
> > I think the problem is somehow related to the Radeon.
> 
> The bisection turned up commit 
> ea1441bdf53692c3dc1fd2658addcf1205629661 "x86: use bus conf in NB conf 
> fun1 to get bus range on, on 64-bit" as the one causing problems.

thanks Rafael for bisecting this!

This was a rather nasty problem - and i'm wondering what else we could 
do to harden our hw resource management code. I'm wondering, is there 
any particular reason why clearly broken resource setup is not detected 
somewhere, automatically, and WARN_ON()-ed about?

for example, in the scheduler code we used to have similar bug patterns 
again and again: architecture code set up scheduler domains incorrectly 
and broke the system in subtle ways. So we added sched_domain_debug() 
which is active under CONFIG_SCHED_DEBUG=y and does a few sanity checks 
and complains if something is wrong. This caught quite a few bugs 
whenever the sched-domains code was modified.

	Ingo

  parent reply	other threads:[~2008-04-13  7:59 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             ` Ingo Molnar [this message]
2008-04-13  8:18               ` [rfc] hw resource debugging checks (was: Re: x86 git tree broken (bisected)) Yinghai Lu
2008-04-13  9:19                 ` Ingo Molnar
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=20080413075845.GJ20332@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=yinghai.lu@sun.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