panic -- sched lock recursed

2001-02-26 Thread Steve Kargl

It appears that lpd is again triggering a panic.  Sources
are from 25 Feb 01 at 1039 PST.  Kernel.debug, vmcore.0, kernel.0
available for the asking.

-- 
Steve

(kgdb) symbol-file kernel.debug
Reading symbols from kernel.debug...done.
(kgdb) exec-file /usr/tmp/kernel.0
(kgdb) core-file /usr/tmp/vmcore.0
IdlePTD 3481600
initial pcb at 2944e0
panicstr: from debugger
panic messages:
---
panic: mutex sched lock recursed at /usr/src/sys/kern/kern_synch.c:873
panic: from debugger
Uptime: 1m16s

dumping to dev da0s2b, offset 466944
dump 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110
 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 
86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60
 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 3
3 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5
 4 3 2 1 
---
#0  dumpsys () at /usr/src/sys/kern/kern_shutdown.c:476
476 if (dumping++) {
(kgdb) trace
trace command requires an argument
(kgdb) bt
#0  dumpsys () at /usr/src/sys/kern/kern_shutdown.c:476
#1  0xc016c2af in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:319
#2  0xc016c679 in panic (fmt=0xc023c4d4 "from debugger")
at /usr/src/sys/kern/kern_shutdown.c:569
#3  0xc012e0f1 in db_panic (addr=-1071565276, have_addr=0, count=-1, 
modif=0xc7c44cb4 "") at /usr/src/sys/ddb/db_command.c:433
#4  0xc012e091 in db_command (last_cmdp=0xc0267d14, cmd_table=0xc0267b74, 
aux_cmd_tablep=0xc02822b0) at /usr/src/sys/ddb/db_command.c:333
#5  0xc012e156 in db_command_loop () at /usr/src/sys/ddb/db_command.c:455
#6  0xc013031f in db_trap (type=3, code=0) at /usr/src/sys/ddb/db_trap.c:71
#7  0xc02133b6 in kdb_trap (type=3, code=0, regs=0xc7c44db4)
at /usr/src/sys/i386/i386/db_interface.c:164
#8  0xc021fbcc in trap (frame={tf_fs = 24, tf_es = 16, tf_ds = 16, 
  tf_edi = -1071358496, tf_esi = 256, tf_ebp = -943436288, 
  tf_isp = -943436320, tf_ebx = 2, tf_edx = -1072984320, tf_ecx = 32, 
  tf_eax = 18, tf_trapno = 3, tf_err = 0, tf_eip = -1071565276, tf_cs = 8, 
  tf_eflags = 70, tf_esp = -1071270881, tf_ss = -1071359837})
at /usr/src/sys/i386/i386/trap.c:614
#9  0xc0213624 in Debugger (msg=0xc02458a3 "panic") at machine/cpufunc.h:60
#10 0xc016c670 in panic (fmt=0xc0244dc4 "mutex %s recursed at %s:%d")
at /usr/src/sys/kern/kern_shutdown.c:567
#11 0xc01673d3 in _mtx_assert (m=0xc02acb20, what=9, 
file=0xc0245de0 "/usr/src/sys/kern/kern_synch.c", line=873)
at /usr/src/sys/kern/kern_mutex.c:614
#12 0xc0171729 in mi_switch () at /usr/src/sys/kern/kern_synch.c:873
#13 0xc0161120 in ithread_schedule (ithread=0xc0aa1400, do_switch=1)
at /usr/src/sys/kern/kern_intr.c:378
#14 0xc022440b in sched_ithd (cookie=0x7) at /usr/src/sys/i386/isa/ithread.c:99
#15 0x8 in ?? ()
#16 0xc021e775 in sw1b ()
#17 0xc0161648 in ithread_loop (arg=0xc0aa1400)
at /usr/src/sys/kern/kern_intr.c:535
#18 0xc0160558 in fork_exit (callout=0xc0161288 ithread_loop, 
arg=0xc0aa1400, frame=0xc7c44fa8) at /usr/src/sys/kern/kern_fork.c:672




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



RE: panic -- sched lock recursed

2001-02-26 Thread John Baldwin


On 26-Feb-01 Steve Kargl wrote:
 It appears that lpd is again triggering a panic.  Sources
 are from 25 Feb 01 at 1039 PST.  Kernel.debug, vmcore.0, kernel.0
 available for the asking.

This is a different panic the dreaded 'ltr' panics everyone has been seeing,
but the enable_intr() in trap keeps hiding it.  I think I'll go commit a hack
for that right now.

-- 

John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message