Re: Possible regression in wm(4)?

[Kengo NAKAHARA <k-nakahara%iij.ad.jp@localhost>]

Hi,

On 2017/11/11 7:23, Bert Kiers wrote:
> On Fri, Nov 10, 2017 at 08:23:21PM +0100, Jimmy Johansson wrote:
> 
> Hi,
> 
>> Has anybody else had issues with these interfaces in NetBSD 8 or NetBSD
>> current?
> 
> yes, see kern/52717: no wm(4) networking in 8.0_BETA 
> also with i82576

Hmm, it seems problems related interrupts on dual socket system.
Could you try the following patch(A)? If it does not work, could
you try patch(B)?

Patch (A) uses only two MSI-X vectors, so the all interrupts may
be affinity to socket0. That can avoid the problems related dual
socket system.
Patch (B) uses not MSI-X but MSI. That means it almost the same
behavior as NetBSD-7 or older.

========== (A) ==========
--- a/sys/dev/pci/if_wm.c
+++ b/sys/dev/pci/if_wm.c
@@ -4883,8 +4883,8 @@ wm_adjust_qnum(struct wm_softc *sc, int nvectors)
 		hw_nrxqueues = 4;
 		break;
 	case WM_T_82576:
-		hw_ntxqueues = 16;
-		hw_nrxqueues = 16;
+		hw_ntxqueues = 1;
+		hw_nrxqueues = 1;
 		break;
 	case WM_T_82580:
 	case WM_T_I350:
========== (A) ==========

========== (B) ==========
--- a/sys/dev/pci/if_wm.c
+++ b/sys/dev/pci/if_wm.c
@@ -177,7 +177,7 @@ int	wm_debug = WM_DEBUG_TX | WM_DEBUG_RX | WM_DEBUG_LINK | WM_DEBUG_GMII
 #define	WM_DISABLE_MSI 0
 #endif
 #ifndef WM_DISABLE_MSIX
-#define	WM_DISABLE_MSIX 0
+#define	WM_DISABLE_MSIX 1
 #endif
 
 int wm_disable_msi = WM_DISABLE_MSI;
========== (B) ==========


Thanks,

-- 
//////////////////////////////////////////////////////////////////////
Internet Initiative Japan Inc.

Device Engineering Section,
IoT Platform Development Department,
Network Division,
Technology Unit

Kengo NAKAHARA <k-nakahara%iij.ad.jp@localhost>