sky2 (was Re: 2.6.18-mm2)

sky2 (was Re: 2.6.18-mm2)

[Jeff Garzik]

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.

	Jeff

Re: sky2 (was Re: 2.6.18-mm2)

[Stephen Hemminger]

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

Re: sky2 (was Re: 2.6.18-mm2)

[Andrew Morton]

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

See also http://bugzilla.kernel.org/show_bug.cgi?id=7222

That's two reports in 18 hours, from amongst the presumably-small population
of sky2-owning -mm testers.

Re: sky2 (was Re: 2.6.18-mm2)

[Stephen Hemminger]

> 
> See also http://bugzilla.kernel.org/show_bug.cgi?id=7222
> 
> That's two reports in 18 hours, from amongst the presumably-small population
> of sky2-owning -mm testers.

I'll back it out if we don't get a simple resolution. It was just trying to
use the pci facilities as intended.

Note: I know what is causing all the sky2 problems, there is something wrong that
is causing flow control negotiation not to propagate back to all the multiple levels
of the chip. Unclear how to fix it, the documentation is not helpful on this.
If not resolved soon, I'll just force Tx flow control off for now.


-- 
Stephen Hemminger <shemminger@osdl.org>

Re: sky2 (was Re: 2.6.18-mm2)

[Andrea Gelmini]

On Thu, Sep 28, 2006 at 04:30:23PM -0700, Stephen Hemminger wrote:
> Note: I know what is causing all the sky2 problems, there is something wrong that
> is causing flow control negotiation not to propagate back to all the multiple levels
> of the chip. Unclear how to fix it, the documentation is not helpful on this.
> If not resolved soon, I'll just force Tx flow control off for now.

just for the record, same problem here.
I mean, with my Sony Vaio VGN-SZ1VP (here[1] you can find all hardware
details), it's enough some mega of udp traffic, usually nfs, to "freeze"
the network. Well, no complain from the kernel. It's enough to rmmod and
modprobe sky2 to fix the problem. I already tried -mm1, but nothing
changed. In the meanwhile I will continue to use my usb network card.

Thanks a lot for your time,
Andrea Gelmini

-------
[1] http://groups.google.it/group/linux.kernel/msg/ceff3014c410bea6 

Re: sky2 (was Re: 2.6.18-mm2)

[Matthias Hentges]

[-- Attachment #1.1: Type: text/plain, Size: 1126 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

[...]

Thanks for the patch:

+root@mhcln01:~ >dmesg |grep -i expres
[   36.814288] sky2 pci express found but not extended error support?
[   36.820494] sky2 pci express error status register fixed from 0x0 to
0x100
[   36.833769] sky2 0000:04:00.0: pci express error (0x100000)
[   36.851296] sky2 pci express found but not extended error support?
[   36.857499] sky2 pci express error status register fixed from 0x0 to
0x100
[   36.870756] sky2 0000:03:00.0: pci express error (0x100000)
+root@mhcln01:~ >

The annoying messages are gone =)
Attached is a complete dmesg of a fresh boot.

Thanks for your time.
-- 
Matthias Hentges 

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

