From: Ben Hutchings <ben@decadent.org.uk>
To: netdev <netdev@vger.kernel.org>,
Eric Dumazet <eric.dumazet@gmail.com>,
Ayaz Abdulla <aabdulla@nvidia.com>
Cc: stephen mulcahy <smulcahy@atlanticlinux.ie>, 572201@bugs.debian.org
Subject: forcedeth driver hangs under heavy load
Date: Sun, 11 Apr 2010 00:36:46 +0100 [thread overview]
Message-ID: <1270942606.6179.64.camel@localhost> (raw)
In-Reply-To: <4BBCA19C.5080204@atlanticlinux.ie>
[-- Attachment #1: Type: text/plain, Size: 968 bytes --]
Stephen Mulcahy reported a regression in forcedeth at
<http://bugs.debian.org/572201>. The system information and some
diagnostic information can be found there. Anyone able to help?
Ben.
stephen mulcahy wrote:
> When running linux-image-2.6.32-trunk-amd64, the network stops
> responding if large amounts of traffic are transmitted/received. Running
> ifdown eth0 followed by ifup eth0 restores operation of the network.
> There are no errors relating to this failure logged in /var/log that I
> could see.
>
> Downgrading to linux-image-2.6.30-2-amd64 results in a stable network.
> Not sure if this is a forcedeth specific problem or a general problem in
> the newer kernel (I have seen problems with forcedeth on other
> distro/kernel combinations).
>
> Happy to run further diagnostics to tie this down if you let me know
> what to run.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next parent reply other threads:[~2010-04-10 23:39 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4B9E6C60.7030300@atlanticlinux.ie>
[not found] ` <20100315182220.GQ2763@decadent.org.uk>
[not found] ` <4B9F5E5E.2060209@atlanticlinux.ie>
[not found] ` <1270393967.8341.11.camel@localhost>
[not found] ` <4BBCA19C.5080204@atlanticlinux.ie>
2010-04-10 23:36 ` Ben Hutchings [this message]
2010-04-12 10:01 ` Bug#572201: forcedeth driver hangs under heavy load stephen mulcahy
2010-04-12 12:39 ` stephen mulcahy
2010-04-12 12:47 ` Eric Dumazet
2010-04-12 13:05 ` stephen mulcahy
2010-04-12 13:19 ` stephen mulcahy
2010-04-12 15:24 ` Eric Dumazet
2010-04-12 16:11 ` stephen mulcahy
2010-04-12 16:59 ` Eric Dumazet
2010-04-13 10:03 ` stephen mulcahy
2010-04-13 10:49 ` Eric Dumazet
2010-04-13 11:00 ` stephen mulcahy
2010-04-13 12:04 ` Ben Hutchings
2010-04-13 14:27 ` stephen mulcahy
2010-04-13 14:42 ` Eric Dumazet
2010-04-13 14:49 ` stephen mulcahy
2010-04-13 15:00 ` stephen mulcahy
2010-04-13 15:05 ` Eric Dumazet
2010-04-13 15:08 ` stephen mulcahy
2010-04-13 15:22 ` Eric Dumazet
2010-04-13 15:25 ` stephen mulcahy
2010-04-13 20:01 ` Eric Dumazet
2010-04-13 21:43 ` David Miller
2010-04-13 21:46 ` Eric Dumazet
2010-04-14 5:33 ` Bug#572201: " Ayaz Abdulla
2010-04-14 1:41 ` David Miller
2010-04-14 14:30 ` stephen mulcahy
2010-04-14 5:31 ` Bug#572201: [PATCH] forcedeth: fix tx limit2 flag check Ayaz Abdulla
2010-04-14 10:14 ` stephen mulcahy
2010-04-13 17:22 forcedeth driver hangs under heavy load Xose Vazquez Perez
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=1270942606.6179.64.camel@localhost \
--to=ben@decadent.org.uk \
--cc=572201@bugs.debian.org \
--cc=aabdulla@nvidia.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=smulcahy@atlanticlinux.ie \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.