Bug 3765 - (net b44) Network link down, when writting to sata disk AND network in use
Summary: (net b44) Network link down, when writting to sata disk AND network in use
Status: REJECTED UNREPRODUCIBLE
Alias: None
Product: Drivers
Classification: Unclassified
Component: Network (show other bugs)
Hardware: i386 Linux
: P2 high
Assignee: Jeff Garzik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-17 21:13 UTC by Surakshan Mendis
Modified: 2008-03-04 19:20 UTC (History)
2 users (show)

See Also:
Kernel Version: 2.6.9, 2.6.13, 2.6.17-rc4
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description Surakshan Mendis 2004-11-17 21:13:32 UTC
Distribution: Gentoo

Hardware Environment: 
P4 2.66ghz
Motherboard: ASUS P4PE (with onboard lan)
Promise Sata150 TX4 PCI (sata expansion card)

Software Environment: 
Kernel 2.6.9
- onboard LAN: driver in use
- "Broadcom 4400 ethernet support" compiled into kernel

- Promise Sata150 TX4 PCI (sata expansion card)
- Driver "Promise SATA TX2/TX4 support" compiled into kernel
- 200GB Western Digital SATA drive attached to PCI sata card

Problem Description:
If data is being copied to the SATA drive (eg from another DISK which is on
motherboard IDE controller) AND I start a network data transfer where data is
goung through the Broadcom lan the following occurs (from kernel log)

Nov 18 11:43:10 synapse b44: eth0: Link is down.
Nov 18 11:43:15 synapse b44: eth0: Link is up at 100 Mbps, full duplex.
Nov 18 11:43:15 synapse b44: eth0: Flow control is on for TX and on for RX.
Nov 18 11:43:19 synapse b44: eth0: Link is down.
Nov 18 11:43:21 synapse b44: eth0: Link is up at 100 Mbps, full duplex. 

Link keeps going up and down, as long as there's data movment from the SATA
drive, and a network movement (network download doesn't have to be saving to the
 sata drive)

I've disabled APCI, problem persits.

Steps to reproduce:
1. copy data to Sata drive CONNECTED to PCI controller
2. Download file from network via onboard LAN, doesn't matter which drive you
save it
3. Onboards lan "link" goes up and down, causing disruption to network useage.
Comment 1 Surakshan Mendis 2004-11-17 22:03:53 UTC
I belive I'm eliminated "power" as a reason, i've disconnected a 7200rpm non
vital drive (IDE), disconnected cd and dvd rom, disconnected non vital fans.

I've also moved the sata cable to a different sata port on the expansion card.
Result hasn't changed, problem persists
Comment 2 Surakshan Mendis 2004-11-19 04:08:00 UTC
added realtek LAN card and 8139too driver.
I can confirm the bug no longer occuers with this network card.

So its got something to do with the Broadcom 4400 driver in the kernel, or
something whack with the hardware on the mobo. I do not have a similar machine
to test this.
Comment 3 Adrian Bunk 2005-08-09 16:41:29 UTC
Is this problem still present in kernel 2.6.13-rc6?
Comment 4 Surakshan Mendis 2005-09-18 18:07:54 UTC
Problem is still there on the stabe 2.6.13 from kernel.org.
Today I tried by doing an FTP transfer where the netword card was the Broadcom
4400 onboard using the b44 driver.

Test 1: saved large file to IDE disk. No problem
Test 2: saved large file to SATA disk (connected to sata controller), network
drops...

Sep 19 08:51:58 synapse b44: eth0: Link is down.
Sep 19 08:52:01 synapse b44: eth0: Link is up at 100 Mbps, full duplex.
Sep 19 08:52:01 synapse b44: eth0: Flow control is on for TX and on for RX.
Sep 19 08:52:03 synapse b44: eth0: Link is down.
Sep 19 08:52:06 synapse b44: eth0: Link is up at 100 Mbps, full duplex.
Sep 19 08:52:06 synapse b44: eth0: Flow control is on for TX and on for RX.
...
.....

TEST 3: Transfers data from IDE disk to sata disk, network drops same as output
from the system logger.

I'm using another PCI network card that uses the natsemi driver -- the problem
doesn't happen on it. Also as mentioned before I've really stripped down the
system by removing all but the SATA controller and the problem continues.
Comment 5 Peter Barker 2006-05-18 22:45:14 UTC
I'm seeing the same occur here.

P4PE motherboard, Promise SATA300 TX4 card installed.

Googling shows others having this problem without mention of the TX4 card.

Disabling ACPI has no effect.

I have a feeling that the PCI bus being flooded is the problem.

I get the problem doing /any/ network traffic, not just traffic resulting in
writes to disk. In the case I'm looking at, the system is resyncing a raid10
array. Doing a "make oldconfig" (or any other network traffic, it seems) in an
nfs-mounted partition causes the link bouncing behaviour.

Fiddling with the raid rebuild rate DOES affect things - reduces the occurence
of the problem, but at a raid10 rebuild rate of 20M/second the problem still occurs.

Wild-assed guess at it being a PCI bus problem.
Comment 6 Peter Barker 2006-05-20 19:31:46 UTC
Removed the PCI sata card. Can still reproduce problems by connecting two SATA
drives to the integrated SATA controller on this motherboard (ASUS P4PE).

Integrated SATA controller is on the same bus as the b44 and the motherboard's
PCI slots.

Both SATA controllers (on-board and PCI card) are Promise chipsets, but I'm
thinking that b44 is simply unhappy when the PCI bus is busy. I don't have any
other convenient way of flooding that bus ATM.

(kernel is 2.6.17rc4)
Comment 7 Natalie Protasevich 2007-09-19 23:21:51 UTC
Any update on this? Is it still a problem with recent kernel?
Thanks.
Comment 8 Natalie Protasevich 2008-03-04 19:20:10 UTC
Since the subsystem has changes so much and no new updates - closing the bug (hopefully everything works now).

Note You need to log in before you can comment on or make changes to this bug.