[-- Attachment #1.2: dmesg_2.6.18-mm2-sky2-patched.txt.gz --]
[-- Type: application/x-gzip, Size: 9572 bytes --]

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

Re: sky2 (was Re: 2.6.18-mm2)

[Matthias Hentges]

[-- 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 --]

Re: sky2 (was Re: 2.6.18-mm2)

[Stephen Hemminger]

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.

Re: sky2 (was Re: 2.6.18-mm2)

[Matthias Hentges]

[-- Attachment #1: Type: text/plain, Size: 2001 bytes --]

Hello Stephen,

Am Dienstag, den 03.10.2006, 20:26 -0700 schrieb Stephen Hemminger:

[...]

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

I am doing a bisect right now which is kind of a PITA as the freeze is
completely random.
I have since noticed that the freeze happens shortly after the network
dies, possibly during the "rrmod sky2 / moprobe sky2" my script is
doing.

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

I'd be happy to assist with that as I have his bug up to 5 times a day :
\
-- 
Matthias 'CoreDump' Hentges 

Webmaster of hentges.net and OpenZaurus developer.
You can reach me in #openzaurus on Freenode.

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

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

Re: sky2 (was Re: 2.6.18-mm2)

[Matthias Hentges]

[-- 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 --]

Re: sky2 (was Re: 2.6.18-mm2)

[Stephen Hemminger]

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

Re: sky2 (was Re: 2.6.18-mm2)

[Matthias Hentges]

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

Am Sonntag, den 08.10.2006, 09:20 -0700 schrieb Stephen Hemminger:
> On Sun, 08 Oct 2006 15:41:45 +0200
> Matthias Hentges <oe@hentges.net> wrote:

[...]

> > 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?

2.6.18 does not require the patch ( in fact, the patch won't apply at
all) and thus does not freeze when the NIC goes down.

> What is the PCI config of the device (lspci -vvvx)?

I've attached the lspci dump of both onboard sky2 NICs.

> What is the chip version (dmesg | grep sky2)?
> 

+root@mhcln01:..patches/generic/coretemp >dmesg |grep sky2
[   34.833453] sky2 v1.7 addr 0xfa9fc000 irq 17 Yukon-EC (0xb6) rev 2
[   34.833527] sky2 eth0: addr 00:17:31:f4:f1:8c
[   34.833663] sky2 v1.7 addr 0xfa8fc000 irq 16 Yukon-EC (0xb6) rev 2
[   34.833729] sky2 eth1: addr 00:17:31:f4:f7:cc
[   42.165687] sky2 eth1: enabling interface
[   43.847972] sky2 eth1: Link is up at 100 Mbps, full duplex, flow
control both

-- 
Matthias 'CoreDump' Hentges 

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

[-- Attachment #1.2: lspci-vvvv_sky2-1.txt --]
[-- Type: text/plain, Size: 1533 bytes --]

03:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053 PCI-E Gigabit Ethernet Controller (rev 20)
	Subsystem: ASUSTeK Computer Inc. Marvell 88E8053 Gigabit Ethernet controller PCIe (Asus)
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size: 16 bytes
	Interrupt: pin A routed to IRQ 216
	Region 0: Memory at fa8fc000 (64-bit, non-prefetchable) [size=16K]
	Region 2: I/O ports at a800 [size=256]
	Expansion ROM at fa8c0000 [disabled] [size=128K]
	Capabilities: [48] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=1 PME-
	Capabilities: [50] Vital Product Data
	Capabilities: [5c] Message Signalled Interrupts: Mask- 64bit+ Queue=0/1 Enable+
		Address: 00000000fee0100c  Data: 4152
	Capabilities: [e0] Express Legacy Endpoint IRQ 0
		Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag-
		Device: Latency L0s unlimited, L1 unlimited
		Device: AtnBtn- AtnInd- PwrInd-
		Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
		Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
		Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
		Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s, Port 0
		Link: Latency L0s <256ns, L1 unlimited
		Link: ASPM Disabled RCB 128 bytes CommClk+ ExtSynch-
		Link: Speed 2.5Gb/s, Width x1


[-- Attachment #1.3: lspci-vvvv_sky2-2.txt --]
[-- Type: text/plain, Size: 1533 bytes --]

04:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053 PCI-E Gigabit Ethernet Controller (rev 20)
	Subsystem: ASUSTeK Computer Inc. Marvell 88E8053 Gigabit Ethernet controller PCIe (Asus)
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size: 16 bytes
	Interrupt: pin A routed to IRQ 217
	Region 0: Memory at fa9fc000 (64-bit, non-prefetchable) [size=16K]
	Region 2: I/O ports at b800 [size=256]
	Expansion ROM at fa9c0000 [disabled] [size=128K]
	Capabilities: [48] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=1 PME-
	Capabilities: [50] Vital Product Data
	Capabilities: [5c] Message Signalled Interrupts: Mask- 64bit+ Queue=0/1 Enable+
		Address: 00000000fee0300c  Data: 414a
	Capabilities: [e0] Express Legacy Endpoint IRQ 0
		Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag-
		Device: Latency L0s unlimited, L1 unlimited
		Device: AtnBtn- AtnInd- PwrInd-
		Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
		Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
		Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
		Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s, Port 0
		Link: Latency L0s <256ns, L1 unlimited
		Link: ASPM Disabled RCB 128 bytes CommClk+ ExtSynch-
		Link: Speed 2.5Gb/s, Width x1


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

Re: sky2 (was Re: 2.6.18-mm2)

[Beber]

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

Le Sun, 8 Oct 2006 09:20:01 -0700, Stephen Hemminger
<shemminger@osdl.org> a écrit :

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

I've got the same issue here since a while (See Message-ID:
<1d7ea2d50604181027o55d9cc43i5a7d912e388387a4@mail.gmail.com> from 18 Apr 2006)

I steel get freeze (with non tainted kernel) and getting these messages
at boot :

~ % dmesg | grep -i sky
sky2 v1.7 addr 0xff3fc000 irq 233 Yukon-EC (0xb6) rev 2
sky2 eth0: addr 00:15:f2:a9:6a:65
sky2 0000:02:00.0: No interrupt was generated using MSI, switching to INTx mode. Please report this failure to the PCI maintainer and include system chipset information.
sky2 eth0: enabling interface
sky2 eth0: disabling interface

lspci -vvvx attached

-- 
Beber - E-Mail / Jabber (+GMail) : beber_AT_meleeweb.net
http://www.meleeweb.net

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: lspci.log --]
[-- Type: text/x-log; name=lspci.log, Size: 23526 bytes --]

00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
	Subsystem: ASUSTeK Computer Inc. Unknown device 81d2
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Capabilities: <access denied>
00: de 10 f4 02 06 01 b0 00 a2 00 00 05 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 d2 81
30: 00 00 00 00 44 00 00 00 00 00 00 00 ff 00 00 00

00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2)
	Subsystem: ASUSTeK Computer Inc. Unknown device 81d2
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
00: de 10 fa 02 00 01 20 00 a2 00 00 05 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 d2 81
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2)
	Subsystem: ASUSTeK Computer Inc. Unknown device 81d2
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
00: de 10 fe 02 00 00 20 00 a2 00 00 05 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 d2 81
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2)
	Subsystem: ASUSTeK Computer Inc. Unknown device 81d2
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
00: de 10 f8 02 00 01 a0 00 a2 00 00 05 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 d2 81
30: 00 00 00 00 00 00 00 00 00 00 00 00 ff 00 00 00

