From owner-freebsd-current Fri Sep 4 00:28:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA15983 for freebsd-current-outgoing; Fri, 4 Sep 1998 00:28:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from word.smith.net.au (castles198.castles.com [208.214.165.198]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA15922 for ; Fri, 4 Sep 1998 00:27:55 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (LOCALHOST [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id AAA01179; Fri, 4 Sep 1998 00:24:26 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199809040024.AAA01179@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: "Andrey A. Chernov" cc: Mike Smith , current@FreeBSD.ORG Subject: Re: sbflush 2 panic, uipc_socket2.c In-reply-to: Your message of "Fri, 04 Sep 1998 10:34:27 +0400." <19980904103427.A3368@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 04 Sep 1998 00:24:25 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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? Thanks. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message