All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Grennan <linux-netdev@cygnusx-1.org>
To: netdev@vger.kernel.org
Subject: Re: sky2 0000:02:00.0: error interrupt status=0x8
Date: Tue, 26 Feb 2008 20:37:32 -0800	[thread overview]
Message-ID: <47C4E90C.3090600@cygnusx-1.org> (raw)
In-Reply-To: <20080226194818.1ee41099@extreme>

Stephen Hemminger wrote:
> On Tue, 26 Feb 2008 18:30:47 -0800
> Nathan Grennan <linux-netdev@cygnusx-1.org> wrote:
>
>   
>>     I am using the sky2 driver in kernel-2.6.23.15-137.fc8.x86_64 with 
>> my Marvell 88E8056 to do iSCSI. I have many errors in dmesg like the 
>> ones below. If I count just the lines that match the first one, there 
>> are over 1500. If I include the suppressed lines it is over 100k. At 
>> first I got three of these doing something and then didn't see it for a 
>> while. I suspect the 100k came from a download of an 8gb file from the 
>> internet that was being written to the remote machine via iSCSI. The 
>> download took about an hour and fifteen minutes. I would ignore just 
>> three of these, but 100k of them suggests a real problem to me.
>>
>> sky2 0000:02:00.0: error interrupt status=0x8
>> printk: 77 messages suppressed.
>>     
>
> That status comes from the MAC getting an error.
> Most likely the receive FIFO is getting overrun. Look at the receive
> errors, RX fifo is probably non-zero.
>
> $ ip -s -s li show dev eth0
> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
>     link/ether 00:00:5a:9b:0e:76 brd ff:ff:ff:ff:ff:ff
>     RX: bytes  packets  errors  dropped overrun mcast   
>     199873594  240394   0       0       0       0      
>     RX errors: length  crc     frame   fifo    missed
>                0        0       0       0       0      
>                                         ^
>
>
> Make sure and use hardware flow control if you are using jumbo frames because
> it is real easy to get the ram buffer full, and frames lost.
>
>   
I couldn't find mention of the flow control till I downed and upped the 
interface.

sky2 eth2: Link is up at 1000 Mbps, full duplex, flow control both


Yes, I do have fifo/overrun errors and the count is around the 100k 
mark, but not on RX. It is on TX.

ifconfig eth2
eth2      Link encap:Ethernet  HWaddr 00:18:F3:7C:38:5A 
          inet addr:192.168.254.1  Bcast:192.168.254.255  Mask:255.255.255.0
          inet6 addr: fe80::218:f3ff:fe7c:385a/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:9000  Metric:1
          RX packets:3196945 errors:69 dropped:69 overruns:2 frame:69
          TX packets:2930128 errors:0 dropped:0 overruns:111324 carrier:0
          collisions:0 txqueuelen:10000
          RX bytes:15313780678 (14.2 GiB)  TX bytes:14583689334 (13.5 GiB)
          Interrupt:17


ip -s -s li show dev eth2
6: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc pfifo_fast 
qlen 10000
    link/ether 00:18:f3:7c:38:5a brd ff:ff:ff:ff:ff:ff
    RX: bytes  packets  errors  dropped overrun mcast  
    2428878890 3196946  69      69      69      0     
    RX errors: length  crc     frame   fifo    missed
               0        0       0       2       0     
    TX: bytes  packets  errors  dropped carrier collsns
    1698787626 2930130  0       0       0       0     
    TX errors: aborted fifo    window  heartbeat
               0        111324  0       0     




I also notice I can't turn on TX checksumming. I can't turn on any of 
the others either, except generic segmentation offload.

ethtool -k eth2         
Offload parameters for eth2:
Cannot get device udp large send offload settings: Operation not supported
rx-checksumming: on
tx-checksumming: off
scatter-gather: off
tcp segmentation offload: off
udp fragmentation offload: off
generic segmentation offload: off



ethtool -K eth2 tx on
Cannot set device tx csum settings: Invalid argument

      reply	other threads:[~2008-02-27  4:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-27  2:30 sky2 0000:02:00.0: error interrupt status=0x8 Nathan Grennan
2008-02-27  3:48 ` Stephen Hemminger
2008-02-27  4:37   ` Nathan Grennan [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=47C4E90C.3090600@cygnusx-1.org \
    --to=linux-netdev@cygnusx-1.org \
    --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 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.