Date: Tue, 2 Jul 2002 15:54:39 -0700 (PDT) From: Julian Elischer <julian@elischer.org> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: freebsd-current@freebsd.org Subject: Re: KSE signal problems still Message-ID: <Pine.BSF.4.21.0207021535240.97650-100000@InterJet.elischer.org> In-Reply-To: <15650.5957.15992.275984@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2 Jul 2002, Andrew Gallatin wrote:
>
> An easy way to induce a panic w/a post KSE -current is to ^C gdb as it
> starts on an SMP machine:
A possibly related breakage is:
type ^Z while doing "make buiildworld" (or something similar).
when you type 'fg' there is a high change the build will abort..
>
> # gdb -k /var/crash/kernel.1 /var/crash/vmcore.1
> GNU gdb 5.2.0 (FreeBSD) 20020627
> Copyright 2002 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and
> you are
> welcome to change it and/or distribute copies of it under certain
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB. Type "show warranty" for
> details.
> This GDB was configured as "i386-undermydesk-freebsd"...
> ^C
>
> panic: mutex sched lock not owned at ../../../kern/subr_smp.c:126
> cpuid = 1; lapic.id = 01000000
> Debugger("panic")
> Stopped at Debugger+0x46: xchgl %ebx,in_Debugger.0
> db> where
> No such command
> db> tr
> Debugger(c02dbf5a) at Debugger+0x46
> panic(c02db1a8,c02db318,c02df736,7e,c4445540) at panic+0xd6
> _mtx_assert(c0315440,1,c02df736,7e) at _mtx_assert+0xa8
> forward_signal(c4445540) at forward_signal+0x1a
> tdsignal(c4445540,2,2) at tdsignal+0x182
> psignal(c443d558,2) at psignal+0x3c8
> pgsignal(c441ad00,2,1,c441ad1c,0) at pgsignal+0x63
> ttyinput(3,c41e8e30,c41e8e00,0,c0347903) at ttyinput+0x316
> ptcwrite(c4307a00,d7d5ec88,7f0011,1,d7d5ebc4) at ptcwrite+0x17f
> spec_write(d7d5ebf0,d7d5ec3c,c0204cc8,d7d5ebf0,7f0011) at spec_write+0x5a
> spec_vnoperate(d7d5ebf0) at spec_vnoperate+0x13
> vn_write(c41ded5c,d7d5ec88,c440cd80,0,c409e780) at vn_write+0x1c8
> dofilewrite(c409e780,c41ded5c,5,8088000,1) at dofilewrite+0xaf
> write(c409e780,d7d5ed14,3,b,282) at write+0x39
> syscall(2f,2f,2f,1,8073410) at syscall+0x23c
> syscall_with_err_pushed() at syscall_with_err_pushed+0x1b
> --- syscall (4, FreeBSD ELF, write), eip = 0x281fb3a3, esp =
> 0xbfbff37c, ebp = 0xbfbff3e8 ---
>
>
hummmmm
so, the question is:
where should we get the sched lock?
>
> Drew
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0207021535240.97650-100000>