Re: Bisects that are neither good nor bad

[Paul Dickson <dickson@permanentmail.com>]

On Sun, 28 May 2006 15:02:08 -0700, Paul Dickson wrote:

> On Sun, 28 May 2006 23:24:12 +0200, Rafael J. Wysocki wrote:
> 
> > On Sunday 28 May 2006 23:08, Paul Dickson wrote:
> > > On Sun, 28 May 2006 14:02:38 -0700, Paul Dickson wrote:
> > > 
> > > > Building and testing a good kernel takes me about 70 minutes.  If I make
> > > > mistakes it can easily take two times (or more!) longer.
> > > >
> > > > I'm currently tracking my work at:
> > > >     https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=185108
> > > >
> > > > I'm currently building my fifth bisect.
> > 
> > Could you please also try if the problems persist if you boot with
> > init=/bin/bash?
> 
> I'll try it after I send this message.  I'm guessing you're refering to
> my third bisect.  I still have that and will use it.

The switchroot in the initrd can't find the ext3 root fs.  So no root
found and bash couldn't be found.  This is the third bisect.  All of this
is because of a compiler warning in ext3 and reiserfs.  If I recall
correctly, something like "generic_slice_[...](?) uninitialized".


> I may try sshing into my notebook when I finish these current bisect
> tests to see if it's still the HD being made RO.  This is assuming ssh
> will keep the connection through a suspend.

While ssh retains a connection on a good kernel.  It gets no response
from a bad kernel.

	-Paul