Date: Sun, 17 Dec 2023 15:29:38 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 275798] panic: sackhint bytes rtx >= 0 Message-ID: <bug-275798-227-EOZBjVbWzr@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-275798-227@https.bugs.freebsd.org/bugzilla/> References: <bug-275798-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D275798 Richard Scheffenegger <rscheff@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bugs@FreeBSD.org |rscheff@freebsd.org --- Comment #4 from Richard Scheffenegger <rscheff@freebsd.org> --- Can you please enable bblogging: Enable BBR logging for all TCP sessions: # sysctl net.inet.tcp.bb.log_auto_mode=3D4 # sysctl net.inet.tcp.bb.log_auto_all=3D1 # sysctl net.inet.tcp.bb.log_auto_ratio=3D1 when this panic is easily reproducible?=20 Alternatively, a tcpdump of the tcp session(s) within the ipsec tunnel (not= a interface packet capture, but after the decoding).=20 The core should then contain full chains of the relevant information we cou= ld extract offline... The full sequence of tcp packets from the onset of packet loss and the ACKs (with SACKs) from the remote side should yield some clue why this is happen= ing. This appears to be some kind of SACK (selective acknowledgment) accounting error - but no recent change in this area... --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-275798-227-EOZBjVbWzr>