Messages in this thread | | | Subject | Re: 2.5.68-mm4 | From | Steven Cole <> | Date | 02 May 2003 14:49:02 -0600 |
| |
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.
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.
Otherwise, kexec works fine here so far over about a dozen reboots on both machines.
Steven
- 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/
| |