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

From: Giorgos Keramidas <keramida_at_ceid.upatras.gr>
Date: Sun, 25 Mar 2007 22:49:46 +0300
On 2007-03-25 13:48, Nicolas Blais <nb_root_at_videotron.ca> wrote:
> > The panic happens after a small amount of network activity, inside
> > the TCP SACK code:
> >
> > ---------------------------------------------------------------------------
> > Disabling SACK lets me use my laptop again:
> >
> >     net.inet.tcp.sack.enable=0
> >
> > without any panics.
> 
> Same here. If you want to quickly crash your system, 
> net.inet.tcp.sack.enable=1 and start a torrent :)
> 
> I couldn't find what was causing my desktop to crash until I STOPPED
> trying to restart my torrent after boot :) . Though
> net.inet.tcp.sack.enable=0 fixed it.

Rebuilding a kernel will take a while here.  If you can try reverting
the following commit before I do, let me know if it fixes the panic.

% andre       2007-03-23 18:33:21 UTC
% 
%   FreeBSD src repository
% 
%   Modified files:
%     sys/netinet          tcp_input.c tcp_sack.c 
%   Log:
%   Bring SACK option handling in tcp_dooptions() in line with all other
%   options and ajust users accordingly.
%   
%   Revision  Changes    Path
%   1.326     +7 -4      src/sys/netinet/tcp_input.c
%   1.35      +1 -0      src/sys/netinet/tcp_sack.c
Received on Sun Mar 25 2007 - 17:50:28 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:07 UTC