On Wed, Jun 28, 2023 at 11:25:56AM +0200, Mark Kettenis wrote: > > From: Alexander Bluhm <alexander.bl...@gmx.net> > > load: 3.00 cmd: ifconfig 52949 [sbar] 0.01u 0.05s 0% 78k > > ifconfig holds the netlock, I guess this prevents progress. > > What does a WITNESS kernel report?
This is hard to say as I cannot reproduce. I grepped through my console logs and found these issues. Nov 13 2022, starting network ix, ot15 amd64 Nov 18 2022, starting network ix, ot15 amd64 Nov 19 2022, starting network ix, ot15 amd64 Nov 19 2022, starting network ix, ot15 amd64 Nov 21 2022, starting network ix, ot15 amd64 Nov 21 2022, starting network ix, ot14 amd64 Feb 2 2023, ifconfig mcx0 down, ot10 arm64 Jun 25 2023, starting network ix ot31 amd64 The hangs in November were fixed by a few backouts. In February it happend once with mcx(4) on arm64. root@ot10:.../~# ifconfig mcx0 down load: 1.08 cmd: ifconfig 81584 [sbar] 0.00u 0.07s 0% 67k^M ddb{0}> ps PID TID PPID UID S FLAGS WAIT COMMAND 81584 79693 8043 0 3 0x3 sbar ifconfig 15833 336275 93940 0 3 0x100083 ttyin ksh 93940 402344 85411 0 3 0x9a kqread sshd 85411 256105 1 0 3 0x88 kqread sshd 8043 494868 1 0 3 0x10008b sigsusp ksh 81425 284730 1 0 3 0x100098 kqread cron 98122 214551 1 99 3 0x1100090 kqread sndiod 12478 363247 1 110 3 0x100090 kqread sndiod 68723 281017 58293 95 3 0x1100092 kqread smtpd 66232 206325 58293 103 3 0x1100092 kqread smtpd 11325 62850 58293 95 3 0x1100092 kqread smtpd 20547 416814 58293 95 3 0x100092 kqread smtpd 56040 129458 58293 95 3 0x1100092 kqread smtpd 17357 62413 58293 95 3 0x1100092 kqread smtpd 58293 210166 1 0 3 0x100080 kqread smtpd 91251 150204 61674 91 3 0x92 kqread snmpd_metrics 61674 232064 1 0 3 0x100080 kqread snmpd 57336 163242 1 91 3 0x1100092 kqread snmpd 85262 6957 0 0 3 0x14200 acct acct 77255 305020 1 0 3 0x100080 kqread ntpd 33023 22895 66431 83 3 0x100092 kqread ntpd 66431 320304 1 83 3 0x1100012 netlock ntpd 23397 480861 4591 74 3 0x1100092 bpf pflogd 4591 165046 1 0 3 0x80 netio pflogd 33526 16136 38718 73 3 0x1100090 kqread syslogd 38718 363093 1 0 3 0x100082 netio syslogd 27296 406775 1 0 3 0x100080 kqread resolvd 48075 26460 29615 77 3 0x100092 kqread dhcpleased 61089 41438 29615 77 3 0x100092 kqread dhcpleased 29615 55499 1 0 3 0x80 kqread dhcpleased 87685 213464 18916 115 3 0x100092 kqread slaacd 20348 141000 18916 115 3 0x100092 kqread slaacd 18916 288162 1 0 3 0x100080 kqread slaacd 52479 405921 0 0 3 0x14200 bored smr 98977 128674 0 0 3 0x14200 pgzero zerothread 47683 136576 0 0 3 0x14200 aiodoned aiodoned 31843 499677 0 0 3 0x14200 syncer update 54183 192766 0 0 3 0x14200 cleaner cleaner 59290 295494 0 0 3 0x14200 reaper reaper 57470 163245 0 0 3 0x14200 pgdaemon pagedaemon 62972 158489 0 0 3 0x14200 mmctsk sdmmc1 38777 388048 0 0 3 0x14200 usbtsk usbtask 50340 433235 0 0 3 0x14200 usbatsk usbatsk 73074 317607 0 0 3 0x14200 bored sensors 34503 452302 0 0 3 0x14200 mmctsk sdmmc0 31956 271329 0 0 3 0x14200 bored suspend 80033 244737 0 0 7 0x40014200 idle3 55093 157860 0 0 1 0x14200 idle2 15894 247866 0 0 7 0x40014200 idle1 96587 185531 0 0 3 0x14200 bored softnet 828 362691 0 0 3 0x14200 bored softnet 51534 398133 0 0 3 0x14200 bored softnet 73800 41723 0 0 3 0x14200 bored softnet 46236 496068 0 0 2 0x40014200 systqmp 31144 27768 0 0 3 0x14200 netlock systq 78836 32990 0 0 3 0x40014200 netlock softclock *93904 268669 0 0 7 0x40014200 idle0 26354 129736 0 0 3 0x14200 kmalloc kmthread 1 147810 0 0 3 0x82 wait init 0 0 -1 0 3 0x10200 scheduler swapper I did not find valuable traces back then, maybe this is the reason why I did not report it. And now, 4 months later, it happend on a amd64 machine. There is little chance that it happens soon. Witness kernel booted fine. bluhm