From: Andrew Morton <akpm@osdl.org>
To: netdev@vger.kernel.org
Cc: "bugme-daemon@kernel-bugs.osdl.org"
<bugme-daemon@bugzilla.kernel.org>,
prusnik@gmail.com
Subject: Re: [Bugme-new] [Bug 7770] New: Network connection randomly drops
Date: Thu, 4 Jan 2007 09:25:02 -0800 [thread overview]
Message-ID: <20070104092502.279e1a5c.akpm@osdl.org> (raw)
In-Reply-To: <200701041649.l04GnnjW021531@fire-2.osdl.org>
On Thu, 4 Jan 2007 08:49:49 -0800
bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=7770
>
> Summary: Network connection randomly drops
> Kernel Version: 2.6.19 onward
> Status: NEW
> Severity: normal
> Owner: acme@conectiva.com.br
> Submitter: prusnik@gmail.com
>
>
> Most recent kernel where this bug did *NOT* occur: 2.6.19-rc4
> Distribution: ubuntu 6.10, 64 bit
> Hardware Environment: ASUS M2N-E (MCP55), AMD X2 4200+
> Software Environment: normal linux distro with a custom kernel
> Problem Description:
> It started when I compiled the stable 2.6.19 kernel (first after rc4). The
> network connection to the router just dropped and I can find no reason why it is
> so. I have to revive the connection via /etc/init.d/networking restart command
> and the connection is there again. At first I was doing remote connection
> (tsclient in ubuntu) on another ubuntu dapper machine. The connection would
> randomly terminate. I assumed it was the program, but then I did a further test.
> I used mc (midnight commander) to copy some large files (a couple ubuntu iso-s)
> to this machine (which acts as a file server) via NFS (and via router) and
> back. The connection would drop! The event is more frequent if I transfer the
> files from that computer than vice versa.
> I then rerun linux with 2.6.19-rc4 kernel and transfers were stable without a
> single connection drop. I then assumed it should be the newer forcedeth driver
> to blame but apparently it isn't. I put the 0.57 driver into the 2.6.20-rc3 and
> the problem persists. I even tried this patch from the bug #7684 but this didn't
> help either.
>
> Steps to reproduce:
> Hopefully with this hardware I mentioned, plain ubuntu 6.10 64 bit installation
> with a kernel higher than 2.6.19-rc4. Config and other status files are in the
> attachment.
>
parent reply other threads:[~2007-01-04 17:42 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200701041649.l04GnnjW021531@fire-2.osdl.org>]
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=20070104092502.279e1a5c.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=prusnik@gmail.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).