[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080620153626.GE17373@elte.hu>
Date: Fri, 20 Jun 2008 17:36:26 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Kevin Winchester <kjwinchester@...il.com>
Cc: Ingo Molnar <mingo@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Yinghai Lu <yhlu.kernel@...il.com>,
"Rafael J. Wysocki" <rjw@...k.pl>, Pavel Machek <pavel@....cz>
Subject: Re: Bisecting tip/auto-x86-next?
* Kevin Winchester <kjwinchester@...il.com> wrote:
> > hm, could you send me the config that triggered this?
>
> I will do so tonight when I am home again. It is a UP AMD64 box with
> a VIA chipset, if that helps.
>
> > btw., you can probably ignore this one safely. Also please tell me
> > at which commit ID you were at when you triggered this warning.
>
> Good to know - I will get the commit ID tonight as well, although
> wouldn't following the same bisection sequence that I did give you the
> same bisection point? I guess that would assume that linus/master and
> auto-x86-next haven't changed much since last night, which might not
> be correct.
yeah, you'd probably not hit that warning with the x86/gart bisection
sequence. (Assuming the bug is introduced in that branch - so you should
first check whether pure x86/gart kernel triggers the problem too.)
If you still have the commit ID around then please send it - if you
dont, no problem, it's no big issue. I wanted to check how wide the
bisection window is where the warning triggers.
Ingo
--
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