Bug 176219 - [2.6.21 regression] sky2 88E8056 support disabled
Bug#: 176219 Product:  Gentoo Linux Version: unspecified Platform: AMD64
OS/Version: Linux Status: RESOLVED Severity: major Priority: P2
Resolution: FIXED Assigned To: dsd@gentoo.org Reported By: paapaa125@hotmail.com
Component: Core system
URL: 
Summary: [2.6.21 regression] sky2 88E8056 support disabled
Keywords:  
Status Whiteboard: linux-2.6.21-regression
Opened: 2007-04-27 09:10 0000
Description:   Opened: 2007-04-27 09:10 0000 
"Not working" == gives no signs of itself.

My eth0 works fine with 2.6.20 with SKY2 driver (I have CONFIG_SKY2=y).The
normal output of "dmesg | grep -i sky" with 2.6.20 is:

sky2 v1.10 addr 0xfeafc000 irq 17 Yukon-EC Ultra (0xb4) rev 2
sky2 eth0: addr 00:18:f3:4f:5f:5e
sky2 eth0: enabling interface
sky2 eth0: ram buffer 0K
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control none

With 2.6.21 "dmesg | grep -i sky" gives nothing at all and obviously network is
not working. "lspci" gives:

02:00.0 Ethernet controller: Marvell Technology Group Ltd. Unknown device 4364
(rev 12)

This is the integrated gigabit network controller of Asus P5B Deluxe
motherboard.I believe it is Marvell Yukon 88E8056.

Reproducible: Always

------- Comment #1 From paapaa125@hotmail.com 2007-04-27 12:48:12 0000 ------- 
Ok, I found this in 2.6.21 changelog:


commit 0a17e4c252ce951615f3c1fccae6d6262c8d4187
Author: Stephen Hemminger <shemminger@linux-foundation.org>
Date:   Wed Apr 11 14:47:58 2007 -0700

    sky2: disable support for 88E8056

    This device is having all sorts of problems that lead to data corruption
    and system instability.  It gets receive status and data out of order,
    it generates descriptor and TSO errors, etc.

    Until the problems are resolved, it should not be used by anyone
    who cares about there system.

    Signed-off-by: Stephen Hemminger <shemminger@linux-foundation.org>
    Signed-off-by: Jeff Garzik <jeff@garzik.org>

------- Comment #2 From Daniel Drake 2007-04-27 15:07:32 0000 ------- 
Please post output of "lspci -vvxnns 02:00.0"

------- Comment #3 From paapaa125@hotmail.com 2007-04-27 19:05:50 0000 ------- 
"lspci -vvxnns 02:00.0":

02:00.0 0200: 11ab:4364 (rev 12)
        Subsystem: 1148:4340
        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: 32 bytes
        Interrupt: pin A routed to IRQ 17
        Region 0: Memory at feafc000 (64-bit, non-prefetchable) [size=16K]
        Region 2: I/O ports at d800 [size=256]
        Expansion ROM at feac0000 [disabled] [size=128K]
        Capabilities: [48] Power Management version 3
                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: 64bit+ Queue=0/0
Enable-
                Address: 0000000000000000  Data: 0000
        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 L1, Port 0
                Link: Latency L0s <256ns, L1 unlimited
                Link: ASPM Disabled RCB 128 bytes CommClk+ ExtSynch-
                Link: Speed 2.5Gb/s, Width x1
00: ab 11 64 43 07 00 10 00 12 00 00 02 08 00 00 00
10: 04 c0 af fe 00 00 00 00 01 d8 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 48 11 40 43
30: 00 00 ac fe 48 00 00 00 00 00 00 00 0a 01 00 00


(This was using gentoo-sources-2.6.20-r6)

------- Comment #4 From Daniel Drake 2007-04-27 22:12:46 0000 ------- 
Thanks, we'll re-enable that hardware for the next release

------- Comment #5 From paapaa125@hotmail.com 2007-04-27 22:22:22 0000 ------- 
The real question is: how come I didn't have problems with 4364 (==8056?) and
others did? 

And if the support was disabled is it really safe to re-enable it?

------- Comment #6 From Daniel Drake 2007-04-27 23:12:51 0000 ------- 
The problem was only observed on Gigabyte boards. Stephen (the driver author)
will either enable all Asus 8056s, or yours in particular (plus maybe 1 or 2
more). We'll backport that patch as soon as it becomes available.

------- Comment #7 From Robert Tate 2007-04-28 01:31:42 0000 ------- 
The driver in 2.6.21 also appears to work fine on my Gigabyte DQ6 board --
apparently not all Gigabyte boards have the problem.

"lspci -vvxnns 03:00.0" reports:
03:00.0 0200: 11ab:4364 (rev 12)
        Subsystem: 1458:e000
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Step
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- 
        Latency: 0, Cache Line Size: 32 bytes
        Interrupt: pin A routed to IRQ 219
        Region 0: Memory at f7000000 (64-bit, non-prefetchable) [size=16K]
        Region 2: I/O ports at 7000 [size=256]
        [virtual] Expansion ROM at 40000000 [disabled] [size=128K]
        Capabilities: [48] Power Management version 3
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot
                Status: D0 PME-Enable- DSel=0 DScale=1 PME-
        Capabilities: [50] Vital Product Data
        Capabilities: [5c] Message Signalled Interrupts: 64bit+ Queue=0/0
Enable
                Address: 00000000fee0300c  Data: 413a
        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 L1, Port 0
                Link: Latency L0s <256ns, L1 unlimited
                Link: ASPM Disabled RCB 128 bytes CommClk- ExtSynch-
                Link: Speed 2.5Gb/s, Width x1
        Capabilities: [100] Advanced Error Reporting
00: ab 11 64 43 07 04 10 00 12 00 00 02 08 00 00 00
10: 04 00 00 f7 00 00 00 00 01 70 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 58 14 00 e0
30: 00 00 00 00 48 00 00 00 00 00 00 00 0a 01 00 00

