Re: sky2 (was Re: 2.6.18-mm2)

[Matthias Hentges <oe@hentges.net>]

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

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.).

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 ;)

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

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

[-- Attachment #1.2: p5w-freeze_2.6.18-mm3.cap.gz --]
[-- Type: application/x-gzip, Size: 10666 bytes --]

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