Date: Mon, 18 Dec 2023 18:39:38 +0000 From: bugzilla-noreply@freebsd.org To: transport@FreeBSD.org Subject: [Bug 275798] panic: sackhint bytes rtx >= 0 Message-ID: <bug-275798-38102-BIR2JJ48sO@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-275798-38102@https.bugs.freebsd.org/bugzilla/> References: <bug-275798-38102@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 --- Comment #9 from Richard Scheffenegger <rscheff@freebsd.org> --- I can see a number of retransmission timeouts (so the theory around EPERM on the ipsec may be valid). There were 3 reordering/loss episodes in that short flow (169 logging event= s),=20 and during the last one, the ACK has a SACK block, where the right edge mov= ed=20 left compared to an ACK received prior to that... Which is peculiar (maybe reordering induced by the packet held up in processing?), but obviously the tcp stack shouldn't loose it's bearings accounting for su= ch events. I'll update this once I have decoded more of the timing and events. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-275798-38102-BIR2JJ48sO>