whoa, other_cpus: 0x0000000e, stopped_cpus: 0x00000004
From: Don Bowman (don_at_sandvine.com)
Date: 05/31/04
- Previous message: Don Bowman: "RE: sysctl lock, system lockup"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: "'current@freebsd.org'" <current@freebsd.org> Date: Sun, 30 May 2004 22:21:42 -0400
I came upon my machine, locked up. I was able
to drop into the debugger. The last message
out was:
"pmap_lazyfix: spun for 50000000"
When i tried to continue, i got this message instead:
whoa, other_cpus: 0x0000000e, stopped_cpus: 0x00000004
panic: stop_cpus() failed
at line 202 in file /usr/src/sys/i386/i386/db_interface.c
cpuid = 0;
boot() called on cpu#0
syncing disks, buffers remaining... panic: pmap_invalidate_range: interrupts
disabled
I'm not sure why the 'whoa, other_cpus' message
would come out?
This comes from sys/i386/i386/db_interface.c
Can this provide a clue as to why it was locked up?
I got the vmcore from this, what does one look for
in it?
--don
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
- Previous message: Don Bowman: "RE: sysctl lock, system lockup"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
