Re: 2.6.17-mm6
From: Alistair John Strachan
Date: Sat Jul 08 2006 - 12:02:14 EST
On Friday 07 July 2006 21:48, Alistair John Strachan wrote:
[snip]
> > > I don't think it's John's code. I commented out the sysfs registration
> > > code from timekeeping_init_device() and the kernel gets further, where
> > > it crashes on kmem_cache_create. SLAB also complains about "losing its
> > > name" and being "of size 0".
> > >
> > > This happens identically on 2.6.18-rc1, and 2.6.17-mm6. Greg, could it
> > > be anything you've changed recently? I considered bisectioning -mm, but
> > > there's been a lot of RAID problems and I'm using RAID5.
> >
> > Please bisect 2.6.18-rc1 if you have git, as the problem is there, and
> > would be good to track down.
>
> I tried this, but it's extremely difficult when the kernel boots
> successfully one every four times. I've already been thrown off the scent
> twice, bringing my bisection count to 25..
>
> I think I'll try an allnoconfig on this machine, hopefully that will boot,
> then I just start enabling things again until it breaks.
Sorry, this turned out to be my fault.
GCC had just recently been upgraded to 4.1.1, which apparently silently
generates bad kernels with the version of H. J. Lu's binutils I had
installed. I figured it out when going back to 2.6.17 didn't help. Why the
crashes were sporadic I will never truly understand.
Going back to GNU binutils 2.17 and rebuilding GCC 4.1.1 fixed it. At least I
learnt how to use Git, which is a truly superb tool. I'm now happily
running -mm6.
--
Cheers,
Alistair.
Final year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/