Bug 11056
| Summary: | constant disconnects and reconnects on Broadcom NIC (wired) when under load | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | John Peters (anothersillyname) |
| Component: | Network | Assignee: | drivers_network (drivers_network) |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | high | CC: | alan, andreas, bishillo, bojan, marc321, noiano, rdunlap, sarannmr |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.35 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
|
Description
John Peters
2008-07-08 15:34:04 UTC
Sorry it just occurred to me that the machine was recently upgraded to 4gb, I don't remember it happening prior to that. Now this is strange........ I had to turn off compiz on the laptop for another reason and the disconnects have stopped? I suspect this could be a 3.25gb (which the OS actually shows) 4gb (actually fitted memory) PCI mapping issue? Frankly I'm out of my depth here and while I've seen some weird stuff over the years with computers this one is pretty unusual. Please HELP before my head explodes. OK I reduced the memory back to 2gb and there are still disconnects when Compiz is turned on. Any ideas? I have a similar problems with "BCM4401-B0 100Base-TX (rev 02)" nic. https://bugs.launchpad.net/linux/+bug/279102 related? I confirm this with the following hardware. When using X session (specially with compiz, it's much more reproducible) the link of the ethernet controller gets down with high network traffic. Using nvidia graphics card and Broadcom BCM4401 network controller. 00:05.0 VGA compatible controller [0300]: nVidia Corporation C51 [GeForce 6150 LE] [10de:0241] (rev a2) Subsystem: Dell Device [1028:01ed] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 16 Region 0: Memory at fc000000 (32-bit, non-prefetchable) [size=16M] Region 1: Memory at e0000000 (64-bit, prefetchable) [size=256M] Region 3: Memory at fb000000 (64-bit, non-prefetchable) [size=16M] [virtual] Expansion ROM at 88000000 [disabled] [size=128K] Capabilities: [48] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable- Address: 0000000000000000 Data: 0000 Kernel driver in use: nvidia Kernel modules: nvidiafb, nvidia 04:07.0 Ethernet controller [0200]: Broadcom Corporation BCM4401-B0 100Base-TX [14e4:170c] (rev 02) Subsystem: Dell Device [1028:01ed] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 64 Interrupt: pin A routed to IRQ 19 Region 0: Memory at fdbfc000 (32-bit, non-prefetchable) [size=8K] Capabilities: [40] 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- Kernel driver in use: b44 Kernel modules: b44 04:09.0 Network controller [0280]: Elsa AG QuickStep 1000 [1048:1000] (rev 01) Subsystem: Elsa AG QuickStep 1000 [1048:1000] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Interrupt: pin A routed to IRQ 7 Region 0: Memory at fdbff000 (32-bit, non-prefetchable) [size=128] Region 1: I/O ports at 9c00 [size=128] Region 3: I/O ports at 9800 [size=4] Kernel modules: hisax It doesn't really have to be heavy load. My interface disconnects as soon as the DHCP gets an address. And if statically configured, stays for a little while longer. Does this problem disappear if one uses a b44 driver from older kernels. The NIC used to work fine for me an year ago! I encounter the same issue on my Dell Vostro 1000 with the "08:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)" ethernet controller on linux 2.6.31.4. Once dhcpcd assigns an ip, the device gets powered down and I'm unable to establish a reliable connection. My last linux kernel was 2.6.28 something and it worked perfectly. With the new kernel I get the following message in dmesg being repeated a _lot_ : http://pastie.org/662308 Is there a chance to fix this issue somehow? Is it probably related to power management or some other part of the kernel? Thanks. I can see this problem on Dell Inspiron 6400 (03:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)) and Fedora 12 (2.6.31.5-127.fc12.i686). Due to problems with Intel graphics, I am actually running metacity and nomodeset, so this is probably not related to anything compiz is doing. Pretty sure this is not related to compiz or anything like that. Anyone looking at b44 driver? This bug has been around for a long time. I wish I knew more about programming so I could help out. Bug is still present in 2.6.35.y series. My experience is similar to Saran's. DHCP results in instant disconnect. Static IP is better. In the interest of not duplicating info, see bug 14451 comment 4 for some of my specs. I have the same issue with kernel 2.6.35-22 and NIC 02:05.0 Ethernet controller: Broadcom Corporation BCM4401 100Base-T (rev 01) Subsystem: ASUSTeK Computer Inc. A7V8X motherboard Flags: bus master, fast devsel, latency 32, IRQ 20 Memory at de000000 (32-bit, non-prefetchable) [size=8K] Capabilities: [40] Power Management version 2 Kernel driver in use: b44 Kernel modules: b44 Is it possible there is no workaround? I got disconnected only when transferring data on the LAN, and yes the ip is statically assigned *** This bug has been marked as a duplicate of bug 7696 *** |