From: Stephen Hemminger <shemminger@vyatta.com>
To: "Niccolò Belli" <darkbasic@linuxsystems.it>
Cc: netdev@vger.kernel.org
Subject: Re: sky2 still badly broken
Date: Wed, 2 May 2012 11:56:18 -0700 [thread overview]
Message-ID: <20120502115618.04ab8ff9@s6510.linuxnetplumber.net> (raw)
In-Reply-To: <4FA14EC6.6050207@linuxsystems.it>
On Wed, 02 May 2012 17:12:06 +0200
Niccolò Belli <darkbasic@linuxsystems.it> wrote:
> Il 30/04/2012 21:25, Stephen Hemminger ha scritto:
> > You are getting CRC and FIFO overrun errors. What laptop is this?
> > Everything works fine on my old Fuijitsu with same chip (but rev 14).
> > You could try taking out the status bit checks and see if the
> > packets are really okay and the Marvell chip is complaining about
> > bogus status.
>
> I compiled 3.4-rc5 + both sky2 patches you recently published and I did
> some more tests:
>
> Point to point: works flawlessly.
> Attached to the switch: rx errors, even downloading a very small 89 KB
> file :(
>
> This is the dump using IPv4:
> http://files.linuxsystems.it/temp/2012-05/sky2_ipv4.pcap
>
> dmesg (I did an rmmod -f sky2 before doing the test):
> [ 1147.885026] sky2 0000:06:00.0: eth0: disabling interface
> [ 1148.909548] sky2: driver version 1.30
> [ 1148.909764] sky2 0000:06:00.0: Yukon-2 EC Ultra chip revision 3
> [ 1148.914367] sky2 0000:06:00.0: irq 45 for MSI/MSI-X
> [ 1148.916310] sky2 0000:06:00.0: eth0: addr 00:13:77:b4:1b:fa
> [ 1148.942297] sky2 0000:06:00.0: eth0: enabling interface
> [ 1148.944225] ADDRCONF(NETDEV_UP): eth0: link is not ready
> [ 1151.496295] sky2 0000:06:00.0: eth0: Link is up at 1000 Mbps, full
> duplex, flow control rx
> [ 1151.497614] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
> [ 1178.479437] device eth0 entered promiscuous mode
> [ 1179.541707] *sky2 0000:06:00.0: eth0: rx error, status 0x7ffc0001
> length 1468*
> [ 1179.544110] *sky2 0000:06:00.0: eth0: rx error, status 0x7ffc0001
> length 1468*
> [ 1181.642598] device eth0 left promiscuous mode
>
>
>
>
> This is the dump using IPv6:
> http://files.linuxsystems.it/temp/2012-05/sky2_ipv6.pcap
>
> dmesg (I did an rmmod -f sky2 before doing the test):
> [ 1314.225572] sky2 0000:06:00.0: eth0: disabling interface
> [ 1315.248523] sky2: driver version 1.30
> [ 1315.248731] sky2 0000:06:00.0: Yukon-2 EC Ultra chip revision 3
> [ 1315.249333] sky2 0000:06:00.0: irq 45 for MSI/MSI-X
> [ 1315.250307] sky2 0000:06:00.0: eth0: addr 00:13:77:b4:1b:fa
> [ 1315.271364] sky2 0000:06:00.0: eth0: enabling interface
> [ 1315.273015] ADDRCONF(NETDEV_UP): eth0: link is not ready
> [ 1317.875985] sky2 0000:06:00.0: eth0: Link is up at 1000 Mbps, full
> duplex, flow control rx
> [ 1317.877311] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
> [ 1345.946062] device eth0 entered promiscuous mode
> [ 1349.119848] device eth0 left promiscuous mode
> [ 1376.231698] device eth0 entered promiscuous mode
> [ 1377.369095] *sky2 0000:06:00.0: eth0: rx error, status 0x7ffc0001
> length 1468*
> [ 1379.618257] device eth0 left promiscuous mode
>
>
>
> Switch is a Netgear GS724Tv3 firmware 5.0.3.5
>
>
> Cheers,
> Niccolò
It could be that your switch doesn't do autonegotiation or flow
control. You are getting receive fifo overflow errors.
next prev parent reply other threads:[~2012-05-02 18:56 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 [this message]
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
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=20120502115618.04ab8ff9@s6510.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.