>Date: Sun, 10 Feb 2002 08:31:57 -0800 (PST)
>From: David Wolfskill <[EMAIL PROTECTED]>

>db> trace
>runq_choose(c0358880,d683dd0c,c02b01ce,c01a7857,34948) at runq_choose+0x83
>choosethread(c01a7857,34948,c0194f10,d682d500,77) at choosethread+0xd
>sw1(d682d604,d683dd34,c0194d50,0,d683dd48) at sw1+0x20
>idle_proc(0,d683dd48,0,c0194f10,0) at idle_proc+0x5c
>fork_exit(c0194f10,0,d683dd48) at fork_exit+0x9c
>fork_trampoline() at fork_trampoline+0x8


>Anything else I can do to help find & resolve this?

A little more information:

* My laptop (running the same sources, though a somewhat different
  kernel config and a rather different hardware config) did not exhibit
  the symptoms.

* A few other things occurred to me that might be of interest with DDB:

db> show pcpu 0
cpuid        = 0
curthread    = 0xd682d604: pid 11 "idle: cpu0"
curpcb       = 0xd683dda0
fpcurthread  = none
idlethread   = 0xd682d604: pid 11 "idle: cpu0"
currentldt   = 0x28
spin locks held:
exclusive (spin mutex) sched lock (0xc0335600) locked @ 
db> show pcpu 1
cpuid        = 1
curthread    = 0xda41a604: pid 289 "reboot"
curpcb       = 0xda432da0
fpcurthread  = none
idlethread   = 0xd682d904: pid 10 "idle: cpu1"
currentldt   = 0x28
spin locks held:
exclusive (spin mutex) clk (0xc0338ee0) locked @ /usr/src/sys/i386/isa/clock.c:415
db> show locks
exclusive (spin mutex) sched lock (0xc0335600) locked @ 
db> show lockedvnodes
Locked vnodes
panic: blockable sleep lock (sleep mutex) mountlist @ /usr/src/sys/kern/vfs_subr.c:2371
cpuid = 0; lapic.id = 00000000
Stopped at      runq_choose+0x83:       movl    0(%edx),%eax

david       (links to my resume at http://www.catwhisker.org/~david)
David H. Wolfskill                              [EMAIL PROTECTED]
I believe it would be irresponsible (and thus, unethical) for me to advise,
recommend, or support the use of any product that is or depends on any
Microsoft product for any purpose other than personal amusement.

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

Reply via email to