Re: kern/47542: PHY access method for 82580(I340) and I350 (wm(4)) is incorrect.

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Fri, Feb 08, 2013 at 03:55:01AM +0000, msaitoh%execsw.org@localhost wrote:
>         PHY access method for 82580(I340) and I350 (wm(4)) is incorrect.
>        For those devices, read/write fuctions for i80003 are used now.
>        We MUST use 82580 specific read/write function.
> 
>         Currently, wm on I350 is not stable. It sometimes stucks.
>        For TX side, the MAC layer send packets to MII layer and the
>        TX complete interrupts occur correctly, but PHY don't send
>        packets. For RX side, PHY don't catch packets.

Hum,
I have a system with:
wm0 at pci7 dev 0 function 0: I350 Gigabit Network Connection (rev. 0x01)
wm0: interrupting at ioapic0 pin 16
wm0: PCI-Express bus
wm0: 65536 word (16 address bits) SPI EEPROM
wm0: Ethernet address 00:25:90:2d:e2:34
ukphy0 at wm0 phy 1: OUI 0x00aa00, model 0x003b, rev. 1
wm1 at pci7 dev 0 function 1: I350 Gigabit Network Connection (rev. 0x01)
wm1: interrupting at ioapic0 pin 17
wm1: PCI-Express bus
wm1: 256 word (8 address bits) SPI EEPROM
wm1: Ethernet address 00:25:90:2d:e2:35
ukphy1 at wm1 phy 1: OUI 0x00aa00, model 0x003b, rev. 1
wm2 at pci7 dev 0 function 2: I350 Gigabit Network Connection (rev. 0x01)
wm2: interrupting at ioapic0 pin 18
wm2: PCI-Express bus
wm2: 256 word (8 address bits) SPI EEPROM
wm2: Ethernet address 00:25:90:2d:e2:36
ukphy2 at wm2 phy 1: OUI 0x00aa00, model 0x003b, rev. 1
wm3 at pci7 dev 0 function 3: I350 Gigabit Network Connection (rev. 0x01)
wm3: interrupting at ioapic0 pin 19
wm3: PCI-Express bus
wm3: 256 word (8 address bits) SPI EEPROM
wm3: Ethernet address 00:25:90:2d:e2:37

All 4 interfaces used in an agr(4). This is a file server, and I didn't
notice any networking issue ...

-- 
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
     NetBSD: 26 ans d'experience feront toujours la difference
--