NetBSD-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: kern/52111: wmX i82574L inoperative in monoprocessor mode (i386)
The following reply was made to PR kern/52111; it has been noted by GNATS.
From: Kengo NAKAHARA <k-nakahara%iij.ad.jp@localhost>
To: gnats-bugs%NetBSD.org@localhost, kern-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
netbsd-bugs%netbsd.org@localhost
Cc:
Subject: Re: kern/52111: wmX i82574L inoperative in monoprocessor mode (i386)
Date: Mon, 27 Mar 2017 11:27:17 +0900
Hi,
On 2017/03/26 7:15, kardel%netbsd.org@localhost wrote:
> When booting a Soekris 6501 in mono processor mode (boot -1) wm interfaces are inoperative
> as arp resolution does not complete at all.
> On an amd64 system with other wm interfaces (i82572EI, i82583V) mono processor mode does not impair
> interface operation.
>
> Soekris interfaces:
> wm0 at pci5 dev 0 function 0: Intel i82574L (rev. 0x00)
> wm0: for TX and RX interrupting at msix0 vec 0 affinity to 0
> wm0: for TX and RX interrupting at msix0 vec 1 affinity to 1
> wm0: for LINK interrupting at msix0 vec 2
> wm0: PCI-Express bus
> wm0: 2048 words (8 address bits) SPI EEPROM, version 2.1.2, Image Unique ID 0000ffff
> wm0: Ethernet address 00:00:aa:bb:cc:ec
Hmm...., It is strange to me that wm(4) use two TX and RX interrupts on
uniprocessor system. The TX and RX interrupt is limited by ncpu.
At my reproduction environment NetBSD/i386(-current updated in today)
on VMware ESXi with e1000e(82574), the wm(4) uses only one TX and RX
interrupt.
Could you show full dmesg?
Thanks,
--
//////////////////////////////////////////////////////////////////////
Internet Initiative Japan Inc.
Device Engineering Section,
IoT Platform Development Department,
Network Division,
Technology Unit
Kengo NAKAHARA <k-nakahara%iij.ad.jp@localhost>
Home |
Main Index |
Thread Index |
Old Index