netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Fitzgerald <netzdamon@gmail.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: netdev@vger.kernel.org
Subject: Re: sky2 hangs
Date: Sat, 20 Sep 2008 17:18:23 -0400	[thread overview]
Message-ID: <20080920211820.GA18095@betsy> (raw)
In-Reply-To: <20080919225310.429c9846@extreme>

On 10:53pm 09/19/08  , Stephen Hemminger wrote:
> On Fri, 19 Sep 2008 20:23:27 -0400
> Greg Fitzgerald <netzdamon@gmail.com> wrote:
> 
> > Hope I am sending this to the right place. Have the sky2 network card.
> > Internet will die out randomly, re-probing the sky2 module usually solves
> > the problem. According to dmesg the receiver is hanging.
> > 
> > sky2 eth0: hung mac 0:81 fifo 3 (86:89)
> > sky2 eth0: receiver hang detected
> > sky2 eth0: disabling interface
> > sky2 eth0: enabling interface
> > sky2 eth0: Link is up at 10 Mbps, half duplex, flow control none
> > sky2 eth0: hung mac 0:11 fifo 194 (51:45)
> > sky2 eth0: receiver hang detected
> > 
> > This top half happens 3 or 4 times, then I'll start to get this extra
> > output in dmesg after that.
> > 
> > sky2 eth0: disabling interface
> > ACPI: PCI interrupt for device 0000:02:00.0 disabled
> > ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 19 (level, low) -> IRQ 19
> > PCI: Setting latency timer of device 0000:02:00.0 to 64
> > sky2 0000:02:00.0: v1.21 addr 0xcdefc000 irq 19 Yukon-EC (0xb6) rev 2
> > sky2 eth0: addr 00:17:31:9b:ca:89
> > sky2 eth0: enabling interface
> > sky2 eth0: Link is up at 10 Mbps, half duplex, flow control none
> > sky2 eth0: disabling interface
> > sky2 eth0: enabling interface
> > sky2 eth0: Link is up at 10 Mbps, half duplex, flow control none
> > 
> > Some where in between all this, it actually gets to the point where I
> > totally loose my connection. Sometimes it will come back up and I'm
> > perfectly fine.
> > 
> > If I can provide any other information please let me know.
> > 
> > Oh, been having this problem for some time now. Current version of the
> > my kernel is 2.6.26.5.
> > 
> > --Greg
> 
> Haven't heard of this before. But since possibly a bad cable or PHY negotiation
> problem.  You might also check for firmware update from motherboard vendor.
> The message happens if a message gets stuck in the receive process and isn't
> making progress. Does it happen under load?  Is this really a half duplex 10mbit
> port or is it meant to be full duplex?

Cable is good, it was working just fine before on my 3com 905b, I did
plug it into my tester to be sure though. Motherboard has a tester that
should alert me as well. It's built into the bios. The nic port is full
duplex. Plugged directly into a westell wirespeed 2100 (ADSL Modem). Nic
is onboard, Asus P5DL2. I have the latest bios flashed from the website. 

As I said before its pretty random. I guess it does happen more often
under load though. Usually downloading a large iso is a quick way to
bring it down. It's not a sure thing though.

If there is any type of debugging I can do to provide more info would be
happy to do so.

Thanks.

  reply	other threads:[~2008-09-20 21:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-20  0:23 sky2 hangs Greg Fitzgerald
2008-09-20  5:53 ` Stephen Hemminger
2008-09-20 21:18   ` Greg Fitzgerald [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-02-01 18:55 Thomas Glanzmann
2007-02-01 19:05 ` Stephen Hemminger
2007-02-01 19:19   ` Thomas Glanzmann
2007-02-01 19:07 ` Stephen Hemminger
2007-02-01 19:16   ` Thomas Glanzmann
2007-02-01 22:46 ` Fagyal Csongor
2007-02-01 22:58   ` Stephen Hemminger
2007-02-02  6:31     ` Thomas Glanzmann
2007-02-02 10:44       ` Julien BLACHE
2007-02-02 10:49         ` Thomas Glanzmann
2007-02-02 11:53           ` Fagyal Csongor
2007-02-02 13:43             ` Jarek Poplawski
2007-02-02 14:13               ` Jarek Poplawski
2007-02-02  6:27   ` Thomas Glanzmann

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=20080920211820.GA18095@betsy \
    --to=netzdamon@gmail.com \
    --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).