sbflush_locked panic and tcp_sack
andre at freebsd.org
Mon Sep 19 06:10:00 PDT 2005
Maxim Konovalov wrote:
> On Mon, 19 Sep 2005, 14:23+0200, Andre Oppermann wrote:
>>Maxim Konovalov wrote:
>>>I got a panic at the end of sbflush_locked() on recent -current when
>>>open a large photo gallery with firefox.
>>>if (sb->sb_cc || sb->sb_mb || sb->sb_mbcnt)
>>> panic("sbflush_locked: cc %u || mb %p || mbcnt %u",
>>> (void *)sb->sb_mb, sb->sb_mbcnt);
>>>It seems I can reproduce this panic easily. Moreover, turning
>>>tcp_sack off eliminates this panic. Does anybody see that?
>>This rings a bell. Sounds like a problem with delayed header drop in TCP
>>segments. In tcp_input() have the variable "tlen" examined.
> Well, there is no tcp_input() in the backtrace.
Yes, it must have happend before and left the socket buffer in an inconsistent
More information about the freebsd-current