[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.00.0812021237310.3256@nehalem.linux-foundation.org>
Date: Tue, 2 Dec 2008 12:40:27 -0800 (PST)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Alejandro Riveira Fernández
<ariveira@...il.com>
cc: Al Viro <viro@...iv.linux.org.uk>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Dmitry Baryshkov <dbaryshkov@...il.com>,
Alistair John Strachan <alistair@...zero.co.uk>,
"Michael B. Trausch" <mike@...usch.us>
Subject: Re: Linux 2.6.28-rc7
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
--
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