From owner-freebsd-current Fri Feb 8 10:54:31 2002 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id 5F4C237B416; Fri, 8 Feb 2002 10:54:26 -0800 (PST) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.11.3/8.10.1) with ESMTP id g18IslR77258; Fri, 8 Feb 2002 10:54:51 -0800 (PST) Date: Fri, 8 Feb 2002 10:54:47 -0800 (PST) From: Doug White To: John Baldwin Cc: Giorgos Keramidas , Subject: RE: bremfree related panic In-Reply-To: Message-ID: <20020208105356.E76713-100000@resnet.uoregon.edu> X-All-Your-Base: are belong to us MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 7 Feb 2002, John Baldwin wrote: > > IdlePTD at phsyical address 0x003d1000 > > initial pcb at physical address 0x00329bc0 > > panicstr: bremfree: bp 0xc2161734 not locked > > panic messages: > > --- > > panic: msleep > > Hmmm, wonder where that came from. > oh: > > KASSERT(ident != NULL && td->td_proc->p_stat == SRUN, ("msleep")); > > However, your trace shows some other type of panic, one not in msleep but from > a fatal kernel trap. As a data point, i can cause bremfree panics with ddb's panic function too. There is some wart in the panic handling that triggers the bremfree one, or the strings are screwed up :) Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message