Re: -current is _definitely_ not stable right now

2001-05-30 Thread John Baldwin
On 30-May-01 Doug Barton wrote: > John Baldwin wrote: >> >> On 28-May-01 Doug Barton wrote: >> > Gang, >> > >> > On the avi front, typing 'aviplay' with or without an argument is >> > guaranteed to instantly wedge the box. I attached a lot of running aviplay >> > through truss, but I have

Re: -current is _definitely_ not stable right now

2001-05-30 Thread Doug Barton
Doug Barton wrote: > This worked excellently for me! I patched the kernel and rebuilt, then > tested aviplay... success. Then I cvsup'ed, built/installed world and > kernel, and started stress testing. I'm currently running two builds of X > 4, one over NFS and one local, 'make cleandir'

Re: -current is _definitely_ not stable right now

2001-05-30 Thread Doug Barton
John Baldwin wrote: > > On 28-May-01 Doug Barton wrote: > > Gang, > > > > On the avi front, typing 'aviplay' with or without an argument is > > guaranteed to instantly wedge the box. I attached a lot of running aviplay > > through truss, but I have no way to know if it stopped at or before

RE: -current is _definitely_ not stable right now

2001-05-29 Thread John Baldwin
On 28-May-01 Doug Barton wrote: > Gang, > > On the avi front, typing 'aviplay' with or without an argument is > guaranteed to instantly wedge the box. I attached a lot of running aviplay > through truss, but I have no way to know if it stopped at or before the > offending instruction. As f

Re: -current is _definitely_ not stable right now

2001-05-29 Thread Thomas Moestl
On Tue, 2001/05/29 at 09:39:42 -0700, John Baldwin wrote: > > On 28-May-01 Doug Barton wrote: > > I forgot something: > > > > IdlePTD 4734976 > > initial pcb at 3b5f80 > > panicstr: mutex sched lock recursed at /usr/src/sys/kern/kern_synch.c:858 > > panic messages: > > I would need a traceback

Re: -current is _definitely_ not stable right now

2001-05-29 Thread John Baldwin
On 28-May-01 Doug Barton wrote: > I forgot something: > > IdlePTD 4734976 > initial pcb at 3b5f80 > panicstr: mutex sched lock recursed at /usr/src/sys/kern/kern_synch.c:858 > panic messages: I would need a traceback from here. It looks like someone called msleep or tsleep with sched lock held

Re: -current is _definitely_ not stable right now

2001-05-28 Thread Robert Watson
I haven't made any mutex commits -- my commits were credential-related. At least two bugs have popped up and been resolved since the pcred removal commits, including: 1) Bug in execve() such that saved uids/gids were not being done in some situations. 2) Bug in crfree() such that there was a

Re: -current is _definitely_ not stable right now

2001-05-28 Thread Doug Barton
I forgot something: IdlePTD 4734976 initial pcb at 3b5f80 panicstr: mutex sched lock recursed at /usr/src/sys/kern/kern_synch.c:858 panic messages: --- panic: blockable sleep lock (sx) allproc @ /usr/src/sys/kern/kern_proc.c:146 syncing disks... 90 90 panic: mutex sched lock recursed at /usr/src