Ken Moffat wrote: > On 13 May 2010 23:53, Ken Moffat <zarniwhoo...@googlemail.com> wrote: >> Â So, it's actually init that segfaults ? Â I suppose that makes sense, >> I think the kernel is privileged enough to do what it wants. Â I must >> admit, when I read your original post I assumed you meant it was >> panicking. >> > Hmm, I can now confirm that it does panic after init segfaults (2.6.34-rc7, > -rc5 and gcc-4.4 were working, x86_64). I built a minimal gcc-4.5 (C only) > and installed it in /opt/kgcc. So, everything else was compiled with the > complier from LFS-6.6. > > copied by hand - > Freeing unused kernel memory: 528k free > INIT: version 2.86 booting > segfault at fffffff810076019 ip ffffffff810076a9 sp 00007fff9db4 57f8 error 15 > [ above line repeated ] > Kernel panic - not syncing: Attempted to kill init!
At least we have confirmation. > I blame gcc-4.5. Me too, but I got a little further by disabling # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set > Related question, although maybe it belongs on support - how do you > get grub2 (1.97, if it matters) to boot in single mode? I need to fsck > my /home partition manually (fsck'd after nn boots, came up with > errors), and it's shared between all the systems on that box. > > init=/bin/bash works, but (of course) no disk devices. > > adding 'single' or '1' or 'init 1' to the end of the grub command line is > ineffective. So, for the moment that box is out of use until I can find my > rescue CD. Never had this problem with lilo, grumble, grumble :-( AFAIK, from the menu, go to the command line: c grub> linux /linux-kernel root=/dev/sda(whatever) single grub> boot If it starts to boot, it's not a grub problem. Note that it does have tab completion for setting the kernel filename. -- Bruce -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page