00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2)
	Subsystem: ASUSTeK Computer Inc. Unknown device 81d2
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
00: de 10 f9 02 06 01 a0 00 a2 00 00 05 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 d2 81
30: 00 00 00 00 00 00 00 00 00 00 00 00 ff 00 00 00

00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
	Subsystem: ASUSTeK Computer Inc. Unknown device 81d2
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Capabilities: <access denied>
00: de 10 ff 02 06 01 b0 00 a2 00 00 05 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 d2 81
30: 00 00 00 00 44 00 00 00 00 00 00 00 ff 00 00 00

00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2)
	Subsystem: ASUSTeK Computer Inc. Unknown device 81d2
	Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
00: de 10 7f 02 02 01 20 00 a2 00 00 05 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 d2 81
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2)
	Subsystem: ASUSTeK Computer Inc. Unknown device 81d2
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
00: de 10 7e 02 00 00 20 00 a2 00 00 05 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 d2 81
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:02.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size: 64 bytes
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: 00007000-00007fff
	Memory behind bridge: ff100000-ff2fffff
	Prefetchable memory behind bridge: 00000000fff00000-0000000000000000
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset- FastB2B-
	Capabilities: <access denied>
00: de 10 fc 02 07 04 10 00 a1 00 04 06 10 00 01 00
10: 00 00 00 00 00 00 00 00 00 01 01 00 71 71 00 00
20: 10 ff 20 ff f1 ff 01 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 40 00 00 00 00 00 00 00 00 00 02 00

00:03.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size: 64 bytes
	Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
	I/O behind bridge: 00008000-00008fff
	Memory behind bridge: ff300000-ff3fffff
	Prefetchable memory behind bridge: 00000000fff00000-0000000000000000
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset- FastB2B-
	Capabilities: <access denied>
00: de 10 fd 02 07 04 10 00 a1 00 04 06 10 00 01 00
10: 00 00 00 00 00 00 00 00 00 02 02 00 81 81 00 00
20: 30 ff 30 ff f1 ff 01 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 40 00 00 00 00 00 00 00 00 00 02 00

