----- Original Message -----
From: "Jeremy Chadwick" <free...@jdc.parodius.com>
Two things to point out:
1) I've seen systems where "cpu_reset: Stopping other CPUs" gets printed
(or sometimes doesn't, see above), then for about 5 *full minutes* the
system sits there doing nothing, but then eventually reboots. Try being
a bit more patient to see if this is the case. Also try dropping to the
debugger via serial console (serial break) or VGA (Ctrl-Alt-Esc).
Waited over 24 hours with the machine sat at the sync print apparently
when our engineer kicked it with the reset button.
2) I'd recommend to those who are experiencing this problem to try
booting with ACPI disabled (it's one of the boot menu options), and then
try rebooting the system. If this works, chances are the issue is
related to the ACPI code, and someone may want to cross-post to
freebsd-acpi to get proper attention to it.
9 times out of 10 this doesn't work any more as machines require it for
correct driver detection, still worth a go but thought I'd mention it.
Regards
Steve
================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
