rge(4) completely hangs

[Thomas Klausner <wiz%NetBSD.org@localhost>]

Hi!

After the latest fixes, rge(4) is better, but it's completely hung up
the network interface twice so far - no network traffic possible on it
- both times so hard, that the BIOS had some kind of issue on the next
boot and needed 15 minutes to sort itself out (before even showing
anything on the screen).

I'm running a kernel from Oct 22.

In /var/log/messages I see:
Nov  1 18:59:43 exadelic dhcpcd[2191]: rge0: xxxx::1 is unreachable
Nov  1 18:59:43 exadelic dhcpcd[2191]: rge0: soliciting an IPv6 router
Nov  1 18:59:45 exadelic dhcpcd[2191]: rge0: Router Advertisement from xxxx::1  1 18:59:46 exadelic dhcpcd[2191]: rge0: xxxx::1 is unreachable
Nov  1 18:59:46 exadelic dhcpcd[2191]: rge0: soliciting an IPv6 router
Nov  1 18:59:58 exadelic dhcpcd[2191]: rge0: no IPv6 Routers available
Nov  1 19:01:11 exadelic dhcpcd[2191]: rge0: xxxx::1 is reachable again
Nov  1 19:01:19 exadelic dhcpcd[2191]: rge0: xxxx::1 is unreachable
Nov  1 19:01:19 exadelic dhcpcd[2191]: rge0: soliciting an IPv6 router
Nov  1 19:01:31 exadelic dhcpcd[2191]: rge0: no IPv6 Routers available
Nov  1 19:01:57 exadelic dhcpcd[2191]: rge0: xxxx::1 is reachable again
Nov  1 19:02:05 exadelic dhcpcd[2191]: rge0: xxxx::1 is unreachable
Nov  1 19:02:05 exadelic dhcpcd[2191]: rge0: soliciting an IPv6 router
Nov  1 19:02:17 exadelic dhcpcd[2191]: rge0: no IPv6 Routers available
Nov  1 19:04:27 exadelic dhcpcd[2191]: rge0: xxxx::1 is reachable again
Nov  1 19:04:35 exadelic dhcpcd[2191]: rge0: xxxx::1 is unreachable
Nov  1 19:04:35 exadelic dhcpcd[2191]: rge0: soliciting an IPv6 router
Nov  1 19:04:47 exadelic dhcpcd[2191]: rge0: no IPv6 Routers available
Nov  1 19:06:12 exadelic dhcpcd[2191]: rge0: xxxx::1 is reachable again
Nov  1 19:06:20 exadelic dhcpcd[2191]: rge0: xxxx::1 is unreachable
Nov  1 19:06:21 exadelic dhcpcd[2191]: rge0: soliciting an IPv6 router
Nov  1 19:06:33 exadelic dhcpcd[2191]: rge0: no IPv6 Routers available
Nov  1 19:09:27 exadelic /netbsd: [ 91537.5847758] nfs server 192.168.178.19:/path: not responding
Nov  1 19:15:16 exadelic dhcpcd[2191]: rge0: xxxx::1 is reachable again
Nov  1 19:15:24 exadelic dhcpcd[2191]: rge0: xxxx::1 is unreachable
Nov  1 19:15:24 exadelic dhcpcd[2191]: rge0: soliciting an IPv6 router
Nov  1 19:15:36 exadelic dhcpcd[2191]: rge0: no IPv6 Routers available
Nov  1 19:16:51 exadelic dhcpcd[2191]: rge0: xxxx::1 is reachable again
Nov  1 19:16:52 exadelic dhcpcd[2191]: ps_root_recvmsg: No buffer space available
Nov  1 19:16:52 exadelic dhcpcd[2191]: ps_root_recvmsg: No buffer space available
Nov  1 19:16:59 exadelic dhcpcd[2191]: rge0: xxxx::1 is unreachable
Nov  1 19:16:59 exadelic dhcpcd[2191]: rge0: soliciting an IPv6 router
Nov  1 19:16:59 exadelic dhcpcd[2191]: ps_root_recvmsg: No buffer space available
Nov  1 19:17:11 exadelic syslogd[2290]: last message repeated 3 times
Nov  1 19:17:11 exadelic dhcpcd[2191]: rge0: no IPv6 Routers available
Nov  1 19:17:44 exadelic dhcpcd[2191]: ps_root_recvmsg: No buffer space available

Just in case it matters, I'm not running with default sysctl's, I have

kern.sbmax: 262144 -> 16777216
net.inet.tcp.recvbuf_max: 262144 -> 16777216
net.inet.tcp.sendbuf_max: 262144 -> 16777216
net.inet.tcp.recvspace: 32768 -> 262144
net.inet.tcp.sendspace: 32768 -> 262144

because of

https://mail-index.netbsd.org/current-users/2017/09/21/msg032369.html

I've now switched to an ure(4) device.

Has anyone else seen this?
 Thomas