Bug 14685 - 2.6.30 -> 2.6.31: very high number of RX dropped in bnx2
Summary: 2.6.30 -> 2.6.31: very high number of RX dropped in bnx2
Status: RESOLVED DOCUMENTED
Alias: None
Product: Drivers
Classification: Unclassified
Component: Network (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_network@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks: 13615
  Show dependency tree
 
Reported: 2009-11-25 00:15 UTC by Krzysztof Oledzki
Modified: 2009-12-02 18:31 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.31.6
Tree: Mainline
Regression: Yes


Attachments

Description Krzysztof Oledzki 2009-11-25 00:15:59 UTC
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.
Comment 1 Andrew Morton 2009-11-25 20:47:33 UTC
(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.
>
Comment 2 Anonymous Emailer 2009-11-30 15:34:07 UTC
Reply-To: ole@ans.pl

On Mon, 30 Nov 2009, Michael Chan wrote:

> Andrew Morton wrote:
>
>>> # 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
>>>
>
> Please report rx_bcast_packets and rx_mcast_packets together with
> rx_fw_discards.  Thanks.

# 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

Best regards,

 				Krzysztof Olędzki
Comment 3 Anonymous Emailer 2009-12-02 13:38:12 UTC
Reply-To: ole@ans.pl

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

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