This ticket is for kernel-side altq(4), not for userland
altqd(8). If your kernel is also updated, I have no idea :(
If you can reproduce the problem within, say, few hours,
LOCKDEBUG should be useful. Temporarily performance
regression is much better than untrackable crashes, IMO...
Thanks,
rin
On 2024/10/04 18:14, BERTRAND Joël wrote:
Rin Okuyama a écrit :
Hi,
altq(4) for netbsd-10 was updated just recently.
What happens if you apply these fixes (or just update to
today's netbsd-10)?
http://releng.netbsd.org/cgi-bin/req-10.cgi?show=917
I have upgraded my tree this morning and I have seen that altqd was
patched. Thus, this server runs altqd with this patch.
Best regards,
JB
