From owner-freebsd-stable Sat Sep 25 9:23: 3 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ady.warpnet.ro (ady.warpnet.ro [194.102.224.1]) by hub.freebsd.org (Postfix) with ESMTP id CF70714E74; Sat, 25 Sep 1999 09:22:44 -0700 (PDT) (envelope-from ady@warpnet.ro) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.9.3/8.9.3) with ESMTP id TAA04407; Sat, 25 Sep 1999 19:21:31 +0300 (EEST) (envelope-from ady@warpnet.ro) Date: Sat, 25 Sep 1999 19:21:31 +0300 (EEST) From: Adrian Penisoara To: Chris Costello Cc: Mark Powell , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: -stable (in)stability (was Re: Best version of FBSD for INN ?) In-Reply-To: <19990925111256.D21879@holly.calldei.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Sat, 25 Sep 1999, Chris Costello wrote: > On Sat, Sep 25, 1999, Adrian Penisoara wrote: > > PS: I could have filed a PR but I can't figure any way of reproducing > > this -- just a double panic caught by my co-worker, details posted on > > -stable on 19th Sep with "3.2-STABLE hangs after several hours" in > > the subject... > > When it happens, write down the panic message and send a PR. > Maybe someone else who can reproduce it can contribute here and > help get this problem fixed. The problem is that it doesn't panic -- that was the only panic that manifested, and it was a double one, which I believe it's even harder to debug. I had crushdumping enabled but nothing got dumped (probably because of double panicing). Thanks, Ady (@warpnet.ro) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message