00:04.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size: 64 bytes
	Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
	I/O behind bridge: 00009000-0000bfff
	Memory behind bridge: ff400000-ff4fffff
	Prefetchable memory behind bridge: 00000000cff00000-00000000dfe00000
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR+ NoISA- VGA+ MAbort- >Reset- FastB2B-
	Capabilities: <access denied>
00: de 10 fb 02 07 04 10 00 a1 00 04 06 10 00 01 00
10: 00 00 00 00 00 00 00 00 00 03 03 00 91 b1 00 00
20: 40 ff 40 ff f1 cf e1 df 00 00 00 00 00 00 00 00
30: 00 00 00 00 40 00 00 00 00 00 00 00 00 00 0a 00

00:09.0 Memory controller: nVidia Corporation CK804 Memory Controller (rev a4)
	Subsystem: ASUSTeK Computer Inc. Unknown device 815a
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Capabilities: <access denied>
00: de 10 5e 00 06 00 b0 00 a4 00 80 05 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 5a 81
30: 00 00 00 00 44 00 00 00 00 00 00 00 00 00 00 00

00:0a.0 ISA bridge: nVidia Corporation CK804 ISA Bridge (rev a4)
	Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard
	Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
00: de 10 50 00 0f 00 a0 00 a4 00 01 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 5a 81
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:0a.1 SMBus: nVidia Corporation CK804 SMBus (rev a2)
	Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard
	Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Interrupt: pin A routed to IRQ 10
	Region 0: I/O ports at ec00 [size=32]
	Region 4: I/O ports at 0600 [size=64]
	Region 5: I/O ports at 0700 [size=64]
	Capabilities: <access denied>
00: de 10 52 00 01 00 b0 00 a2 00 05 0c 00 00 80 00
10: 01 ec 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 06 00 00 01 07 00 00 00 00 00 00 43 10 5a 81
30: 00 00 00 00 44 00 00 00 00 00 00 00 0a 01 03 01

00:0b.0 USB Controller: nVidia Corporation CK804 USB Controller (rev a2) (prog-if 10 [OHCI])
	Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0 (750ns min, 250ns max)
	Interrupt: pin A routed to IRQ 10
	Region 0: Memory at ff6fe000 (32-bit, non-prefetchable) [size=4K]
	Capabilities: <access denied>
00: de 10 5a 00 07 00 b0 00 a2 10 03 0c 00 00 80 00
10: 00 e0 6f ff 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 5a 81
30: 00 00 00 00 44 00 00 00 00 00 00 00 0a 01 03 01

00:0b.1 USB Controller: nVidia Corporation CK804 USB Controller (rev a4) (prog-if 20 [EHCI])
	Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0 (750ns min, 250ns max)
	Interrupt: pin B routed to IRQ 66
	Region 0: Memory at ff6ffc00 (32-bit, non-prefetchable) [size=256]
	Capabilities: <access denied>
00: de 10 5b 00 06 00 b0 00 a4 20 03 0c 00 00 80 00
10: 00 fc 6f ff 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 5a 81
30: 00 00 00 00 44 00 00 00 00 00 00 00 0a 02 03 01

00:0d.0 Multimedia audio controller: nVidia Corporation CK804 AC'97 Audio Controller (rev a2)
	Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0 (500ns min, 1250ns max)
	Interrupt: pin A routed to IRQ 74
	Region 0: I/O ports at e400 [size=256]
	Region 1: I/O ports at e000 [size=256]
	Region 2: Memory at ff6fd000 (32-bit, non-prefetchable) [size=4K]
	Capabilities: <access denied>
00: de 10 59 00 07 00 b0 00 a2 00 01 04 00 00 00 00
10: 01 e4 00 00 01 e0 00 00 00 d0 6f ff 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 2a 81
30: 00 00 00 00 44 00 00 00 00 00 00 00 0a 01 02 05

00:0f.0 IDE interface: nVidia Corporation CK804 IDE (rev f3) (prog-if 8a [Master SecP PriP])
	Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0 (750ns min, 250ns max)
	Region 4: I/O ports at ffa0 [size=16]
	Capabilities: <access denied>
