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: Tue, 3 Oct 2006 20:26:43 -0700 [thread overview]
Message-ID: <20061003202643.0e0ceab2@localhost.localdomain> (raw)
In-Reply-To: <1159930628.16765.9.camel@mhcln03>
On Wed, 04 Oct 2006 04:57:08 +0200
Matthias Hentges <oe@hentges.net> wrote:
> Hello Stephen,
>
> Am Donnerstag, den 28.09.2006, 16:19 -0700 schrieb Stephen Hemminger:
>
> > 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);
>
> while the above patch indeed removes the error messages from my previous
> mail, I have since seen random but reproduceable freezes of the box in
> question. I believe they are sky2 related since the freeze can be
> triggered by continuous network traffic (like playing a movie over NFS
> etc.).
When it fixes what does the log say. I'm probably going to back out
the PCI express extended error using the pci_XXX functions.
> The freezes only happen with 2.6.18-mm2 and 2.6.18-mm3. 2.6.18-mm1 works
> perfectly fine.
> I've hooked up the box to my laptop via a serial cable and captured all
> kernel messages from booting up the machine to the freeze. You'll note
> that the last messages are from the sky2 driver ;)
>
Does it still happen with linus git tree. If so, a git bisect might
help. It might not be sky2 related at all, there has been lots of changes.
> Once frozen the network is dead, the screen won't wake up from suspend
> and CAPSLOCK can not be toggled. SYSRQ (sp?) still works tho.
>
> Any help in debugging this problem would be appreciated =)
The TX timeout is a symptom of a common bug still not fixed where
the transmitter stops. I'm working on reproducing it on my hardware and switches,
because without a reproducible test, its just shooting in the dark and
that isn't working.
next prev parent reply other threads:[~2006-10-04 3:35 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 [this message]
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-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=20061003202643.0e0ceab2@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.