From: Michael Neuling <mikey@neuling.org>
To: David Newall <kexec@davidnewall.com>
Cc: kexec@lists.infradead.org
Subject: Re: general protection error:0
Date: Fri, 30 Apr 2010 08:04:03 +1000 [thread overview]
Message-ID: <27864.1272578643@neuling.org> (raw)
In-Reply-To: <4BD72F0D.5010708@davidnewall.com>
David.
> 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?
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
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2010-04-29 22:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 18:38 general protection error:0 David Newall
2010-04-29 22:04 ` Michael Neuling [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=27864.1272578643@neuling.org \
--to=mikey@neuling.org \
--cc=kexec@davidnewall.com \
--cc=kexec@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.