Skip to contentSkip to conversation

general protection error:0

DISCUSSION David Newall 2 participants 2 messages Apr 27, 2010 – Apr 29, 2010

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

Hi all,

I'm running Ubuntu Hardy with a 2.6.28 kernel on VirtualBox, and want to simply restart the current kernel (because I'm a kexec noob and that seems a sensible first step.) I've put "break=init" on the command line so it gives me a shell just before pivoting root from the initrd to the hard-disk. I do the kexec -l and kexec -e, the kernel (re)starts, does all of the usual startup things, and drops me back in a shell when it's about to start init (break=init, remember?) At this point, when I try to run almost any command, for example "chroot /root bash", I get "Segmentation fault" with general protection logged in dmesg, for example: "bash[1058] general protection ip:b7f0c425 sb:bfb282f4 error:0" No doubt I'm making a basic mistake, but Google failed to show me what, hence I'm asking here for suggestions.

Has anyone any suggestion?

Thanks,

David

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec

#1 lore raw

David.

Quoted 13 lines

I'm running Ubuntu Hardy with a 2.6.28 kernel on VirtualBox, and want to simply restart the current kernel (because I'm a kexec noob and that seems a sensible first step.) I've put "break=init" on the command line so it gives me a shell just before pivoting root from the initrd to the hard-disk. I do the kexec -l and kexec -e, the kernel (re)starts, does all of the usual startup things, and drops me back in a shell when it's about to start init (break=init, remember?) At this point, when I try to run almost any command, for example "chroot /root bash", I get "Segmentation fault" with general protection logged in dmesg, for
example: "bash[1058] general protection ip:b7f0c425 sb:bfb282f4 error:0" No doubt I'm making a basic mistake, but Google failed to show me what, hence I'm asking here for suggestions.

Quoted 1 line

Has anyone any suggestion?

2.6.28 is pretty old these days. It's unlikely someone here is going to help you debug a kernel that ancient.

Can you retry with current mainline and kexec-tools user space? Also post your full boot log and kexec -l and -e outputs when you hit this problem.

Mikey

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec