mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: "Alejandro Riveira Fernández" <ariveira@gmail.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Dmitry Baryshkov <dbaryshkov@gmail.com>,
	Alistair John Strachan <alistair@devzero.co.uk>,
	"Michael B. Trausch" <mike@trausch.us>
Subject: Re: Linux 2.6.28-rc7
Date: Tue, 2 Dec 2008 12:40:27 -0800 (PST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0812021237310.3256@nehalem.linux-foundation.org> (raw)
In-Reply-To: <20081202204503.57363502@varda>



On Tue, 2 Dec 2008, Alejandro Riveira Fernández wrote:
> 
>  Well i already sent the result of the revert on another mail;
> it did not help :(

Ahh. Oh, well.

>  I tried again with what i thought was my "good" commit and the
> bug is there too :/
> 
>  could it be that something changed in userspace[1] between the
> day i installed the 2.6.28-rc6-00007-ged31348 and today that
> make this bug trigger?

Sure, that's possible. It happens occasionally with updated user-land 
binaries, especially system-related ones (eg something like X or SElinux 
or whatever).

Or perhaps a configuration change meant that if you recompiled the "good" 
kernel, you now recompiled a different config? Or did you re-use the exact 
same kernel image you had originally?

>  Next step is try to find an "actually good" kernel and bisect
> again sigh... 2.6.27.6 seems to work ok

Ok, that's a much bigger bisection thing, but again, even just narrowing 
it down a bit will help. But check the configuration too before you start.

			Linus

  reply	other threads:[~2008-12-02 20:41 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-02  4:11 Linus Torvalds
2008-12-02 12:14 ` Alejandro Riveira Fernández
2008-12-02 13:11   ` pazke
2008-12-02 14:48     ` Alejandro Riveira Fernández
2008-12-02 15:20       ` Alistair John Strachan
2008-12-02 15:50         ` Alejandro Riveira Fernández
2008-12-02 16:14           ` Alistair John Strachan
2008-12-02 15:54         ` Alejandro Riveira Fernández
2008-12-02 15:50   ` Linus Torvalds
2008-12-02 15:56     ` Alejandro Riveira Fernández
2008-12-02 16:13       ` Linus Torvalds
2008-12-02 16:29         ` About git-bisect (was: Linux 2.6.28-rc7) Renato S. Yamane
2008-12-02 16:55           ` Sam Ravnborg
2008-12-02 17:05             ` Linus Torvalds
2008-12-02 17:01           ` Linus Torvalds
2008-12-02 18:49         ` Linux 2.6.28-rc7 Alejandro Riveira Fernández
2008-12-02 19:22           ` Alejandro Riveira Fernández
2008-12-02 19:23           ` Linus Torvalds
2008-12-02 19:45             ` Alejandro Riveira Fernández
2008-12-02 20:40               ` Linus Torvalds [this message]
2008-12-02 20:29             ` Al Viro
     [not found] <fa.IDjfwzrT2B02+NHfmYwtICnzOOA@ifi.uio.no>
     [not found] ` <fa.J8MFTCUT8El3sK8BuYDBvaMRaB8@ifi.uio.no>
     [not found]   ` <fa.q/4H3AtoJGSJ+i8tlXR4X35LFFU@ifi.uio.no>
     [not found]     ` <fa.98CeSgxJ/GGaLLyZ97s1oHgh7hE@ifi.uio.no>
2008-12-02 17:11       ` Michael B. Trausch
2008-12-02 18:06         ` Alejandro Riveira Fernández
2008-12-02 18:56           ` Michael B. Trausch

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=alpine.LFD.2.00.0812021237310.3256@nehalem.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=alistair@devzero.co.uk \
    --cc=ariveira@gmail.com \
    --cc=dbaryshkov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike@trausch.us \
    --cc=viro@zeniv.linux.org.uk \
    /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

Powered by JetHome