Re: panic: blockable sleep lock (sx) allproc @ /usr/local/src/sys/kern/kern_proc.c:212

[Garrett Wollman]

On Sun, 7 Oct 2001 14:49:16 +1000 (EST), Bruce Evans [EMAIL PROTECTED] said:

 Is using xconsole significantly better than tail -f /var/log/messages?

I don't know.  I think `xterm -C' is better than either one, if it can
be made to work properly.  (I have held off on updating to latest
-current in the hope that this might be resolved one way or the
other.)

-GAWollman


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

Re: panic: blockable sleep lock (sx) allproc @ /usr/local/src/sys/kern/kern_proc.c:212

[Bruce Evans]

On Sun, 30 Sep 2001, Doug Barton wrote:

   With -current as of last night around 7pm PDT:


 IdlePTD 4390912
 initial pcb at 320920
 panicstr: bremfree: bp 0xc68bf184 not locked
 panic messages:
 ---
 panic: blockable sleep lock (sx) allproc @
 /usr/local/src/sys/kern/kern_proc.c:212

 syncing disks... panic: bremfree: bp 0xc68bf184 not locked
 Uptime: 9h46m14s

 ...
 #10 0xc01cf4d5 in panic (fmt=0xc02b0f20 blockable sleep lock (%s) %s @
 %s:%d)
 at /usr/local/src/sys/kern/kern_shutdown.c:628
 #11 0xc01e6054 in witness_lock (lock=0xc035a9a0, flags=0,
 file=0xc02ad8e0 /usr/local/src/sys/kern/kern_proc.c, line=212)
 at /usr/local/src/sys/kern/subr_witness.c:493
 #12 0xc01d3625 in _sx_slock (sx=0xc035a9a0,
 file=0xc02ad8e0 /usr/local/src/sys/kern/kern_proc.c, line=212)
 at /usr/local/src/sys/kern/kern_sx.c:115
 #13 0xc01ca5e4 in pfind (pid=353) at
 /usr/local/src/sys/kern/kern_proc.c:212
 #14 0xc01e98a2 in selwakeup (sip=0xc179b804) at
 /usr/local/src/sys/kern/sys_generic.c:1292
 #15 0xc01f33a3 in ptcwakeup (tp=0xc179b828, flag=1)
 at /usr/local/src/sys/kern/tty_pty.c:321
 #16 0xc01f337a in ptsstart (tp=0xc179b828) at
 /usr/local/src/sys/kern/tty_pty.c:310
 #17 0xc01f0958 in ttstart (tp=0xc179b828) at
 /usr/local/src/sys/kern/tty.c:1409
 #18 0xc01f1da9 in tputchar (c=99, tp=0xc179b828) at
 /usr/local/src/sys/kern/tty.c:2469
 #19 0xc01e291f in putchar (c=99, arg=0xcd9a0be8) at
 /usr/local/src/sys/kern/subr_prf.c:306
 #20 0xc01e2b9e in kvprintf (
 fmt=0xc02add01 alcru: negative time of %ld usec for pid %d (%s)\n,
 func=0xc01e28d0 putchar, arg=0xcd9a0be8, radix=10, ap=0xcd9a0c00
 Þ/Ìÿ\002\020)
 at /usr/local/src/sys/kern/subr_prf.c:489
 #21 0xc01e284c in printf (
 fmt=0xc02add00 calcru: negative time of %ld usec for pid %d (%s)\n)
 at /usr/local/src/sys/kern/subr_prf.c:262
 #22 0xc01cdeab in calcru (p=0xcd0e7300, up=0xc189ae00, sp=0xc189ae08,
 ip=0x0)
 at /usr/local/src/sys/kern/kern_resource.c:669
 #23 0xc01c041c in exit1 (td=0xcd0e7404, rv=256) at
 /usr/local/src/sys/kern/kern_exit.c:318
 #24 0xc01bfdde in sys_exit (td=0xcd0e7404, uap=0xcd9a0d20)
 at /usr/local/src/sys/kern/kern_exit.c:110
 #25 0xc027543f in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47,
 tf_edi = 0,
   tf_esi = -1, tf_ebp = -1077937600, tf_isp = -845542028, tf_ebx =
 672297256,
   tf_edx = 512, tf_ecx = 672374048, tf_eax = 1, tf_trapno = 12, tf_err
 = 2,
   tf_eip = 671896240, tf_cs = 31, tf_eflags = 643, tf_esp =
 -1077937644, tf_ss = 47})
 at /usr/local/src/sys/i386/i386/trap.c:1122
 #26 0xc026953d in syscall_with_err_pushed ()

This is a well-know bug in printf(9).  The TIOCCONS ioctl always gave
non-deterministic crashes.  Now it gives determinstic panics when
pintf() is called while sched_lock is held.  Work-around: don't use
anything that uses TIOCCONS (xconsole?).

Bruce


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