From: Andrew Morton <akpm@linux-foundation.org>
To: Michael Chan <mchan@broadcom.com>, netdev@vger.kernel.org
Cc: bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org, olel@ans.pl
Subject: Re: [Bugme-new] [Bug 14685] New: 2.6.30 -> 2.6.31: very high number of RX dropped in bnx2
Date: Wed, 25 Nov 2009 12:47:13 -0800 [thread overview]
Message-ID: <20091125124713.f7ac10e4.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-14685-10286@http.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Wed, 25 Nov 2009 00:16:00 GMT
bugzilla-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=14685
>
> Summary: 2.6.30 -> 2.6.31: very high number of RX dropped in
> bnx2
> Product: Drivers
> Version: 2.5
> Kernel Version: 2.6.31.6
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Network
> AssignedTo: drivers_network@kernel-bugs.osdl.org
> ReportedBy: olel@ans.pl
> Regression: Yes
>
>
> After upgradig my kernel from 2.6.30 to 2.6.31 I'm observing very high number
> of dropped packets on BCM5708(Dell PowerEdge 1950)/BCM5716(Dell PowerEdge R410)
> NICs.
>
> # uptime ; ifconfig eth0|grep "RX p"; ethtool -S eth0|grep disc
> 01:07:31 up 6 min, 1 user, load average: 0.00, 0.07, 0.04
> RX packets:2234 errors:0 dropped:527 overruns:0 frame:0
> rx_discards: 0
> rx_fw_discards: 527
>
> Everything seems to work just fine so I suspect that the driver/firmware is
> counting something wrong.
>
next parent reply other threads:[~2009-11-25 20:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-14685-10286@http.bugzilla.kernel.org/>
2009-11-25 20:47 ` Andrew Morton [this message]
2009-11-30 11:33 ` [Bugme-new] [Bug 14685] New: 2.6.30 -> 2.6.31: very high number of RX dropped in bnx2 Michael Chan
2009-11-30 15:33 ` Krzysztof Oledzki
2009-11-30 17:44 ` Michael Chan
2009-12-02 13:37 ` Krzysztof Olędzki
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=20091125124713.f7ac10e4.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=olel@ans.pl \
/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).