From: Ed Tomlinson <tomlins@cam.org>
To: ebiederm@xmission.com (Eric W. Biederman)
Cc: linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>
Subject: Re: [PATCH] kexec for 2.5.51....
Date: Sat, 14 Dec 2002 18:59:07 -0500 [thread overview]
Message-ID: <200212141859.07191.tomlins@cam.org> (raw)
In-Reply-To: <m14r9gv1c8.fsf@frodo.biederman.org>
On December 14, 2002 02:37 pm, Eric W. Biederman wrote:
>
> Hurray! a bug report :)
Feels good huh.
> > One other datum. Without the --append line a kernel booted with kexec
> > hangs when
> >
> > tring to mount the real root - it cannot find the device.
>
> I suspect you want to specify --append="root=/dev/xyz" when calling kexec.
This helps - see below.
> > Am I using kexec correctly? What else can I try? Is there any debug
> > info I can gather?
>
> Generally you want to put kexec -e your shutdown scripts just before
> the call to reboot. And then you can just say: kexec ...
> and the you get a clean system shutdown. Dropping to run level 1
Why not include this info in kexec -h ? Bet it would prevent a few
failure reports...
> before calling kexec tends to get most of the user space shutdown
> called as well. It is definitely a good idea to be certain X is
> shutdown before calling kexec.
droping to init 1, then calling kexec -e (with the root= and the rest
of the appended parms) works and boots 2.5.51 just fine. <grin>
Two more possible additions to the kexec command.
1. kexec -q which returns rc=1 and types the pending selection and
its command/append string if one exists and returns rc=0 if nothing
is pending.
2. kexec -c which clears any pending kernels.
> With respect to USB it is quite possible something in the USB drivers
> does not shutdown correctly on a reboot, and the driver then has trouble
> reinitializing the device.
Very possible since I did not do an init 0/1/6 before the kexec -e. Usb
was probably being asked to do something very unexpected...
> Since you got to the point of mounting root earlier when you did not
> specify anything I wonder if you some of your command line arguments
> made the situation worse.
>
> Which kernel are you booting with kexec anyway?
2.5.51 + fbcon(bk) + usb(bk) + kexec
> This is actually an expected failure mode, but one I have not seen
> much of yet. The new kernel not coming up because the old drivers
> left the hardware in a state the new drivers cannot handle
> Greg kh asked:
>Could you enable CONFIG_USB_DEBUG to hopefully see more debugging
>messages from the uhci driver during boot, so we could narrow this down?
Done. I will see if I get this to reoccur and will send you debug
output.
TIA,
Ed Tomlinson
next prev parent reply other threads:[~2002-12-14 23:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-14 17:15 [PATCH] kexec for 2.5.51 Ed Tomlinson
2002-12-14 19:37 ` Eric W. Biederman
2002-12-14 23:59 ` Ed Tomlinson [this message]
2002-12-15 21:03 ` Eric W. Biederman
2002-12-15 21:41 ` Ed Tomlinson
2002-12-16 0:41 ` Eric W. Biederman
2002-12-14 19:49 ` Greg KH
[not found] ` <200212172243.52786.tomlins@cam.org>
[not found] ` <20021218054802.GF28629@kroah.com>
2003-01-13 3:42 ` usb mouse and 2.5.56bk Ed Tomlinson
2003-01-14 1:23 ` Greg KH
2003-01-14 13:44 ` Ed Tomlinson
2003-01-15 8:02 ` Greg KH
[not found] ` <mailman.1042429501.18263.linux-kernel2news@redhat.com>
2003-01-13 19:06 ` Pete Zaitcev
2003-01-13 19:26 ` Joshua M. Kwan
-- strict thread matches above, loose matches on Subject: below --
2002-12-14 8:26 [PATCH] kexec for 2.5.51 Eric W. Biederman
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=200212141859.07191.tomlins@cam.org \
--to=tomlins@cam.org \
--cc=ebiederm@xmission.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).