netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Hentges <oe@hentges.net>
To: Stephen Hemminger <shemminger@osdl.org>
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, 08 Oct 2006 15:41:45 +0200	[thread overview]
Message-ID: <1160314905.4575.21.camel@mhcln03> (raw)
In-Reply-To: <1160250529.4575.7.camel@mhcln03>


[-- Attachment #1.1: Type: text/plain, Size: 584 bytes --]

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
  
-- 
Matthias 'CoreDump' Hentges 

My OS: Debian SID. Geek by Nature, Linux by Choice

[-- Attachment #1.2: sky2-pcie.patch --]
[-- Type: text/x-patch, Size: 1125 bytes --]

--- sky2.c.orig	2006-09-30 01:50:35.000000000 +0200
+++ sky2.c	2006-09-30 01:50:38.000000000 +0200
@@ -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,16 @@
 			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);

[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-10-08 13:41 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
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 [this message]
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=1160314905.4575.21.camel@mhcln03 \
    --to=oe@hentges.net \
    --cc=akpm@osdl.org \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@osdl.org \
    /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).