00: de 10 53 00 05 00 b0 00 f3 8a 01 01 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: a1 ff 00 00 00 00 00 00 00 00 00 00 43 10 5a 81
30: 00 00 00 00 44 00 00 00 00 00 00 00 00 00 03 01

00:10.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev f3) (prog-if 85 [Master SecO PriO])
	Subsystem: ASUSTeK Computer Inc. Unknown device 815a
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0 (750ns min, 250ns max)
	Interrupt: pin A routed to IRQ 225
	Region 0: I/O ports at dc00 [size=8]
	Region 1: I/O ports at d880 [size=4]
	Region 2: I/O ports at d800 [size=8]
	Region 3: I/O ports at d480 [size=4]
	Region 4: I/O ports at d400 [size=16]
	Region 5: Memory at ff6fc000 (32-bit, non-prefetchable) [size=4K]
	Capabilities: <access denied>
00: de 10 54 00 07 00 b0 00 f3 85 01 01 00 00 00 00
10: 01 dc 00 00 81 d8 00 00 01 d8 00 00 81 d4 00 00
20: 01 d4 00 00 00 c0 6f ff 00 00 00 00 43 10 5a 81
30: 00 00 00 00 44 00 00 00 00 00 00 00 0b 01 03 01

00:12.0 PCI bridge: nVidia Corporation CK804 PCI Bridge (rev a2) (prog-if 01 [Subtractive decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Bus: primary=00, secondary=04, subordinate=04, sec-latency=64
	I/O behind bridge: 0000c000-0000cfff
	Memory behind bridge: ff500000-ff5fffff
	Prefetchable memory behind bridge: 50000000-500fffff
	Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset- FastB2B-
00: de 10 5c 00 07 00 a0 00 a2 01 04 06 00 00 01 00
10: 00 00 00 00 00 00 00 00 00 04 04 40 c0 c0 80 22
20: 50 ff 50 ff 00 50 00 50 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 06

00:13.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev a3)
	Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0 (250ns min, 5000ns max)
	Interrupt: pin A routed to IRQ 10
	Region 0: Memory at ff6fb000 (32-bit, non-prefetchable) [size=4K]
	Region 1: I/O ports at d080 [size=8]
	Capabilities: <access denied>
00: de 10 57 00 07 00 b0 00 a3 00 80 06 00 00 00 00
10: 00 b0 6f ff 81 d0 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 41 81
30: 00 00 00 00 44 00 00 00 00 00 00 00 0a 01 01 14

00:16.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) (prog-if 00 [Normal decode])
	Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size: 64 bytes
	Bus: primary=00, secondary=05, subordinate=05, sec-latency=0
	I/O behind bridge: 0000f000-00000fff
	Memory behind bridge: fff00000-000fffff
	Prefetchable memory behind bridge: 00000000fff00000-0000000000000000
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset- FastB2B-
	Capabilities: <access denied>
00: de 10 5d 00 04 04 10 00 a3 00 04 06 10 00 01 00
10: 00 00 00 00 00 00 00 00 00 05 05 00 f1 01 00 00
20: f0 ff 00 00 f1 ff 01 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 40 00 00 00 00 00 00 00 00 00 02 00

00:17.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) (prog-if 00 [Normal decode])
	Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size: 64 bytes
	Bus: primary=00, secondary=06, subordinate=06, sec-latency=0
	I/O behind bridge: 0000f000-00000fff
	Memory behind bridge: fff00000-000fffff
	Prefetchable memory behind bridge: 00000000fff00000-0000000000000000
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset- FastB2B-
	Capabilities: <access denied>
00: de 10 5d 00 04 04 10 00 a3 00 04 06 10 00 01 00
10: 00 00 00 00 00 00 00 00 00 06 06 00 f1 01 00 00
20: f0 ff 00 00 f1 ff 01 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 40 00 00 00 00 00 00 00 00 00 02 00

00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Capabilities: <access denied>
00: 22 10 00 11 00 00 10 00 00 00 00 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 80 00 00 00 00 00 00 00 00 00 00 00

00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
00: 22 10 01 11 00 00 00 00 00 00 00 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
00: 22 10 02 11 00 00 00 00 00 00 00 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
00: 22 10 03 11 00 00 00 00 00 00 00 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

