From: "Krzysztof Olędzki" <ole@ans.pl>
To: Michael Chan <mchan@broadcom.com>
Cc: "'Andrew Morton'" <akpm@linux-foundation.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"bugzilla-daemon@bugzilla.kernel.org"
<bugzilla-daemon@bugzilla.kernel.org>,
"bugme-daemon@bugzilla.kernel.org"
<bugme-daemon@bugzilla.kernel.org>
Subject: Re: [Bugme-new] [Bug 14685] New: 2.6.30 -> 2.6.31: very high number of RX dropped in bnx2
Date: Wed, 02 Dec 2009 14:37:56 +0100 [thread overview]
Message-ID: <4B166DB4.9080101@ans.pl> (raw)
In-Reply-To: <1259603093.14964.79.camel@nseg_linux_HP1.broadcom.com>
On 2009-11-30 18:44, Michael Chan wrote:
> On Mon, 2009-11-30 at 07:33 -0800, Krzysztof Oledzki wrote:
>> # ethtool -S eth0|egrep "(rx_bcast_packets|rx_mcast_packets|
>> rx_fw_discards)"
>> rx_mcast_packets: 2806
>> rx_bcast_packets: 790016
>> rx_fw_discards: 790016
>
> This tells me that all the dropped packets are occurring in the iSCSI
> ring.
>
> We have recently enabled iSCSI in the kernel and you probably don't have
> the userspace components to handle the iSCSI ring. All broadcast
> packets are also received in the iSCSI ring and they are all dropped in
> this case without the userspace components. Networking is not affected.
> If you rmmod the bnx2i and cnic drivers, the drop counter should stop
> counting.
>
> We have newer firmware that will not include dropped iSCSI packets in
> the networking counters. It should appear in the 2.6.33 kernel
> time-frame.
Yep, it was the cnic driver. Now I feel silly. Thank you for you help
and sorry for the noise. I going to close it with RESOLVED-DOCUMENTED.
Best regards,
Krzysztof Olędzki
prev parent reply other threads:[~2009-12-02 13:38 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 ` [Bugme-new] [Bug 14685] New: 2.6.30 -> 2.6.31: very high number of RX dropped in bnx2 Andrew Morton
2009-11-30 11:33 ` Michael Chan
2009-11-30 15:33 ` Krzysztof Oledzki
2009-11-30 17:44 ` Michael Chan
2009-12-02 13:37 ` Krzysztof Olędzki [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=4B166DB4.9080101@ans.pl \
--to=ole@ans.pl \
--cc=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 \
/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).