Messages in this thread | | | Date | Fri, 2 May 2003 14:05:08 -0700 | From | Andrew Morton <> | Subject | Re: 2.5.68-mm4 |
| |
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.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |