linux-kernel - Re: sky2 regression in 2.6.21: Asus P5B-E Plus ethernet adapter no more supported

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <46327503.9040902@gentoo.org>
Date:	Fri, 27 Apr 2007 18:11:15 -0400
From:	Daniel Drake <dsd@...too.org>
To:	Stephen Hemminger <shemminger@...ux-foundation.org>
CC:	linux-kernel@...r.kernel.org, curio@...e.fr
Subject: Re: sky2 regression in 2.6.21: Asus P5B-E Plus ethernet adapter no
 more supported

Hi Stephen,

Stephen Hemminger wrote:
> But the same hardware dies horribly on Gigabyte GA-965P motherboards.
> Could you send me full lspci -vvx output. I'll re-enable it for Asus and add a block
> for the Gigabyte boards. (sigh)

This was also reported by another user at 
https://bugs.gentoo.org/show_bug.cgi?id=176219

The following hardware on an Asus P5B Deluxe board worked fine with 2.6.20:

sky2 v1.10 addr 0xfeafc000 irq 17 Yukon-EC Ultra (0xb4) rev 2

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

I guess it may come as a side effect of your upcoming patch, but it 
would be nice if sky2 could printk() some basic info when it detects one 
of the controllers that it is going to ignore. Right now it is kind of 
mysterious why eth0 has disappeared in 2.6.21 for some users.

Thanks,
Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/