From owner-freebsd-current Thu Sep 3 13:18:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA12280 for freebsd-current-outgoing; Thu, 3 Sep 1998 13:18:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA12275 for ; Thu, 3 Sep 1998 13:18:49 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA01029; Thu, 3 Sep 1998 13:15:02 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199809031315.NAA01029@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Andrey A. Chernov" cc: current@FreeBSD.ORG Subject: Re: sbflush 2 panic, uipc_socket2.c In-reply-to: Your message of "Thu, 03 Sep 1998 14:18:08 +0400." <19980903141808.A939@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 03 Sep 1998 13:15:02 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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? -- \\ 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