Re: 2.5.68-mm4

Andrew Morton
2003-05-02T21:05:08Z

Steven Cole <elenstev@mesatop.com> wrote:
>
> On Fri, 2003-05-02 at 14:34, Andrew Morton wrote:
> > Steven Cole <elenstev@mesatop.com> wrote:
> > >
> > > For what it's worth, kexec has worked for me on the following
> > > two systems.
> > > ...
> > > 00:03.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 08)
> >
> > Are you using eepro100 or e100? I found that e100 failed to bring up the
> > interface on restart ("failed selftest"), but eepro100 was OK.
>
> CONFIG_EEPRO100=y
> # CONFIG_EEPRO100_PIO is not set
> # CONFIG_E100 is not set
>
> I can test E100 again to verify if that would help.

May as well.

There's something in the driver shutdown which is failing to bring the
device into a state in which the driver startup can start it up. Probably
just a missing device reset. I'll bug Scott about it if we get that far.

> Also, I found that if I mistyped the argument to do-kexec.sh, the
> system would stay up, but the interface would get hosed, fixable with
> /etc/rc.d/init.d/network restart.

Yes, kexec userspace shuts down the network interfaces then tries to exec
the new kernel. But none was loaded and the syscall returns -EINVAL.
You're left with downed interfaces. The script should be checking the
success of the initial image loading.