All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Kevin Winchester <kjwinchester@gmail.com>
Cc: Ingo Molnar <mingo@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Yinghai Lu <yhlu.kernel@gmail.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>, Pavel Machek <pavel@ucw.cz>
Subject: Re: Bisecting tip/auto-x86-next?
Date: Fri, 20 Jun 2008 17:36:26 +0200	[thread overview]
Message-ID: <20080620153626.GE17373@elte.hu> (raw)
In-Reply-To: <d1af83620806200437p7c3817d8i381a99f92f47fd4f@mail.gmail.com>


* Kevin Winchester <kjwinchester@gmail.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

  reply	other threads:[~2008-06-20 15:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-20  0:40 Bisecting tip/auto-x86-next? Kevin Winchester
2008-06-20  7:15 ` Sitsofe Wheeler
2008-06-20 10:04 ` Ingo Molnar
2008-06-20 22:23   ` Kevin Winchester
2008-06-20 10:07 ` Ingo Molnar
2008-06-20 10:17 ` Ingo Molnar
2008-06-20 10:49   ` Pavel Machek
2008-06-20 11:40     ` Kevin Winchester
2008-06-20 10:51   ` Rafael J. Wysocki
2008-06-20 11:37   ` Kevin Winchester
2008-06-20 15:36     ` Ingo Molnar [this message]
2008-06-21  0:00       ` Kevin Winchester
2008-06-21  0:14         ` Yinghai Lu
2008-06-21 10:00           ` Kevin Winchester
2008-06-21 10:18             ` Yinghai Lu
2008-06-21 10:23               ` Kevin Winchester
2008-06-21 10:30                 ` Yinghai Lu
2008-06-21 10:39                   ` Kevin Winchester
2008-06-21 10:50                     ` Yinghai Lu
2008-06-21 11:49                       ` Kevin Winchester
2008-06-23 11:12                         ` 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=20080620153626.GE17373@elte.hu \
    --to=mingo@elte.hu \
    --cc=hpa@zytor.com \
    --cc=kjwinchester@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.