Bug 61816
Summary: | (NET EEPRO100) Update to kernel hoses networking on Acer Travelmate | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Michal Jaegermann <michal> | ||||
Component: | kernel | Assignee: | Jeff Garzik <jgarzik> | ||||
Status: | CLOSED UPSTREAM | QA Contact: | Brian Brock <bbrock> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 7.2 | CC: | peterm | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i386 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2004-03-03 05:56:27 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Red Hat Bugzilla
2002-03-24 20:59:40 UTC
Created attachment 50004 [details]
dmesg output from an NFS session
On the less optimistic note just now an ssh session _to_ this laptop running 2.4.18-0.4 wedged up and it does not look that it is going to recover. :-( It is already few minutes with a dead network. One more possible clue. After I did 'ifdown eth0; iup eth0' on a laptop a network is back and dmesg reports a bunch of eepro100: wait_for_cmd_done timeout! ("last message repeated 4 times" and "last message repeated 13 times") followed by eth0: 0 multicast blocks dropped. I'm getting this same thing with kernel 2.4.8-0.16, under RH7.2. Everything works fine after a reboot/startup, but after suspending and unsuspending, I get (copied from /var/log/messages): Apr 8 10:44:07 rain kernel: eepro100.c:v1.09j-t 9/29/99 Donald Becker http://www.scyld.com/network/eepro100.html Apr 8 10:44:07 rain kernel: eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <saw.com.sg> and others Apr 8 10:44:07 rain kernel: PCI: Enabling device 08:04.0 (0000 -> 0003) Apr 8 10:44:07 rain kernel: PCI: Setting latency timer of device 08:04.0 to 64 Apr 8 10:44:07 rain kernel: eth0: Invalid EEPROM checksum 0xff00, check settings before activating this device! Apr 8 10:44:07 rain kernel: eth0: OEM i82557/i82558 10/100 Ethernet, FF:FF:FF:FF:FF:FF, IRQ 10. Apr 8 10:44:07 rain kernel: Board assembly ffffff-255, Physical connectors present: RJ45 BNC AUI MII Apr 8 10:44:07 rain kernel: Primary interface chip unknown-15 PHY #31. Apr 8 10:44:07 rain kernel: Secondary interface chip i82555. Apr 8 10:44:07 rain kernel: Self test failed, status ffffffff: Apr 8 10:44:07 rain kernel: Failure to initialize the i82557. Apr 8 10:44:07 rain kernel: Verify that the card is a bus-master capable slot. diff -u of 'lspci -vv' from pre and post suspend shows a number of differences: --- ee.pre Tue Apr 9 11:40:57 2002 +++ ee.post Tue Apr 9 11:40:35 2002 @@ -1,15 +1,13 @@ 08:04.0 Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100] (rev 08) Subsystem: Action Tec Electronics Inc: Unknown device 1100 - 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 + 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: 64 (2000ns min, 14000ns max) Interrupt: pin A routed to IRQ 10 - Region 0: Memory at f8fff000 (32-bit, non-prefetchable) [size=4K] + Region 0: [virtual] Memory at f8fff000 (32-bit, non-prefetchable) [size=4K] Region 1: I/O ports at ecc0 [size=64] - Region 2: Memory at f8e00000 (32-bit, non-prefetchable) [size=1M] + Region 2: [virtual] Memory at f8e00000 (32-bit, non-prefetchable) [size=1M] Expansion ROM at f9000000 [disabled] [size=1M] Capabilities: [dc] Power Management version 2 - Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot -+,D3cold+) - Status: D2 PME-Enable- DSel=0 DScale=2 PME- + Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) + Status: D0 PME-Enable+ DSel=0 DScale=2 PME- (I hope bugzilla doesn't mangle this) 2.4.18-0.13 from the current "public beta" included e100 among "addon" drivers. This one seems to work without going away after a while. It also survives suspend. The value of this report seems to be mostly historical. I did not hear from the owner about network problems; but he is using e100 driver. Ok, closing since e100 appears to work. We are deprecating eepro100 in favor of e100. |