Messages in this thread |  | | Date | Mon, 29 Oct 2001 14:52:19 +0100 | From | Thomas Langås <> | Subject | Re: Intel EEPro 100 with kernel drivers |
| |
Alan Cox: > Which kernel version, which eepro100 chip ?
All kernels so far, starting with 2.4.0 (the first one we tested), and we've now come to 2.4.13 and the error is still there.
Output from lspci -vvvxx: 02:04.0 Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100] (rev 08) Subsystem: Dell Computer Corporation: Unknown device 009b Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 32 (2000ns min, 14000ns max), cache line size 08 Interrupt: pin A routed to IRQ 16 Region 0: Memory at fe900000 (32-bit, non-prefetchable) [size=4K] Region 1: I/O ports at bcc0 [size=64] Region 2: Memory at fe500000 (32-bit, non-prefetchable) [size=1M] Expansion ROM at fe600000 [disabled] [size=1M] Capabilities: [dc] Power Management version 2 Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=2 PME- 00: 86 80 29 12 17 01 90 02 08 00 00 02 08 20 00 00 10: 00 00 90 fe c1 bc 00 00 00 00 50 fe 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 28 10 9b 00 30: 00 00 60 fe dc 00 00 00 00 00 00 00 05 01 08 38
Output from dmesg: eepro100.c:v1.09j-t 9/29/99 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <saw@saw.sw.com.sg> and others eth0: Intel Corporation 82557 [Ethernet Pro 100], 00:B0:D0:F0:8B:65, IRQ 16. Receiver lock-up bug exists -- enabling work-around. Board assembly 07195d-000, Physical connectors present: RJ45 Primary interface chip i82555 PHY #1. General self-test: passed. Serial sub-system self-test: passed. Internal registers self-test: passed. ROM checksum self-test: passed (0x04f4518b). Receiver lock-up workaround activated.
I'd gladly help you track down and fix this problem, and if you need any more info (or testing of patches) just tell me :)
-- Thomas - 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/
|  |