From: Stephen Hemminger <shemminger@osdl.org>
To: Matthias Hentges <oe@hentges.net>
Cc: Jeff Garzik <jeff@garzik.org>, Andrew Morton <akpm@osdl.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Netdev List <netdev@vger.kernel.org>
Subject: Re: sky2 (was Re: 2.6.18-mm2)
Date: Sun, 8 Oct 2006 09:20:01 -0700 [thread overview]
Message-ID: <20061008092001.0c83a359@localhost.localdomain> (raw)
In-Reply-To: <1160314905.4575.21.camel@mhcln03>
On Sun, 08 Oct 2006 15:41:45 +0200
Matthias Hentges <oe@hentges.net> wrote:
> Hi Stephen,
>
> I believe I have identified the problem. The freeze only happens when
> your debug patch to work around sky2 PCIe error messages is applied.
> Without your patch (attached) I get _tons_ of error messages and the NIC
> dies every few seconds / minutes (reproduceable!), but the system
> recovers just fine from a NIC crash.
>
> I have verified this behavior (works fine w/o debug patch, freezes with
> patch applied) with:
> - 2.6.19-rc1-git4
> - 2.6.18-git something
> - 2.6.18-mm3
>
Does 2.6.18 work?
What is the PCI config of the device (lspci -vvvx)?
What is the chip version (dmesg | grep sky2)?
next prev parent reply other threads:[~2006-10-08 16:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060928155053.7d8567ae.akpm@osdl.org>
2006-09-28 23:07 ` sky2 (was Re: 2.6.18-mm2) Jeff Garzik
2006-09-28 23:19 ` Stephen Hemminger
2006-09-30 0:26 ` Matthias Hentges
2006-10-04 2:57 ` Matthias Hentges
2006-10-04 3:26 ` Stephen Hemminger
2006-10-07 19:48 ` Matthias Hentges
2006-10-08 13:41 ` Matthias Hentges
2006-10-08 16:20 ` Stephen Hemminger [this message]
2006-10-08 17:00 ` Matthias Hentges
2006-10-08 18:31 ` Matthias Hentges
2006-10-09 16:45 ` Stephen Hemminger
2006-10-09 23:14 ` Oleg Verych
2006-10-15 4:27 ` Oleg Verych
2006-10-10 10:45 ` Matthias Hentges
2006-10-10 0:02 ` Beber
2006-09-28 23:25 ` Andrew Morton
2006-09-28 23:30 ` Stephen Hemminger
2006-09-29 16:04 ` Andrea Gelmini
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=20061008092001.0c83a359@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=akpm@osdl.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe@hentges.net \
/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.