All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: "Niccolò Belli" <darkbasic@linuxsystems.it>
Cc: netdev@vger.kernel.org
Subject: Re: sky2 still badly broken
Date: Thu, 3 May 2012 11:15:36 -0700	[thread overview]
Message-ID: <20120503111536.269490e3@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <4FA2C913.4080504@linuxsystems.it>

On Thu, 03 May 2012 20:06:11 +0200
Niccolò Belli <darkbasic@linuxsystems.it> wrote:

> Il 03/05/2012 17:23, Stephen Hemminger ha scritto:
> > The receiver on some versions of the chip can't keep up with full speed
> > of 1G bit/sec. The receive  FIFO has hardware issues, and since I don't
> > work for Marvell, working around the problem is guesswork. Without exact
> > information all that can be done is have a timeout and blunt force reset
> > logic. The vendor driver sk98lin has the same brute force logic, but may
> > just not print the message.
> 
> If I lower the speed to 100Mb/s I don't have rx errors anymore *BUT* 
> when using dhcp after a while the network doesn't work anymore:
> 
> 64 bytes from 8.8.8.8: icmp_req=590 ttl=47 time=61.7 ms
> 64 bytes from 8.8.8.8: icmp_req=591 ttl=47 time=62.0 ms
> 64 bytes from 8.8.8.8: icmp_req=592 ttl=47 time=62.0 ms
> ping: sendmsg: Network is unreachable
> ping: sendmsg: Network is unreachable
> ping: sendmsg: Network is unreachable
> 
> 
> I have no problems with dhcp using wifi or other NICs.
> 
> Niccolò

Maybe ethtool registers have some info?

# ethtool -S eth0
NIC statistics:
     tx_bytes: 3640274
     rx_bytes: 61588953
     tx_broadcast: 641
     rx_broadcast: 9964
     tx_multicast: 126
     rx_multicast: 1501
     tx_unicast: 32683
     rx_unicast: 50415
     tx_mac_pause: 0
     rx_mac_pause: 0
     collisions: 0
     late_collision: 0
     aborted: 0
     single_collisions: 0
     multi_collisions: 0
     rx_short: 0
     rx_runt: 0
     rx_64_byte_packets: 8704
     rx_65_to_127_byte_packets: 4414
     rx_128_to_255_byte_packets: 6218
     rx_256_to_511_byte_packets: 1289
     rx_512_to_1023_byte_packets: 1777
     rx_1024_to_1518_byte_packets: 39478
     rx_1518_to_max_byte_packets: 0
     rx_too_long: 0
     rx_fifo_overflow: 0
     rx_jabber: 0
     rx_fcs_error: 0
     tx_64_byte_packets: 1628
     tx_65_to_127_byte_packets: 27483
     tx_128_to_255_byte_packets: 2885
     tx_256_to_511_byte_packets: 637
     tx_512_to_1023_byte_packets: 429
     tx_1024_to_1518_byte_packets: 388
     tx_1519_to_max_byte_packets: 0
     tx_fifo_underrun: 0


And if you enable the debugfs option there is more info
hidden there.

# mount -t debugfs debugfs /sys/kernel/debug
# cat /sys/kernel/debug/sky2/eth0

  reply	other threads:[~2012-05-03 18:15 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-27 20:15 sky2 still badly broken Niccolò Belli
2012-04-27 20:41 ` [RFT] sky2: fix status length check on older chips Stephen Hemminger
2012-04-27 20:48   ` David Miller
2012-04-27 20:55   ` Stephen Hemminger
2012-04-27 23:05     ` Niccolò Belli
2012-04-28  2:46       ` Stephen Hemminger
2012-04-28 10:25         ` Niccolò Belli
2012-04-30 16:19           ` Stephen Hemminger
2012-04-30 18:23             ` Niccolò Belli
2012-04-28  3:03       ` [PATCH] sky2: fix receive length error in mixed non-VLAN/VLAN traffic Stephen Hemminger
2012-04-28  3:05         ` Stephen Hemminger
2012-09-17 14:20     ` [RFT] sky2: fix status length check on older chips Ivan Minev
2012-04-30 19:25 ` sky2 still badly broken Stephen Hemminger
2012-04-30 23:50   ` Niccolò Belli
2012-05-02 15:12   ` Niccolò Belli
2012-05-02 18:56     ` Stephen Hemminger
2012-05-03  9:40       ` Niccolò Belli
2012-05-03 15:23         ` Stephen Hemminger
2012-05-03 18:06           ` Niccolò Belli
2012-05-03 18:15             ` Stephen Hemminger [this message]
2012-05-03 19:26               ` Niccolò Belli
2012-05-03 19:36           ` Niccolò Belli
2012-05-03 21:25             ` Stephen Hemminger

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=20120503111536.269490e3@nehalam.linuxnetplumber.net \
    --to=shemminger@vyatta.com \
    --cc=darkbasic@linuxsystems.it \
    --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.