From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Rob Sims <lkml-z@robsims.com>
Cc: "Thomas Glanzmann" <thomas@glanzmann.de>,
LKML <linux-kernel@vger.kernel.org>,
"Andreas Allgöwer" <andreas.allgoewer@web.de>,
"Michael Gernoth" <simigern@cip.informatik.uni-erlangen.de>
Subject: Re: sky2 PHY setup
Date: Fri, 16 Mar 2007 14:16:48 -0700 [thread overview]
Message-ID: <20070316141648.15d7ff75@freekitty> (raw)
In-Reply-To: <20070316203645.GA24699@robsims.com>
On Fri, 16 Mar 2007 14:36:45 -0600
Rob Sims <lkml-z@robsims.com> wrote:
> On Fri, Mar 16, 2007 at 09:59:32AM -0700, Stephen Hemminger wrote:
> > On Fri, 16 Mar 2007 01:29:12 +0100
> > Thomas Glanzmann <thomas@glanzmann.de> wrote:
> >
> > > Hello Stephen,
> > >
> > > > yesterday I pulled from Linus tree because I saw the sky2 updated and I
> > > > tried to break it but it seems that my problems are gone. I let you know
> > > > if anything pops up in the future.
> > >
> > > bad news. I today tried the sky2 driver which is in Linus Kernel Tree
> > > (HEAD) on a machine with very high network load and it stopped working
> > > without any kernel messages after doing a flawless job under high load
> > > for 5 hours. My watchdog rebooted the machine after 500 seconds. ;-(
> > >
> > > Thomas
> >
> > I have run for 2+ days under load without problems. It is hard to
> > reproduce or do much about your problem without more info.
>
> Are there some debug hooks that can be activated? My sky2 stops
> responding (very light load) about twice a day. The netdev watchdog
> notices after a while and is able to reactivate the interface:
>
> Mar 15 13:28:12 btd kernel: NETDEV WATCHDOG: eth0: transmit timed out
> Mar 15 13:28:12 btd kernel: sky2 eth0: tx timeout
> Mar 15 13:28:12 btd kernel: sky2 eth0: transmit ring 458 .. 435 report=458 done=458
> Mar 15 13:28:12 btd kernel: sky2 eth0: disabling interface
> Mar 15 13:28:12 btd kernel: sky2 eth0: enabling interface
> Mar 15 13:28:12 btd kernel: sky2 eth0: ram buffer 48K
> Mar 15 13:28:15 btd kernel: sky2 eth0: Link is up at 1000 Mbps, full duplex, flow control both
Use ethtool -S to if there are any pause frames, etc. See if frames are
still making it into PHY statistics but not being received.
Use ethtool -d to dump registers. Need current version of ethtool with decode logic.
Then look for things like is Ram buffer read/write pointer changing?
Is GMAC stuck in pause:
Normal is:
GMAC 1
Status 0x5010 (see GM_GPSR_XXX in sky2.h)
Control 0x1800
Stuck is
GMAC 1
Status 0x5810 (or 0x5A10)
--
Stephen Hemminger <shemminger@linux-foundation.org>
next prev parent reply other threads:[~2007-03-16 21:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070202102705.3cf028a6@freekitty>
[not found] ` <20070202210934.GM1693@cip.informatik.uni-erlangen.de>
[not found] ` <20070202151601.677ec5d9@freekitty>
[not found] ` <20070203073012.GO1693@cip.informatik.uni-erlangen.de>
[not found] ` <20070205090429.31d7bd32@freekitty>
[not found] ` <20070222193611.GR20035@cip.informatik.uni-erlangen.de>
2007-03-16 0:29 ` sky2 PHY setup Thomas Glanzmann
2007-03-16 16:59 ` Stephen Hemminger
2007-03-16 20:36 ` Rob Sims
2007-03-16 21:16 ` Stephen Hemminger [this message]
2007-03-27 3:24 ` Rob Sims
2007-04-04 18:19 ` Stephen Hemminger
2007-04-07 17:53 ` Rob Sims
2007-05-06 20:22 ` Rob Sims
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=20070316141648.15d7ff75@freekitty \
--to=shemminger@linux-foundation.org \
--cc=andreas.allgoewer@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml-z@robsims.com \
--cc=simigern@cip.informatik.uni-erlangen.de \
--cc=thomas@glanzmann.de \
/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