From: Surakshan Mendis <surakshan@surasoft.com>
To: Andrew Morton <akpm@osdl.org>
Cc: netdev@oss.sgi.com, bugtracker@surasoft.com
Subject: Re: Fw: [Bugme-new] [Bug 3765] New: Network link down, when writting to sata disk AND network in use
Date: Fri, 19 Nov 2004 20:06:39 +0800 [thread overview]
Message-ID: <1100865999.13851.7.camel@localhost> (raw)
In-Reply-To: <20041117211822.243aa8bd.akpm@osdl.org>
FYI
I've just added a realtek based card using the 8139too kernel module.
The "issue" mention below DOES NOT happen with this network card. Only
with the onboard b44 card!
On Wed, 2004-11-17 at 21:18 -0800, Andrew Morton wrote:
>
> Well this is novel. I'd be suspecting a hardware problem. Are you sure
> the power supply isn't overloaded, or in need of replacement?
>
>
> Begin forwarded message:
>
> Date: Wed, 17 Nov 2004 21:13:36 -0800
> From: bugme-daemon@osdl.org
> To: bugme-new@lists.osdl.org
> Subject: [Bugme-new] [Bug 3765] New: Network link down, when writting to sata disk AND network in use
>
>
> http://bugme.osdl.org/show_bug.cgi?id=3765
>
> Summary: Network link down, when writting to sata disk AND
> network in use
> Kernel Version: linux-kernel 2.6.9
> Status: NEW
> Severity: high
> Owner: other_other@kernel-bugs.osdl.org
> Submitter: bugtracker@surasoft.com
>
>
> 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.
>
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug, or are watching someone who is.
>
>
prev parent reply other threads:[~2004-11-19 12:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 5:18 Fw: [Bugme-new] [Bug 3765] New: Network link down, when writting to sata disk AND network in use Andrew Morton
2004-11-18 6:33 ` Surakshan Mendis
2004-11-19 12:06 ` Surakshan Mendis [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1100865999.13851.7.camel@localhost \
--to=surakshan@surasoft.com \
--cc=akpm@osdl.org \
--cc=bugtracker@surasoft.com \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).