Subject: Re: panic: setrunqueue
To: Julio M. Merino Vidal <jmmv84@gmail.com>
From: Pavel Cahyna <pavel.cahyna@st.mff.cuni.cz>
List: current-users
Date: 02/13/2006 11:53:52
On Sun, Feb 12, 2006 at 10:51:10PM +0100, Julio M. Merino Vidal wrote:

Setrunqueue is not the right panic message - this looks like a second
panic when ddb attempted to sync filesystems. Look at the backtrace, how
ddb was called recursively.

> #0  0x3fefc000 in ?? ()
> #1  0xc02c56f2 in cpu_reboot (howto=256, bootstr=0x0)
>     at /usr/src/sys/arch/i386/i386/machdep.c:755
> #2  0xc014f020 in db_sync_cmd (addr=0, have_addr=0, count=-1070595662,
>     modif=0xcba2f520 "A7\001") at /usr/src/sys/ddb/db_command.c:798
> #3  0xc014ea57 in db_command (last_cmdp=0xc03db964, cmd_table=0xc0357ac0)
>     at /usr/src/sys/ddb/db_command.c:503
> #4  0xc014e766 in db_command_loop () at /usr/src/sys/ddb/db_command.c:294
> #5  0xc01518a4 in db_trap (type=1, code=0) at /usr/src/sys/ddb/db_trap.c:101
> #6  0xc02c2d72 in kdb_trap (type=1, code=0, regs=0xcba2f764)
>     at /usr/src/sys/arch/i386/i386/db_interface.c:226
> #7  0xc02cdee4 in trap (frame=0xcba2f764)
>     at /usr/src/sys/arch/i386/i386/trap.c:310
> #8  0xc010af95 in calltrap ()
> #9  0xc026e5d1 in panic (fmt=0xc038806f "setrunqueue")
>     at /usr/src/sys/kern/subr_prf.c:243
> #10 0xc0260f58 in setrunqueue (l=0xcbc715b0)
>     at /usr/src/sys/kern/kern_synch.c:1377
> #11 0xc0260c95 in setrunnable (l=0xcbc715b0)
>     at /usr/src/sys/kern/kern_synch.c:1134
> #12 0xc025a864 in kpsignal2 (p=0xcbbd900c, ksi=0xcba2f89c, dolock=1)
>     at /usr/src/sys/kern/kern_sig.c:1371
> #13 0xc0265eee in itimerfire (pt=0xcbbd3c98)
>     at /usr/src/sys/kern/kern_time.c:1266
> #14 0xc026552a in realtimerexpire (arg=0xcbbd3c98)
>     at /usr/src/sys/kern/kern_time.c:943
> #15 0xc0266736 in softclock (v=0x0) at /usr/src/sys/kern/kern_timeout.c:387
> #16 0xc02bd96c in softintr_dispatch (which=0)
>     at /usr/src/sys/arch/x86/x86/softintr.c:104
> #17 0xc010ac92 in Xsoftclock ()
> #18 0xc02500e9 in lockmgr (lkp=0xccb6447c, flags=65554, interlkp=0xccb6440c)
>     at /usr/src/sys/kern/kern_lock.c:788
> #19 0xc029d4a7 in genfs_lock (v=0xcba2fa60)
>     at /usr/src/sys/miscfs/genfs/genfs_vnops.c:300
> #20 0xc029c408 in VOP_LOCK (vp=0xccb6440c, flags=65554)
>     at /usr/src/sys/kern/vnode_if.c:1228
> #21 0xc029a2fa in vn_lock (vp=0xccb6440c, flags=65554)
>     at /usr/src/sys/kern/vfs_vnops.c:725
> #22 0xc0292537 in vget (vp=0xccb6440c, flags=65554)
>     at /usr/src/sys/kern/vfs_subr.c:1204
> #23 0xc01ee14e in ffs_sync (mp=0xc17cf000, waitfor=1, cred=0xcae80dc8,
>     l=0xcca0b9d4) at /usr/src/sys/ufs/ffs/ffs_vfsops.c:1331
> #24 0xc0295002 in dounmount (mp=<incomplete type>, flags=524288, l=0xcca0b9d4)
>     at /usr/src/sys/kern/vfs_syscalls.c:579
> #25 0xc029360f in vfs_unmountall (l=0xcca0b9d4)
>     at /usr/src/sys/kern/vfs_subr.c:2170
> #26 0xc02936be in vfs_shutdown () at /usr/src/sys/kern/vfs_subr.c:2229
> #27 0xc02c5706 in cpu_reboot (howto=256, bootstr=0x0)
>     at /usr/src/sys/arch/i386/i386/machdep.c:741
> #28 0xc014f020 in db_sync_cmd (addr=0, have_addr=0, count=-1070595662,

> #33 0xc02cdee4 in trap (frame=0xcba2fe04)
>     at /usr/src/sys/arch/i386/i386/trap.c:310
> #34 0xc010af95 in calltrap ()

The real panic happens here. What is the original panic message?

> #35 0xc021e4b6 in uvmspace_free (vm=0xcc864d28)
>     at /usr/src/sys/uvm/uvm_map.c:3802
> #36 0xc024a3df in exit1 (l=0xcca0b9d4, rv=0)
>     at /usr/src/sys/kern/kern_exit.c:341
> #37 0xc024a19b in sys_exit (l=0xcca0b9d4, v=0xcba2ff64, retval=0xcba2ff5c)
>     at /usr/src/sys/kern/kern_exit.c:176
> #38 0xc02cd94b in syscall_plain (frame=0xcba2ffa8)
>     at /usr/src/sys/arch/i386/i386/syscall.c:160

Pavel