Date: Mon, 18 Feb 2002 10:53:26 -0800 (PST) From: David Wolfskill <david@catwhisker.org> To: current@freebsd.org Subject: Hangs with today's -CURRENT Message-ID: <200202181853.g1IIrQQ61800@bunrab.catwhisker.org>
next in thread | raw e-mail | index | archive | help
Not entirely sure whether these hangs are related. First one (which I
have been able to reproduce, and from which I invoked the debugger) is
on my build machine, which is an SMP box:
Mounting root from ufs:/dev/ad0s4a
ad0s1: type 0xa5, start 63, end = 4192964, size 4192902 : OK
ad0s2: type 0xa5, start 4192965, end = 8385929, size 4192965 : OK
ad0s3: type 0xa5, start 8385930, end = 12578894, size 4192965 : OK
ad0s4: type 0xa5, start 12578895, end = 80276804, size 67697910 : OK
rMP: CPU1 apic_isntiatrita_liinziet(:) :t
0 i n g /lisnbti0n:/ i0nxi0t0
10700 lint1: 0x00010400 TPR: 0x00000010 SVR: 0x000001ff
SMP: AP CPU #1 Launched!
db> trace
siointr1(c3f59c00,c0390280,0,c02f9b03,661) at siointr1+0xb1
siointr(c3f59c00) at siointr+0x23
Xfastintr4() at Xfastintr4+0x34
--- interrupt, eip = 0xc01a72f1, esp = 0xd683cd04, ebp = 0xd683cd0c ---
runq_check(d682c600,d683cd34,c0195ca8,0,d683cd48) at runq_check+0x21
idle_proc(0,d683cd48,0,c0195e68,0) at idle_proc+0x2f
fork_exit(c0195e68,0,d683cd48) at fork_exit+0x9c
fork_trampoline() at fork_trampoline+0x8
db> show locks
exclusive (spin mutex) sio (0xc0390280) locked @ /usr/src/sys/dev/sio/sio.c:1633
db> show pcpu 0
cpuid = 0
curthread = 0xd682c600: pid 11 "idle: cpu0"
curpcb = 0xd683cda0
fpcurthread = none
idlethread = 0xd682c600: pid 11 "idle: cpu0"
currentldt = 0x28
spin locks held:
exclusive (spin mutex) sio (0xc0390280) locked @ /usr/src/sys/dev/sio/sio.c:1633
db> show pcpu 1
cpuid = 1
curthread = 0xd682c900: pid 10 "idle: cpu1"
curpcb = 0xd6838da0
fpcurthread = none
idlethread = 0xd682c900: pid 10 "idle: cpu1"
currentldt = 0x28
spin locks held:
db> show lockedvnodes
Locked vnodes
panic: blockable sleep lock (sleep mutex) mountlist @ /usr/src/sys/kern/vfs_subr.c:2386
cpuid = 0; lapic.id = 00000000
Debugger("panic")
Stopped at siointr1+0xb1: jmp siointr1+0x1b7
db> show map
Task map 0xc02927f1: pmap=0x86ff00f7, nentries=1581315584, version=268435456
kernel trap 12 with interrupts disabled
Fatal trap 12: page fault while in kernel mode
cpuid = 0; lapic.id = 00000000
fault virtual address = 0x83f6890c
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc0280898
stack pointer = 0x10:0xd683cb00
frame pointer = 0x10:0xd683cb0c
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = resume, IOPL = 0
current process = 11 (idle: cpu0)
kernel: type 12 trap, code=0
Stopped at siointr1+0xb1: jmp siointr1+0x1b7
db>
As noted, the machine is sitting, waiting for me to do more stuff to it,
which I'm quite willing to do.
The second is on my laptop. I don't have as extensive information on
that, because I use the laptop to access the other machines, so having
it non-responsive impairs my ability to do such things as send mail. :-)
But after breaking to the debugger, a "show locks" on the laptop yielded:
db> show locks
exclusive (sleep mutex) Giant (0x0408460) locked @ /usr/src/sys/kern/kern_intr.c:532
db>
Local CVS repository synced with cvsup14 (I think; I'd need to get the
build machine running again to be sure, as it is also the local CVSup
server) starting at 0347 hrs., ending around 0356 hrs. US/Pacific
(8 hrs. west of GMT/UTC).
Hints/clues/suggestions/...?
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?200202181853.g1IIrQQ61800>