From: ebiederm@xmission.com (Eric W. Biederman)
To: "Venkatesan, Ganesh" <ganesh.venkatesan@intel.com>
Cc: <jgarzik@pobox.com>,
"Chilakala, Mallikarjuna" <mallikarjuna.chilakala@intel.com>,
<netdev@oss.sgi.com>, <fastboot@osdl.org>
Subject: Re: e1000: driver reboot/kexec bug.
Date: 17 Feb 2005 12:53:05 -0700 [thread overview]
Message-ID: <m1sm3v55ge.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <468F3FDA28AA87429AD807992E22D07E044A15C5@orsmsx408>
"Venkatesan, Ganesh" <ganesh.venkatesan@intel.com> writes:
> >Do you know enough about kexec to attempt to reproduce this problem
> >that way?
>
> Not much. All I have is an old paper by Andy Pfiffer. Could you point me
> to more resources on this?
Short explanation:
The user space lives at:
http://www.xmission.com/~ebiederm/files/kexec/kexec-tools-1.101.tar.gz
Other bits and pieces can be found at:
http://www.xmission.com/~ebiederm/files/kexec/
The latest patches are in the -mm tree.
Usually it is as simple as:
/sbin/kexec -l /path/to/bzImage --append='your command line options'
Then drop to single user mode and do:
/sbin/kexec -e
My patches have not made into the initscripts yet so doing a clean system
shutdown has not been fully automated yet.
i386 and x86-64 architectures should both work.
Not it is a matter of slowing digging into the hardware support code and
getting out the bugs that are revealed.
Eric
next prev parent reply other threads:[~2005-02-17 19:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-17 18:33 e1000: driver reboot/kexec bug Venkatesan, Ganesh
2005-02-17 19:53 ` Eric W. Biederman [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-17 17:04 Venkatesan, Ganesh
2005-02-17 17:02 Venkatesan, Ganesh
2005-02-17 17:57 ` Eric W. Biederman
2005-02-15 21:24 [PATCH net-drivers-2.6 0/10] e1000: driver update Malli Chilakala
2005-02-16 12:25 ` e1000: driver reboot/kexec bug 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=m1sm3v55ge.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=fastboot@osdl.org \
--cc=ganesh.venkatesan@intel.com \
--cc=jgarzik@pobox.com \
--cc=mallikarjuna.chilakala@intel.com \
--cc=netdev@oss.sgi.com \
/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).