netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Tino Keitel <tino.keitel@tikei.de>
Cc: netdev@vger.kernel.org
Subject: Re: sky2 hangs without any messages
Date: Wed, 27 Jun 2007 13:31:06 -0400	[thread overview]
Message-ID: <20070627133106.7cf1ce5c@oldman> (raw)
In-Reply-To: <20070523075431.GA15935@dose.home.local>

On Wed, 23 May 2007 09:54:31 +0200
Tino Keitel <tino.keitel@tikei.de> wrote:

> Hi folks,
> 
> in the last 2 days, I had 2 outages of the NIC of my Mac mini Core Duo.
> I checked the kernel log but I found nothing sky2 related. After
> reloading the module, the interface worked again.
> 
> Both freezes were connected to access from a remote NFS client to a
> directory with ~4700 files in it. Both times, after reloading the
> module and waiting some minutes until the NFS client had recovered from
> the hanging NFS server, the same action worked.
> 
> The network is 100 mbit full duplex. I use NFS over TCP and kernel
> 2.6.21 with the "disable flow control" patch, the configuration is
> attached.
> 
> Here are the sky2 messages that appeared when I discovered the freeze
> and reloaded the driver:
> 
> sky2 eth0: disabling interface
> ACPI: PCI interrupt for device 0000:01:00.0 disabled
> ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 17
> PCI: Setting latency timer of device 0000:01:00.0 to 64
> sky2 0000:01:00.0: v1.14 addr 0x90200000 irq 17 Yukon-EC (0xb6) rev 2
> Device driver eth0 lacks bus and class support for being resumed.
> sky2 eth0: addr 00:16:cb:a4:e1:68
> sky2 eth0: enabling interface
> sky2 eth0: ram buffer 48K
> sky2 eth0: Link is up at 100 Mbps, full duplex, flow control none
> 


There is a reproducible hang (due to missed IRQ) in sky2.  It is more reproducible
with slower CPU's like Mac Mini.

  parent reply	other threads:[~2007-06-27 17:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-23  7:54 sky2 hangs without any messages Tino Keitel
2007-05-23 14:50 ` Stephen Hemminger
2007-05-23 15:01   ` Tino Keitel
2007-05-23 15:49     ` Stephen Hemminger
2007-06-27 17:31 ` Stephen Hemminger [this message]
     [not found] <6278d2220707020315q7c3df1cci5c7bb52316ad6081@mail.gmail.com>
2007-07-02 10:17 ` Daniel J Blueman
     [not found] ` <20070703123546.5d41410b@freepuppy.localdomain.hemminger.net>
     [not found]   ` <6278d2220707031402o7b13e45egc564076a1114b6f5@mail.gmail.com>
     [not found]     ` <6278d2220707050609s3579915bo50cf259ba73712f4@mail.gmail.com>
     [not found]       ` <20070705101046.542c1f8e@freepuppy.localdomain.hemminger.net>
2007-07-11 10:15         ` Daniel J Blueman
2007-07-11 15:27           ` Stephen Hemminger
2007-07-11 15:43             ` Daniel J Blueman
2007-07-11 21:39               ` Daniel J Blueman
2007-07-11 21:45                 ` Stephen Hemminger
2007-07-11 22:21                   ` Daniel J Blueman
2007-07-11 22:55                     ` Daniel J Blueman
2007-07-12  1:46                       ` Stephen Hemminger
2007-07-12 21:29                         ` Daniel J Blueman
2007-07-12 21:43                           ` Stephen Hemminger
2007-07-13  8:53                             ` 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=20070627133106.7cf1ce5c@oldman \
    --to=shemminger@linux-foundation.org \
    --cc=netdev@vger.kernel.org \
    --cc=tino.keitel@tikei.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;
as well as URLs for NNTP newsgroup(s).