------- Comment #8 From Robert Tate 2007-04-28 01:43:20 0000 ------- 
(In reply to comment #7)
> The driver in 2.6.21 also appears to work fine on my Gigabyte DQ6 board --
> apparently not all Gigabyte boards have the problem.

Sorry the ends of a few of the lines got cut off.  "lspci -vvxnns 03:00.0"
reports:
03:00.0 0200: 11ab:4364 (rev 12)
        Subsystem: 1458:e000
        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: 32 bytes
        Interrupt: pin A routed to IRQ 219
        Region 0: Memory at f7000000 (64-bit, non-prefetchable) [size=16K]
        Region 2: I/O ports at 7000 [size=256]
        [virtual] Expansion ROM at 40000000 [disabled] [size=128K]
        Capabilities: [48] Power Management version 3
                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: 64bit+ Queue=0/0
Enable+
                Address: 00000000fee0300c  Data: 413a
        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 L1, Port 0
                Link: Latency L0s <256ns, L1 unlimited
                Link: ASPM Disabled RCB 128 bytes CommClk- ExtSynch-
                Link: Speed 2.5Gb/s, Width x1
        Capabilities: [100] Advanced Error Reporting
00: ab 11 64 43 07 04 10 00 12 00 00 02 08 00 00 00
10: 04 00 00 f7 00 00 00 00 01 70 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 58 14 00 e0
30: 00 00 00 00 48 00 00 00 00 00 00 00 0a 01 00 00

------- Comment #9 From Daniel Drake 2007-04-28 01:51:56 0000 ------- 
Thanks, sent that one up as well. I assume you mean 2.6.20 (or do you mean
2.6.21 with the ifdef removed?)

------- Comment #10 From Vladi 2007-04-28 05:02:43 0000 ------- 
Kernel 2.6.21-rc7: Gigabyte S3 with 88E8056 works fine for more then a week
(100 Mbps link). Maybe the problem exists only for 1000Mbps links? At the
moment I'm using 2.6.21 with the original Marvell driver (patched sk98lin) and
it works fine for a couple of days.
sk98lin: Network Device Driver v10.0.5.3
(C)Copyright 1999-2007 Marvell(R).
eth0: Marvell Yukon 88E8056 Gigabit Ethernet Controller
      PrefPort:A  RlmtMode:Check Link State

------- Comment #11 From Mark 2007-04-28 06:24:32 0000 ------- 
Here's my output from a gigabyte ds3 that's been working fine with 2.6.20.  I'm
about to test it on 2.6.21 with ifdef removed and will post again if I have any
problems.

04:00.0 Ethernet controller [0200]: Marvell Technology Group Ltd. Unknown
device [11ab:4364] (rev 12)
        Subsystem: Giga-byte Technology Unknown device [1458:e000]
        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: 32 bytes
        Interrupt: pin A routed to IRQ 16
        Region 0: Memory at f8000000 (64-bit, non-prefetchable) [size=16K]
        Region 2: I/O ports at 8000 [size=256]
        [virtual] Expansion ROM at 40000000 [disabled] [size=128K]
        Capabilities: [48] Power Management version 3
                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/0
Enable-
                Address: 0000000000000000  Data: 0000
        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 L1, Port 0
                Link: Latency L0s <256ns, L1 unlimited
                Link: ASPM Disabled RCB 128 bytes CommClk- ExtSynch-
                Link: Speed 2.5Gb/s, Width x1
        Capabilities: [100] Advanced Error Reporting
00: ab 11 64 43 07 00 10 00 12 00 00 02 08 00 00 00
10: 04 00 00 f8 00 00 00 00 01 80 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 58 14 00 e0
30: 00 00 00 00 48 00 00 00 00 00 00 00 0b 01 00 00

------- Comment #12 From Robert Tate 2007-04-28 17:40:34 0000 ------- 
(In reply to comment #9)
> Thanks, sent that one up as well. I assume you mean 2.6.20 (or do you mean
> 2.6.21 with the ifdef removed?)
> 

I meant 2.6.21 with the #ifdef removed.  (BTW, it is a 100Mbps link.)

------- Comment #13 From paapaa125@hotmail.com 2007-04-28 21:56:12 0000 ------- 
I also want to report back that my system is working perfectly using 2.6.21 and
sky2 with my adapter (8056) enabled.(ifdef just removed).

And as a bonus I now have flow control which was previously disabled :)

------- Comment #14 From Simon Griph 2007-04-29 23:17:00 0000 ------- 
I've had no problems at all, 6 weeks uptime with 2.6.20.3;
asus p5b-e plus mainboard.

02:00.0 0200: 11ab:4364 (rev 12)
        Subsystem: 1043:81f8
        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: 32 bytes
        Interrupt: pin A routed to IRQ 17
        Region 0: Memory at fe8fc000 (64-bit, non-prefetchable) [size=16K]
        Region 2: I/O ports at a800 [size=256]
        Expansion ROM at fe8c0000 [disabled] [size=128K]
        Capabilities: [48] Power Management version 3
                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: 64bit+ Queue=0/0
Enable-
                Address: 0000000000000000  Data: 0000
        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 L1, Port 0
                Link: Latency L0s <256ns, L1 unlimited
                Link: ASPM Disabled RCB 128 bytes CommClk+ ExtSynch-
                Link: Speed 2.5Gb/s, Width x1
00: ab 11 64 43 07 00 10 00 12 00 00 02 08 00 00 00
10: 04 c0 8f fe 00 00 00 00 01 a8 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 f8 81
30: 00 00 8c fe 48 00 00 00 00 00 00 00 0a 01 00 00

------- Comment #15 From Daniel Drake 2007-05-01 13:57:24 0000 ------- 
(In reply to comment #10)
> Kernel 2.6.21-rc7: Gigabyte S3 with 88E8056 works fine for more then a week

Please post lspci output for this device like others have done.

------- Comment #16 From Daniel Drake 2007-05-02 23:06:51 0000 ------- 
Can someone with a gigabyte board who is affected by this issue please show the
sky2 chip information from dmseg?

For example: comment #0 includes "sky2 v1.10 addr 0xfeafc000 irq 17 Yukon-EC
Ultra (0xb4) rev 2"
I'd like to see this info from a gigabyte board or 2.

------- Comment #17 From Daniel Drake 2007-05-03 17:49:38 0000 ------- 
Vladi: please see comment #16

------- Comment #18 From Mark 2007-05-03 18:37:10 0000 ------- 
(In reply to comment #16)
> Can someone with a gigabyte board who is affected by this issue please show the
> sky2 chip information from dmseg?

This is from my gigabyte ds3:

sky2 0000:04:00.0: v1.14 addr 0xf8000000 irq 16 Yukon-EC Ultra (0xb4) rev 2

------- Comment #19 From Vladi 2007-05-04 04:31:45 0000 ------- 
(In reply to comment #15)
> (In reply to comment #10)
> > Kernel 2.6.21-rc7: Gigabyte S3 with 88E8056 works fine for more then a week
> 
> Please post lspci output for this device like others have done.
> 
lspci -vvxnns 04:00.0
04:00.0 Ethernet controller [0200]: Marvell Technology Group Ltd. Unknown
device [11ab:4364] (rev 12)
        Subsystem: Giga-byte Technology Unknown device [1458:e000]
        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: 32 bytes
        Interrupt: pin A routed to IRQ 16
        Region 0: Memory at f8000000 (64-bit, non-prefetchable) [size=16K]
        Region 2: I/O ports at 8000 [size=256]
        [virtual] Expansion ROM at 40000000 [disabled] [size=128K]
        Capabilities: [48] Power Management version 3
                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/0
Enable-
                Address: 0000000000000000  Data: 0000
        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 2048 bytes
                Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 0
                Link: Latency L0s <256ns, L1 unlimited
                Link: ASPM Disabled RCB 128 bytes CommClk- ExtSynch-
                Link: Speed 2.5Gb/s, Width x1
        Capabilities: [100] Advanced Error Reporting
00: ab 11 64 43 07 00 10 00 12 00 00 02 08 00 00 00
10: 04 00 00 f8 00 00 00 00 01 80 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 58 14 00 e0
30: 00 00 00 00 48 00 00 00 00 00 00 00 0b 01 00 00

------- Comment #20 From Matthew Swaringen 2007-05-08 21:57:52 0000 ------- 
(In reply to comment #19)
Same as previous, I also have a Gigabyte S3 that works fine with 8056 on kernel
2.6.21-rc7 (not 2.6.21 regular though due to the disabling in the source).

However, it does have some issues with not doing full speed transfers when it
is in gigabit mode, and is generally slower than it should be.  It still works
just fine for what I need it to, but I'm hoping the driver one day allows full
speeds.

Here's my lspci -vvxnns 04:00.0
04:00.0 0200: 11ab:4364 (rev 12)
        Subsystem: 1458:e000
        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: 32 bytes
        Interrupt: pin A routed to IRQ 16
        Region 0: Memory at f9000000 (64-bit, non-prefetchable) [size=16K]
        Region 2: I/O ports at 9000 [size=256]
        [virtual] Expansion ROM at 80000000 [disabled] [size=128K]
        Capabilities: [48] Power Management version 3
                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: 64bit+ Queue=0/0
Enable-
                Address: 0000000000000000  Data: 0000
        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 L1, Port 0
                Link: Latency L0s <256ns, L1 unlimited
                Link: ASPM Disabled RCB 128 bytes CommClk- ExtSynch-
                Link: Speed 2.5Gb/s, Width x1
        Capabilities: [100] Advanced Error Reporting
00: ab 11 64 43 07 00 10 00 12 00 00 02 08 00 00 00
10: 04 00 00 f9 00 00 00 00 01 90 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 58 14 00 e0
30: 00 00 00 00 48 00 00 00 00 00 00 00 0b 01 00 00

------- Comment #21 From Daniel Drake 2007-05-10 22:36:15 0000 ------- 
Could those people with 88E8056 devices on Gigabyte boards please attach output
of "lspci -vvxxx"? We're interested in the *full* output, for all devices in
the system (rather than just the network device). Thanks!

------- Comment #22 From Vladi 2007-05-11 04:44:20 0000 ------- 
Created an attachment (id=118827) [details]
full lspci -vvxxx on Gigabyte P965-S3

------- Comment #23 From Matthew Swaringen 2007-05-11 11:40:20 0000 ------- 
Created an attachment (id=118848) [details]
Xanas - lspci-vvxx-gigabyte-p965-s3

------- Comment #24 From Daniel Drake 2007-05-11 21:51:29 0000 ------- 
Thanks. Could I now get the same output ("lspci -vvxxx") from a couple of
non-gigabyte boards?

------- Comment #25 From paapaa125@hotmail.com 2007-05-12 20:07:44 0000 ------- 
Created an attachment (id=119038) [details]
"lspci -vvxxx" from Asus P5B Deluxe

This is "lspci -vvxxx" from my Asus P5B Deluxe.

------- Comment #26 From Daniel Drake 2007-05-17 03:22:11 0000 ------- 
Thanks for the info everyone. After all that it's been decided the best way to
proceed is to just drop the restriction for 2.6.22 and hope that this
corruption doesn't affect too many users (Gentoo have no reports of it).
gentoo-sources-2.6.21 will be adjusted accordingly.

------- Comment #27 From Daniel Drake 2007-05-19 05:32:39 0000 ------- 
Fixed in gentoo-sources-2.6.21-r1 (genpatches-2.6.21-2). All 88E8056 enabled.