Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 13 Feb 2002 13:36:48 -0800 (PST)
From:      David Wolfskill <david@catwhisker.org>
To:        current@freebsd.org
Subject:   Panic at schedcpu+0x13d with today's -CURRENT
Message-ID:  <200202132136.g1DLamv37458@bunrab.catwhisker.org>

next in thread | raw e-mail | index | archive | help
So... I'm at BSDCon; got today's -STABLE & -CURRENT built & running
(serially) on the build machine.  I then "cloned" the slice for today's
-CURRENT from slice 4 to slice 3, cleaned up the source tree a bit, then
went through the process Greg Shapiro posted for setting up sendmail
8.12.2 for testing.  Last part of that is "make buildworld", "make
installworld", & "mergemaster", so that's what the machine was doing
when I went to lunch.

Came back, and the box was not responding to pings... and I belatedly
recalled that I had a serial console that I can get to.  Here's some
information; more available upon request (though I'll try to avoid
spamming the entire list with the additional stuff -- interested
folks can contact me via email or in person at BSDCon):

FreeBSD/i386 (freebeast.catwhisker.org) (cuaa0)

login: lock order reversal
 1st 0xc0336a80 sched lock @ /usr/src/sys/kern/kern_synch.c:850
 2nd 0xc038fea0 sio @ /usr/src/sys/dev/sio/sio.c:3137
kernel trap 12 with interrupts disabled


Fatal trap 12: page fault while in kernel mode
cpuid = 0; lapic.id = 00000000
fault virtual address   = 0x6d
fault code              = supervisor read, page not present
instruction pointer     = 0x8:0xc01a7b15
stack pointer           = 0x10:0xd7a26cbc
frame pointer           = 0x10:0xd7a26cd8
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, def32 1, gran 1
processor eflags        = resume, IOPL = 0
current process         = 13 (swi6: tty:sio clock)
kernel: type 12 trap, code=0
timeout stopping cpus
Stopped at      schedcpu+0x13d: cmpb    $0x9f,0x6d(%edx)
db> trace
schedcpu(0) at schedcpu+0x13d
softclock(0) at softclock+0x136
ithread_loop(c145d680,d7a26d48,c145d680,c0196590,0) at ithread_loop+0x12e
fork_exit(c0196590,c145d680,d7a26d48) at fork_exit+0x9c
fork_trampoline() at fork_trampoline+0x8
db> show locks
shared (sx) allproc (0xc031ba40) locked @ /usr/src/sys/kern/kern_synch.c:267
exclusive (spin mutex) sched lock (0xc0336a80) locked @ /usr/src/sys/kern/kern_synch.c:850
db> show lockedvnode    
Locked vnodes
panic: blockable sleep lock (sleep mutex) mountlist @ /usr/src/sys/kern/vfs_subr.c:2371
cpuid = 0; lapic.id = 00000000
Debugger("panic")
Stopped at      schedcpu+0x13d: cmpb    $0x9f,0x6d(%edx)
db> show pcpu 0
cpuid        = 0
curthread    = 0xd682d000: pid 13 "swi6: tty:sio clock"
curpcb       = 0xd7a26da0
fpcurthread  = none
idlethread   = 0xd682d600: pid 11 "idle: cpu0"
currentldt   = 0x28
spin locks held:
exclusive (spin mutex) sched lock (0xc0336a80) locked @ /usr/src/sys/kern/kern_synch.c:850
db> show pcpu 1
cpuid        = 1
curthread    = 0xdb3e6c00: pid 87109 "sh"
curpcb       = 0xdb3eada0
fpcurthread  = none
idlethread   = 0xd682d900: pid 10 "idle: cpu1"
currentldt   = 0x28
spin locks held:
exclusive (spin mutex) clk (0xc033a360) locked @ /usr/src/sys/i386/isa/clock.c:415
db> 

Hints?  Clues?

Thanks,
david
-- 
David H. Wolfskill				david@catwhisker.org
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 majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200202132136.g1DLamv37458>