Date: Mon, 13 Jan 2025 07:33:14 +0100 (CET) From: Ronald Klop <ronald-lists@klop.ws> To: Kyle Evans <kevans@FreeBSD.org> Cc: freebsd-net@freebsd.org Subject: Re: panic: tcp_do_segment: sent too much Message-ID: <284762638.373.1736749994743@localhost> In-Reply-To: <a93eac02-df4c-4c25-90a1-b2370cf4cc54@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] Seen this before. Does one of these issues match your case? https://bugs.freebsd.org/bugzilla/buglist.cgi?quicksearch=Tcp_do_segment&list_id=789107 Regards, Ronald Van: Kyle Evans <kevans@FreeBSD.org> Datum: 13 januari 2025 02:45 Aan: freebsd-net@freebsd.org Onderwerp: panic: tcp_do_segment: sent too much > > > Hi, > > I seem to have hit this panic during normal laptop usage with a -CURRENT running at 2832af7b4ea256b18ef4dbf2ff97a50765f0609a: > > panic: tcp_do_segment: sent too much > cpuid = 5 > time = 1736731772 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe015b74b9b0 > vpanic() at vpanic+0x136/frame 0xfffffe015b74bae0 > panic() at panic+0x43/frame 0xfffffe015b74bb40 > tcp_do_segment() at tcp_do_segment+0x2998/frame 0xfffffe015b74bc20 > tcp_input_with_port() at tcp_input_with_port+0x10f8/frame 0xfffffe015b74bd70 > tcp_input() at tcp_input+0xb/frame 0xfffffe015b74bd80 > ip_input() at ip_input+0x28f/frame 0xfffffe015b74bde0 > swi_net() at swi_net+0x19b/frame 0xfffffe015b74be60 > ithread_loop() at ithread_loop+0x266/frame 0xfffffe015b74bef0 > fork_exit() at fork_exit+0x82/frame 0xfffffe015b74bf30 > fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe015b74bf30 > > Doing a little bit of inspection: > > (kgdb) print tp->t_dupacks > $1 = 1 > (kgdb) print tp->snd_limited > $6 = 0 '' > (kgdb) p/x tp->t_flags > $4 = 0x10000264 > (kgdb) print maxseg > $1 = 1428 > > `sent` appears to be optimized out. As far as I know, I don't hit this one often, but I'm wondering if there's anything else useful I could extract here / if anyone has a theory about what happened. > > Thanks, > > Kyle Evans > > > > > [-- Attachment #2 --] <html><head></head><body>Seen this before.<div> Does one of these issues match your case?<div><br></div><div><a href="https://bugs.freebsd.org/bugzilla/buglist.cgi?quicksearch=Tcp_do_segment&list_id=789107">https://bugs.freebsd.org/bugzilla/buglist.cgi?quicksearch=Tcp_do_segment&list_id=789107</a></div><div><br></div><div>Regards,</div><div>Ronald </div><div><br></div><div><br><p><small><strong>Van:</strong>; Kyle Evans <kevans@FreeBSD.org><br><strong>Datum:</strong> 13 januari 2025 02:45<br><strong>Aan:</strong> freebsd-net@freebsd.org<br><strong>Onderwerp:</strong> panic: tcp_do_segment: sent too much<br></small></p><blockquote style="margin-left: 5px; border-left: 3px solid #ccc; margin-right: 0px; padding-left: 5px;"><div class="MessageRFC822Viewer do_not_remove" id="P"><!-- P --> <!-- processMimeMessage --><div class="TextPlainViewer do_not_remove" id="P.P"><!-- P.P -->Hi,<br> <br> I seem to have hit this panic during normal laptop usage with a -CURRENT running at 2832af7b4ea256b18ef4dbf2ff97a50765f0609a:<br> <br> panic: tcp_do_segment: sent too much<br> cpuid = 5<br> time = 1736731772<br> KDB: stack backtrace:<br> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe015b74b9b0<br> vpanic() at vpanic+0x136/frame 0xfffffe015b74bae0<br> panic() at panic+0x43/frame 0xfffffe015b74bb40<br> tcp_do_segment() at tcp_do_segment+0x2998/frame 0xfffffe015b74bc20<br> tcp_input_with_port() at tcp_input_with_port+0x10f8/frame 0xfffffe015b74bd70<br> tcp_input() at tcp_input+0xb/frame 0xfffffe015b74bd80<br> ip_input() at ip_input+0x28f/frame 0xfffffe015b74bde0<br> swi_net() at swi_net+0x19b/frame 0xfffffe015b74be60<br> ithread_loop() at ithread_loop+0x266/frame 0xfffffe015b74bef0<br> fork_exit() at fork_exit+0x82/frame 0xfffffe015b74bf30<br> fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe015b74bf30<br> <br> Doing a little bit of inspection:<br> <br> (kgdb) print tp->t_dupacks<br> $1 = 1<br> (kgdb) print tp->snd_limited<br> $6 = 0 ''<br> (kgdb) p/x tp->t_flags<br> $4 = 0x10000264<br> (kgdb) print maxseg<br> $1 = 1428<br> <br> `sent` appears to be optimized out. As far as I know, I don't hit this one often, but I'm wondering if there's anything else useful I could extract here / if anyone has a theory about what happened.<br> <br> Thanks,<br> <br> Kyle Evans<br> <br> </div><!-- TextPlainViewer --> <hr> </div><!-- MessageRFC822Viewer --> </blockquote><br><br><br></div></div></body></html>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?284762638.373.1736749994743>