Date: Fri, 4 Sep 1998 10:34:27 +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: <19980904103427.A3368@nagual.pp.ru> In-Reply-To: <199809031315.NAA01029@dingo.cdrom.com>; from mike@smith.net.au on Thu, Sep 03, 1998 at 01:15:02PM %2B0000 References: <19980903141808.A939@nagual.pp.ru> <199809031315.NAA01029@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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: #2 0xf012648e in sbflush () #3 0xf0150e93 in tcp_disconnect () #4 0xf0150646 in tcp_usr_disconnect () #5 0xf01242fc in sodisconnect () #6 0xf0124112 in soclose () #7 0xf011a42a in soo_close () #8 0xf0106b22 in closef () #9 0xf010610b in close () -- 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?19980904103427.A3368>