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?
Besides, it would be helpful if you were able to get a serial console log
from the failing system.
> Is there a method of bisecting that means neither "good" nor "bad"? I
> have run into kernel problems that are not related to the problem I'm
> attempting to track. Some are not avoidable by changing the .config (see
> the third bisect in comments 10 and 11 in the bugzilla report).
There are lots of patches between 2.6.16-rc* and 2.6.17-rc1, most of them
having stayed in -mm for some time. If you found the first failing -mm kernel,
it would be easier to catch the offending patch.
BTW, have you tried any kernel _after_ 2.6.17-rc1? If not, I'd start from
these.
Greetings,
Rafael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
