Re: kern/52111: wmX i82574L inoperative in monoprocessor mode (i386)

[Frank Kardel <kardel%netbsd.org@localhost>]

The following reply was made to PR kern/52111; it has been noted by GNATS.

From: Frank Kardel <kardel%netbsd.org@localhost>
To: gnats-bugs%NetBSD.org@localhost, kern-bug-people%netbsd.org@localhost, 
 gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost, kardel%netbsd.org@localhost
Cc: 
Subject: Re: kern/52111: wmX i82574L inoperative in monoprocessor mode (i386)
Date: Sun, 26 Mar 2017 10:27:08 +0200

 The other system
 machdep.dmi.bios-vendor = American Megatrends Inc.
 machdep.dmi.board-vendor = ASRock
 machdep.dmi.board-product = 990FX Extreme9
 uses ioapic for interrupts:
 
 wm0 at pci6 dev 0 function 0: Intel i82572EI 1000baseT Ethernet (rev. 0x06)
 wm0: interrupting at ioapic1 pin 23
 wm0: PCI-Express bus
 wm0: 2048 words (16 address bits) SPI EEPROM, version 5.11.8, Image 
 Unique ID 0000ffff
 wm0: Ethernet address 00:1b:21:aa:9b:7c
 igphy0 at wm0 phy 1: Intel IGP01E1000 Gigabit PHY, rev. 0
 igphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
 1000baseT-FDX, auto
 
 wm1 at pci13 dev 0 function 0: Intel i82583V (rev. 0x00)
 wm1: interrupting at ioapic0 pin 18
 wm1: PCI-Express bus
 wm1: 2048 words FLASH, version 1.10.0, Image Unique ID 0000ffff
 wm1: Ethernet address bc:5f:f4:98:32:84
 makphy0 at wm1 phy 1: Marvell 88E1149 Gigabit PHY, rev. 1
 makphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
 1000baseT-FDX, auto
 
 So we have differences in interrupt handling and chips and one setup is 
 sensible to mono processor mode.
 
 Best regards,
    Frank
 
 On 03/26/17 09:55, Martin Husemann wrote:
 > The following reply was made to PR kern/52111; it has been noted by GNATS.
 >
 > From: Martin Husemann <martin%duskware.de@localhost>
 > To: gnats-bugs%NetBSD.org@localhost
 > Cc:
 > Subject: Re: kern/52111: wmX i82574L inoperative in monoprocessor mode (i386)
 > Date: Sun, 26 Mar 2017 09:52:37 +0200
 >
 >   On Sat, Mar 25, 2017 at 10:15:00PM +0000, kardel%netbsd.org@localhost wrote:
 >   > wm0: for LINK interrupting at msix0 vec 2
 >   
 >   On the other systems that do not show this issue, does the wm use msi?
 >   
 >   Martin
 >