Messages in this thread | | | Subject | Re: 2.5.68-mm4 | From | Steven Cole <> | Date | 02 May 2003 15:20:20 -0600 |
| |
On Fri, 2003-05-02 at 15:05, Andrew Morton wrote: > 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. > Here is a snippet from dmesg output for a successful kexec e100 boot:
Intel(R) PRO/100 Network Driver - version 2.2.21-k1 Copyright (c) 2003 Intel Corporation
e100: selftest OK. Freeing alive device c1b23000, eth%d e100: eth0: Intel(R) PRO/100 Network Connection Hardware receive checksums enabled cpu cycle saver enabled
I booted the e100 2.5.68-mm4 kernel twice with kexec, initially from the eepro100 version, and once from the e100 version. Both worked OK.
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/
| |