Problem with TCP/IP stack?
Mohan Srinivasan
mohan_srinivasan at yahoo.com
Tue Jun 7 17:21:22 GMT 2005
Hi,
This change should fix the issue. If you have this change
and still see the issue, please let us know.
Revision 1.22 / (download) - annotate - [select for diffs], Mon Jun 6 19:46:53 2005 UTC (21 hours,
34 minutes ago) by ps
Branch: MAIN
CVS Tags: HEAD
Changes since 1.21: +9 -4 lines
Diff to previous 1.21 (colored)
Fix for a bug in the change that walks the scoreboard backwards from
the tail (in tcp_sack_option()). The bug was caused by incorrect
accounting of the retransmitted bytes in the sackhint.
Reported by: Kris Kennaway.
Submitted by: Noritoshi Demizu.
mohan
--- Tarc <tarc at tarc.po.cs.msu.su> wrote:
> I found in dmesg following lines:
>
> tcp_sack_output: Computed sack_bytes_retransmitted (1400) not the same as cached value (2800)
>
>
> This problems founded after latest recompilling & reinstalling kernel.
>
> My dmesg can be found at http://tarc.po.cs.msu.su/usr/tarc/kernels/current/dmesg
> Kernel config at http://tarc.po.cs.msu.su/usr/tarc/kernels/TarcCurrent
> What shall I do in this case?
> --
> Best regards,
> Arseny Nasokin
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
>
More information about the freebsd-current
mailing list