Re: kern/59664: kernel keeps spewing can't handle af18

["Martin Husemann via gnats" <gnats-admin%NetBSD.org@localhost>]

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

From: Martin Husemann <martin%duskware.de@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: kern/59664: kernel keeps spewing can't handle af18
Date: Mon, 22 Sep 2025 10:06:11 +0200

 On Sun, Sep 21, 2025 at 05:15:00PM +0000, christos%zoulas.com@localhost wrote:
 > 	Since early August I think the kernel has been spewing:
 > 
 > [  6997.112809] ether_output: wm1: can't handle af18 (link: link#2)
 > [  6997.159684] ether_output: wm1: can't handle af18 (link: link#2)
 > [  6998.147196] ether_output: wm1: can't handle af18 (link: link#2)
 > [  6998.391980] ether_output: wm1: can't handle af18 (link: link#2)
 > [  6998.981565] ether_output: wm1: can't handle af18 (link: link#2)
 
 Could you add a Debugger() call and then get a backtrace and continue?
 
 We can probably clone a minor variation of the AF_UNSPEC case for AF_LINK,
 but it would be interesting to see where ethere_output is called from with
 this adress family.
 
 Martin
 
 Index: if_ethersubr.c
 ===================================================================
 RCS file: /cvsroot/src/sys/net/if_ethersubr.c,v
 retrieving revision 1.330
 diff -u -p -r1.330 if_ethersubr.c
 --- if_ethersubr.c	23 Apr 2025 12:17:05 -0000	1.330
 +++ if_ethersubr.c	22 Sep 2025 08:05:40 -0000
 @@ -377,6 +377,7 @@ ether_output(struct ifnet * const ifp0, 
  	default:
  		printf("%s: can't handle af%d\n", ifp->if_xname,
  		    dst->sa_family);
 +		Debugger();
  		senderr(EAFNOSUPPORT);
  	}