Date: Fri, 4 Sep 1998 14:31:52 +0400 From: "Andrey A. Chernov" <ache@nagual.pp.ru> To: Mike Smith <mike@smith.net.au> Cc: current@FreeBSD.ORG Subject: Re: sbflush 2 panic, uipc_socket2.c Message-ID: <19980904143152.A20161@nagual.pp.ru> In-Reply-To: <199809040024.AAA01179@word.smith.net.au>; from mike@smith.net.au on Fri, Sep 04, 1998 at 12:24:25AM %2B0000 References: <19980904103427.A3368@nagual.pp.ru> <199809040024.AAA01179@word.smith.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
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() -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y 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?19980904143152.A20161>