Re: hitting Assertion !callout_active(&tp->t_callout) failed at /usr/src/sys/netinet/tcp_subr.c:2386 after 62d47d7
- Reply: Cheng Cui : "Re: hitting Assertion !callout_active(&tp->t_callout) failed at /usr/src/sys/netinet/tcp_subr.c:2386 after 62d47d7"
- In reply to: tuexen_a_freebsd.org: "Re: hitting Assertion !callout_active(&tp->t_callout) failed at /usr/src/sys/netinet/tcp_subr.c:2386 after 62d47d7"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 12 Feb 2024 11:41:18 UTC
On Mon, 12 Feb 2024, at 10:26, tuexen@freebsd.org wrote: >> On Feb 12, 2024, at 09:50, Dave Cottlehuber <dch@freebsd.org> wrote: >> >> On Mon, 12 Feb 2024, at 08:31, Dave Cottlehuber wrote: >>> I'm repeatedly hitting this assert soon after boot on my ryzen desktop >>> I've a coredump. >>> >>> Panic String: Assertion !callout_active(&tp->t_callout) failed at >>> /usr/src/sys/netinet/tcp_subr.c:2386 This one "just happens" while I'm sitting at the PC hacking in the terminal, I don't get much incoming data here so it's presumably clean local traffic. >>> I'll apply your latest patch in >>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276761#c16 and report >>> back.. >> >> Reporting back, insta-panic on boot at: >> >> Panic String: Assertion !tcp_timer_active(tp, TT_REXMT) failed at /usr/src/sys/netinet/tcp_subr.c:2387 >> >> Does that help any? > Sure! Could you provide any hints how to reproduce it? this one happens during boot very early, I have a coredump handy if that helps. I will try with all sysctls disabled, and without zerotier (overlay network) too, see if that makes a difference. A+ Dave ——— O for a muse of fire, that would ascend the brightest heaven of invention!