From: "Niccolò Belli" <darkbasic@linuxsystems.it>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: netdev@vger.kernel.org
Subject: Re: sky2 still badly broken
Date: Tue, 01 May 2012 01:50:03 +0200 [thread overview]
Message-ID: <4F9F252B.6060703@linuxsystems.it> (raw)
In-Reply-To: <20120430122501.5fff4b1e@nehalam.linuxnetplumber.net>
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.
Laptop is a Samsung X360. I will make a little dump.
Niccolò
next prev parent reply other threads:[~2012-04-30 23:49 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 [this message]
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
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=4F9F252B.6060703@linuxsystems.it \
--to=darkbasic@linuxsystems.it \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
/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).