Re: wm devices don't work under current amd64

[Masanobu SAITOH <msaitoh%execsw.org@localhost>]

Hello, Jarle.

On 2016/11/27 0:45, Jarle Greipsland wrote:
> Masanobu SAITOH <msaitoh%execsw.org@localhost> writes:
> > Hi.
> >
> > On 2016/03/07 21:12, Tobias Nygren wrote:
> > > On Mon, 7 Mar 2016 20:57:02 +0900
> > > Masanobu SAITOH <msaitoh%execsw.org@localhost> wrote:
> > >
> > > > One of the possibility is that the multicast filter table and broadcast
> > > > bit in a register aren't set correctly on ICH9.
> > >
> > > I'm not sure if this is relevant to the discussion, but I have a wm(4)
> > > device (8086:1502) on -current that does not work after boot. It comes
> > > to life only after running "tcpdump -n -i wm0" once. I am using vlan(4),
> > > but haven't checked if that makes any difference. I usually run the
> > > tcpdump command then forget about it until the next reboot.
> >
> >  It must be a bug! Could you tell me how you set up network interface include
> > vlan? (e.g. part of /etc/rc.conf, /etc/ifconfig.xxx, and the output of "ifconfig -a)
>
> Was this problem ever fixed?

 Perhaps no. I've added a lot of changes into if_wm.c, but I've not
touched vlan related stuff.

 I've struggled to make I219 work for month but the work have not
finished yet.

 I also resumed working ixg(4) sync with FreeBSD last week and it'll
take a few or more weeks to finish. Until finishing the work, I won't
come back to any wm bugfixes. So if someone can spend time to fix vlan
and I219 problem of wm(4), please do!

 Regards.


>  I am experiencing very similar
> problems with -current as of yesterday.  My system is a
> SuperMicro X7SPA-HF used as a router with a non-vlan interface
> towards my ISP (wm1), and a vlan'ed interface for a number of
> internal networks (wm0).
>
> An old kernel 7.99.21 from October last year works fine:
> [ ... ]
> ppb0 at pci0 dev 28 function 0: vendor 8086 product 2940 (rev. 0x02)
> ppb0: PCI Express capability version 1 <Root Port of PCI-E Root Complex> x4 @ 2.
> 5GT/s
> pci1 at ppb0 bus 1
> pci1: i/o space, memory space enabled, rd/line, wr/inv ok
> ppb1 at pci0 dev 28 function 4: vendor 8086 product 2948 (rev. 0x02)
> ppb1: PCI Express capability version 1 <Root Port of PCI-E Root Complex> x1 @ 2.
> 5GT/s
> pci2 at ppb1 bus 2
> pci2: i/o space, memory space enabled, rd/line, wr/inv ok
> wm0 at pci2 dev 0 function 0: Intel i82574L (rev. 0x00)
> wm0: for TX interrupting at msix0 vec 0 affinity to 0
> wm0: for RX interrupting at msix0 vec 1 affinity to 1
> wm0: for RX interrupting at msix0 vec 2 affinity to 2
> wm0: for LINK interrupting at msix0 vec 3
> wm0: PCI-Express bus
> wm0: 2048 words (8 address bits) SPI EEPROM, version 1.9.0, Image Unique ID 0000ffff
> wm0: Ethernet address 00:xx:xx:xx:xx:xx
> makphy0 at wm0 phy 1: Marvell 88E1149 Gigabit PHY, rev. 1
> makphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
> ppb2 at pci0 dev 28 function 5: vendor 8086 product 294a (rev. 0x02)
> ppb2: PCI Express capability version 1 <Root Port of PCI-E Root Complex> x1 @ 2.5GT/s
> pci3 at ppb2 bus 3
> pci3: i/o space, memory space enabled, rd/line, wr/inv ok
> wm1 at pci3 dev 0 function 0: Intel i82574L (rev. 0x00)
> wm1: for TX interrupting at msix1 vec 0 affinity to 0
> wm1: for RX interrupting at msix1 vec 1 affinity to 1
> wm1: for RX interrupting at msix1 vec 2 affinity to 2
> wm1: for LINK interrupting at msix1 vec 3
> wm1: PCI-Express bus
> wm1: 512 words (8 address bits) SPI EEPROM, version 1.9.0, Image Unique ID 0000ffff
> wm1: Ethernet address 00:yy:yy:yy:yy:yy
> makphy1 at wm1 phy 1: Marvell 88E1149 Gigabit PHY, rev. 1
> makphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
>
> With a current kernel from yesterday (7.99.42) however, the vlan
> interfaces on wm0 do not work.  The dmesg also looks slightly different
> (the interrupt routing seems different):
>
> ppb0 at pci0 dev 28 function 0: vendor 8086 product 2940 (rev. 0x02)
> ppb0: PCI Express capability version 1 <Root Port of PCI-E Root Complex> x4 @ 2.
> 5GT/s
> pci1 at ppb0 bus 1
> pci1: i/o space, memory space enabled, rd/line, wr/inv ok
> ppb1 at pci0 dev 28 function 4: vendor 8086 product 2948 (rev. 0x02)
> ppb1: PCI Express capability version 1 <Root Port of PCI-E Root Complex> x1 @ 2.
> 5GT/s
> pci2 at ppb1 bus 2
> pci2: i/o space, memory space enabled, rd/line, wr/inv ok
> wm0 at pci2 dev 0 function 0: Intel i82574L (rev. 0x00)
> wm0: for TX and RX interrupting at msix0 vec 0 affinity to 1
> wm0: for TX and RX interrupting at msix0 vec 1 affinity to 2
> wm0: for LINK interrupting at msix0 vec 2
> wm0: PCI-Express bus
> wm0: 2048 words (8 address bits) SPI EEPROM, version 1.9.0, Image Unique ID 0000ffff
> wm0: Ethernet address 00:xx:xx:xx:xx:xx
> makphy0 at wm0 phy 1: Marvell 88E1149 Gigabit PHY, rev. 1
> makphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
> ppb2 at pci0 dev 28 function 5: vendor 8086 product 294a (rev. 0x02)
> ppb2: PCI Express capability version 1 <Root Port of PCI-E Root Complex> x1 @ 2.5GT/s
> pci3 at ppb2 bus 3
> pci3: i/o space, memory space enabled, rd/line, wr/inv ok
> wm1 at pci3 dev 0 function 0: Intel i82574L (rev. 0x00)
> wm1: for TX and RX interrupting at msix1 vec 0 affinity to 1
> wm1: for TX and RX interrupting at msix1 vec 1 affinity to 2
> wm1: for LINK interrupting at msix1 vec 2
> wm1: PCI-Express bus
> wm1: 512 words (8 address bits) SPI EEPROM, version 1.9.0, Image Unique ID 0000ffff
> wm1: Ethernet address 00:yy:yy:yy:yy:yy
> makphy1 at wm1 phy 1: Marvell 88E1149 Gigabit PHY, rev. 1
> makphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
>
> With this kernel, I have to do a tcpdump of one or two packets on
> wm0 until it starts to work, as suggest by tnn@ in his message
> from March.
>
> Any idea what might be the problem?
> 					-jarle


--
-----------------------------------------------
                SAITOH Masanobu (msaitoh%execsw.org@localhost
                                 msaitoh%netbsd.org@localhost)