Date: Sun, 6 Sep 1998 09:26:52 +0100 (BST) From: Doug Rabson <dfr@nlsystems.com> To: "Andrey A. Chernov" <ache@nagual.pp.ru> Cc: Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG, dfr@FreeBSD.ORG Subject: Re: sbflush 2 panic, uipc_socket2.c Message-ID: <Pine.BSF.4.01.9809060926150.796-100000@herring.nlsystems.com> In-Reply-To: <19980906083007.A19996@nagual.pp.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 6 Sep 1998, Andrey A. Chernov wrote: > On Fri, Sep 04, 1998 at 02:31:52PM +0400, Andrey A. Chernov wrote: > > On Fri, Sep 04, 1998 at 12:24:25AM +0000, Mike Smith wrote: > > > > On Thu, Sep 03, 1998 at 01:15:02PM +0000, Mike Smith wrote: > > > > > > Approx. once a day I have this panic (see subj.) on heavily loaded > > > > > > -current HTTP server. Is any solution possible? Briefly looking through > > > > > > code I think some sort of spl protection needed between freeing sb_cc and > > > > > > checking it again. > > > > > > > > > > That sounds reasonable. What have you tried so far? > > > > > > > > No, just gather more panic details: > > > > > > How about whacking an splnet() around it and letting us know how it > > > goes? > > > > No, the code already under splnet() from tcp_usr_disconnect() > > It means that internal mbuf structure is changed somehow under splnet() > > I found that the panic trigger is new ip defragmenting code from dfr, > there is no such panic before this commit. ssh key exchange (large > packets) can effectively cause panic after 10min when someone quickly > log in with ssh after machine come after reboot. Thanks for working on this Andrey. I'll have a look at the code today and see if I can see anything. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.01.9809060926150.796-100000>