01:00.0 RAID bus controller: Silicon Image, Inc. SiI 3132 Serial ATA Raid II Controller (rev 01)
	Subsystem: ASUSTeK Computer Inc. Unknown device 8177
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 10
	Region 0: Memory at ff2ffc00 (64-bit, non-prefetchable) [size=128]
	Region 2: Memory at ff2f8000 (64-bit, non-prefetchable) [size=16K]
	Region 4: I/O ports at 7c00 [size=128]
	Expansion ROM at ff200000 [disabled] [size=512K]
	Capabilities: <access denied>
00: 95 10 32 31 07 01 10 00 01 00 04 01 10 00 00 00
10: 04 fc 2f ff 00 00 00 00 04 80 2f ff 00 00 00 00
20: 01 7c 00 00 00 00 00 00 00 00 00 00 43 10 77 81
30: 00 00 20 ff 54 00 00 00 00 00 00 00 0a 01 00 00

02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053 PCI-E Gigabit Ethernet Controller (rev 15)
	Subsystem: ASUSTeK Computer Inc. Marvell 88E8053 Gigabit Ethernet controller PCIe (Asus)
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 233
	Region 0: Memory at ff3fc000 (64-bit, non-prefetchable) [size=16K]
	Region 2: I/O ports at 8800 [size=256]
	Expansion ROM at ff3c0000 [disabled] [size=128K]
	Capabilities: <access denied>
00: ab 11 62 43 07 01 10 00 15 00 00 02 10 00 00 00
10: 04 c0 3f ff 00 00 00 00 01 88 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 42 81
30: 00 00 3c ff 48 00 00 00 00 00 00 00 0a 01 00 00

03:00.0 VGA compatible controller: ATI Technologies Inc R430 [Radeon X800 (PCIE)] (prog-if 00 [VGA])
	Subsystem: Micro-Star International Co., Ltd. Unknown device 0970
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 10
	Region 0: Memory at d0000000 (64-bit, prefetchable) [size=128M]
	Region 2: Memory at ff4f0000 (64-bit, non-prefetchable) [size=64K]
	Region 4: I/O ports at b000 [size=256]
	Expansion ROM at ff4c0000 [disabled] [size=128K]
	Capabilities: <access denied>
00: 02 10 4f 55 07 00 10 00 00 00 00 03 10 00 80 00
10: 0c 00 00 d0 00 00 00 00 04 00 4f ff 00 00 00 00
20: 01 b0 00 00 00 00 00 00 00 00 00 00 62 14 70 09
30: 00 00 4c ff 50 00 00 00 00 00 00 00 0a 01 00 00

03:00.1 Display controller: ATI Technologies Inc R430 [Radeon X800 (PCIE) Secondary]
	Subsystem: Micro-Star International Co., Ltd. Unknown device 0971
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size: 64 bytes
	Region 0: Memory at ff4e0000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: <access denied>
00: 02 10 6f 55 07 00 10 00 00 00 80 03 10 00 00 00
10: 04 00 4e ff 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 62 14 71 09
30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 00 00 00

04:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
	Subsystem: Realtek Semiconductor Co., Ltd. RT8139
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 64 (8000ns min, 16000ns max)
	Interrupt: pin A routed to IRQ 58
	Region 0: I/O ports at c800 [size=256]
	Region 1: Memory at ff5ffc00 (32-bit, non-prefetchable) [size=256]
	Expansion ROM at 50000000 [disabled] [size=64K]
	Capabilities: <access denied>
00: ec 10 39 81 07 01 90 02 10 00 00 02 00 40 00 00
10: 01 c8 00 00 00 fc 5f ff 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 ec 10 39 81
30: 00 00 5e ff 50 00 00 00 00 00 00 00 0a 01 20 40

04:0b.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) (prog-if 10 [OHCI])
	Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 64 (500ns min, 1000ns max), Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 10
	Region 0: Memory at ff5ff000 (32-bit, non-prefetchable) [size=2K]
	Region 1: Memory at ff5f8000 (32-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
00: 4c 10 23 80 16 01 10 02 00 10 00 0c 10 40 00 00
10: 00 f0 5f ff 00 80 5f ff 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 8b 80
30: 00 00 00 00 44 00 00 00 00 00 00 00 0a 01 02 04


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]