From: Stephen Hemminger <shemminger@osdl.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: oe@hentges.net, 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: Thu, 28 Sep 2006 16:19:56 -0700 [thread overview]
Message-ID: <20060928161956.5262e5d3@freekitty> (raw)
In-Reply-To: <451C5599.80402@garzik.org>
On Thu, 28 Sep 2006 19:07:05 -0400
Jeff Garzik <jeff@garzik.org> wrote:
> Andrew Morton wrote:
> > Another customer..
> >
> > Begin forwarded message:
> >
> > Date: Fri, 29 Sep 2006 00:44:01 +0200
> > From: Matthias Hentges <oe@hentges.net>
> > To: Andrew Morton <akpm@osdl.org>
> > Cc: linux-kernel@vger.kernel.org
> > Subject: Re: 2.6.18-mm2
> >
> >
> > Hello all,
> >
> > I've just tested -mm2 on my C2D system and I'm getting a lot of these
> > messages:
> >
> > "[ 139.143807] printk: 131 messages suppressed.
> > [ 139.148235] sky2 0000:03:00.0: pci express error (0x500547)"
> >
> > Please note that the "sky2" driver has always been the black sheep on
> > that system due to regular full lock-ups of the driver, requiring a
> > rmmod sky2 + modprobe sky2 cycle.
> >
> > This happens often enough to warrant writing a cronjob checking the
> > network and auto-rmmod'ing the module.....
> >
> > While the above is bloody annoying at times (heh), the driver never
> > caused any messages like the ones I now get with -mm2 .
>
> sky2 just turned on PCI Express error reporting, so it makes sense that
> messages would appear. The better question is whether this is a driver
> problem, or a hardware problem. With your "black sheep" comment, I
> wonder if it isn't a hardware problem that's been hidden.
Here is the debug patch I sent to the first reporter of the problem.
I know what the offset is supposed to be, so if the PCI subsystem is
wrong, this will show.
--- sky2.orig/drivers/net/sky2.c 2006-09-28 08:45:27.000000000 -0700
+++ sky2/drivers/net/sky2.c 2006-09-28 08:51:24.000000000 -0700
@@ -2463,6 +2463,7 @@
sky2_write8(hw, B0_CTST, CS_MRST_CLR);
+#define PEX_UNC_ERR_STAT 0x104 /* PCI extended error capablity */
/* clear any PEX errors */
if (pci_find_capability(hw->pdev, PCI_CAP_ID_EXP)) {
hw->err_cap = pci_find_ext_capability(hw->pdev, PCI_EXT_CAP_ID_ERR);
@@ -2470,6 +2471,15 @@
sky2_pci_write32(hw,
hw->err_cap + PCI_ERR_UNCOR_STATUS,
0xffffffffUL);
+ else
+ printk(KERN_ERR PFX "pci express found but not extended error support?\n");
+
+ if (hw->err_cap + PCI_ERR_UNCOR_STATUS != PEX_UNC_ERR_STAT) {
+
+ printk(KERN_ERR PFX "pci express error status register fixed from %#x to %#x\n",
+ hw->err_cap, PEX_UNC_ERR_STAT - PCI_ERR_UNCOR_STATUS);
+ hw->err_cap = PEX_UNC_ERR_STAT - PCI_ERR_UNCOR_STATUS;
+ }
}
hw->pmd_type = sky2_read8(hw, B2_PMD_TYP);
next prev parent reply other threads:[~2006-09-28 23:20 UTC|newest]
Thread overview: 13+ 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 [this message]
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
2006-10-08 17:00 ` 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=20060928161956.5262e5d3@freekitty \
--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 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).