Re: Latest -current complete lockup (tcp changes?)

Andrey Chernov wrote:
On Mon, Mar 26, 2007 at 01:28:46AM +0200, Andre Oppermann wrote:
Giorgos Keramidas wrote:
Hi Andre,

The attached thread below is a reply from Nicolas Blais which shows some
problems with the recent SACK changes. Any idea how we can proceed from
this point?
Please update to rev. 1.36 of sys/netinet/tcp_sack.c. The KASSERT() was
too tight but actually caught a bug that would have caused a crash anyway.

The problem is deeper than that (((
I still got the same lockup, just with more net activity.
I even try to completely disable sack, with the same result, so probem is
somewhere else. Last working kernel still from Mar 22.

I'll give a CVSup / upgrade a try and see what happens.

-Garrett

_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: Latest -current complete lockup (tcp changes?)
    ... The attached thread below is a reply from Nicolas Blais which shows some ... problems with the recent SACK changes. ... I'm updating my CVSup tree as I type this, and I'll let you know after a ...
    (freebsd-current)
  • Re: Latest -current complete lockup (tcp changes?)
    ... The attached thread below is a reply from Nicolas Blais which shows some ... problems with the recent SACK changes. ... I even try to completely disable sack, with the same result, so probem is ... Last working kernel still from Mar 22. ...
    (freebsd-current)