Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 230992 - gigabit ethernet network losing connection
Summary: gigabit ethernet network losing connection
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 6
Hardware: ia64
OS: Linux
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2007-03-05 12:59 UTC by Matt Gross
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-03-05 14:46:31 UTC

Attachments (Terms of Use)

Description Matt Gross 2007-03-05 12:59:36 UTC
Description of problem:

I am having a lot of problems with my Fedora Core 6 server connection
going down when traffic increases. I bought a new switch (mine is quite
old) in hopes of fixing the problem, however, that seems to have
exacerbated the problem.

Version-Release number of selected component (if applicable):

How reproducible:
Always - Consistent

Steps to Reproduce:
1. Running kernel: 2.6.19-1.2911.fc6
2. Increase traffic by ftp'ing, or downloading something (reproducible with
different methods of increasing network traffic)
3. between 15 and 60 seconds later, the connection will be lost.
Actual results:
connection is lost

Expected results:
connection should be maintained

Additional info:
There is a lot of info and prior conversations and diagnostics with other linux
experts in the Linux community at the link provided.  Please look there for
details.  I am happy to contribute more diagnostics if needed:

Comment 1 Matt Gross 2007-03-05 14:43:48 UTC
I just updated my kernel to 2.6.19-1.2911.6.4.fc6 and I am no longer able to
reproduce the problem.  Let's set this bug to "waiting to be reproduced" until I
prove that I can consistently reproduce the bug.

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