From owner-freebsd-current Tue Feb 6 12:36:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from jbloom.jbloom.org (reyim.ne.mediaone.net [24.218.251.241]) by hub.freebsd.org (Postfix) with ESMTP id A85C337B4EC; Tue, 6 Feb 2001 12:36:11 -0800 (PST) Received: from acm.org (localhost [127.0.0.1]) by jbloom.jbloom.org (8.11.2/8.11.2) with ESMTP id f16Ka6030030; Tue, 6 Feb 2001 15:36:07 -0500 (EST) (envelope-from bloom@acm.org) Message-ID: <3A806036.5694FD66@acm.org> Date: Tue, 06 Feb 2001 15:36:06 -0500 From: Jim Bloom Reply-To: bloom@acm.org X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: John Baldwin Cc: current@FreeBSD.ORG Subject: Re: Kernel Panic from Yesterday's CVSup References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here are the registers (subject to typing errors): cs 0xc2fb0008 ds 0xa000010 es 0x10 fs 0x18 ss 0x10 eax 0x12 ecx 0x20 edx 0xc00b8f00 ebx 0x2 esp 0xc2fbee1c ebp 0xc2fbee28 esi 0x100 edi 0xc0290990 __set_sysctl_set_sym_sysctl__kern_fscale+0x4 eip 0xc0266fcc Debugger+44 efl 0x56 Jim Bloom bloom@acm.org John Baldwin wrote: > > On 06-Feb-01 Jim Bloom wrote: > > The line where I was having the trap is still within cpu_switch (line > > 236 of swtch.s). > > > > I added WITNESS and INVARIANTS to my kernel and I get a new panic. > > This time I see: > > > > kernel trap 12 with interrupts disabled > > panic: mutex sched lock recursed at ../../kern/kern_synch.c:918 > > > > panic() > > _mtx_assert(c031b6c0,9,c0290990,396,c043b100) at _mtx_assert+0x63 > > mi_switch(c031b6c0,0,c,c24bef08,c02681cd) at mi_switch+0x25 > > sched_ithd(e) at sched_ithd+0xd9 > > Xresume14() at Xresume14+0x8 > > --- interrupt, eip = 0xc02b0008, esp - 0xc2fbeee4, epb = 0xc2feed4 --- > > __set_sysinit_set_sym_sc_mem_sys_init(c0275020,c02b0008,286,c031b7230,0) > > at __set_sysinit_set_sym_sc_mem_sys_init+0x644 > > > > Jim Bloom > > bloom@acm.org > > Hmmmmm, can you show the registers? I wonder if we are somehow running a > process that isn't fully created yet. Hmm, that shouldn't be a problem > looking at fork1().. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message