netdev
[Top] [All Lists]

Re: e1000: driver reboot/kexec bug.

To: "Venkatesan, Ganesh" <ganesh.venkatesan@xxxxxxxxx>
Subject: Re: e1000: driver reboot/kexec bug.
From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
Date: 17 Feb 2005 12:53:05 -0700
Cc: <jgarzik@xxxxxxxxx>, "Chilakala, Mallikarjuna" <mallikarjuna.chilakala@xxxxxxxxx>, <netdev@xxxxxxxxxxx>, <fastboot@xxxxxxxx>
In-reply-to: <468F3FDA28AA87429AD807992E22D07E044A15C5@orsmsx408>
References: <468F3FDA28AA87429AD807992E22D07E044A15C5@orsmsx408>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.2
"Venkatesan, Ganesh" <ganesh.venkatesan@xxxxxxxxx> 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





<Prev in Thread] Current Thread [Next in Thread>