From: Stephen Hemminger <shemminger@vyatta.com>
To: Krzysztof Oledzki <ole@ans.pl>
Cc: Linux Netdev <netdev@vger.kernel.org>,
Linux Networking <linux-net@vger.kernel.org>,
Daniel J Blueman <daniel.blueman@gmail.com>
Subject: Re: [sky2, solved] transmit timeouts and firmware update...
Date: Mon, 25 Aug 2008 15:22:06 -0400 [thread overview]
Message-ID: <20080825152206.2d554cf7@speedy> (raw)
In-Reply-To: <alpine.LNX.1.10.0808252048440.25225@bizon.gios.gov.pl>
On Mon, 25 Aug 2008 21:03:25 +0200 (CEST)
Krzysztof Oledzki <ole@ans.pl> wrote:
>
>
> On Mon, 25 Aug 2008, Daniel J Blueman wrote:
>
> > I (and a lot of other users) have been experiencing the frequent sky2
> > transmit timeout problem [1] (on 88E8053/Yukon2 EC gig hardware); this
> > is a result of the embedded NIC controller locking up, and I've found
> > that updating the firmware addresses this issue. I'm still seeing a
> > previous and different issue [2] from time to time though (silicon
> > bug?).
>
> Thanks for the info. I've been dealing with this problem for some long
> time, hopefully sky driver from the latest kernels is able to recover
> from such hangs, so it is not that critical problem now.
>
> > Marvell shipping broken firmware is completely unpublicised or
> > acknowledged, however updated firmware is available through your
> > motherboard vendor, so all hope it not lost after all...
>
> Unfortunately not through all vendors. :( Or maybe not *yet*?
>
> > My 8053/EC is using firmware 2.2 (previously 1.9) - you can check in
> > DOS with 'yukondg.exe' from
> > http://www.marvell.com/drivers/files/yukondg_v6.53.4.3.zip .
>
> Stephen, is it possible for sky2 driver to check and print the
> firmware version?
It is possible to dump and program eeprom from linux, and the version
maybe buried in the VPD, but some hardware has non-functional VPD.
next prev parent reply other threads:[~2008-08-25 19:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-25 14:42 [sky2, solved] transmit timeouts and firmware update Daniel J Blueman
2008-08-25 19:03 ` Krzysztof Oledzki
2008-08-25 19:22 ` Stephen Hemminger [this message]
2008-08-27 20:27 ` Stephen Hemminger
2008-08-27 21:37 ` Daniel J Blueman
2008-08-27 21:42 ` Stephen Hemminger
2008-08-27 21:48 ` Daniel J Blueman
2008-08-27 21:58 ` Daniel J Blueman
2008-08-27 22:16 ` Krzysztof Oledzki
2008-08-27 22:14 ` Krzysztof Oledzki
2008-08-25 19:46 ` Daniel J Blueman
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=20080825152206.2d554cf7@speedy \
--to=shemminger@vyatta.com \
--cc=daniel.blueman@gmail.com \
--cc=linux-net@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ole@ans.pl \
/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.