On some new hardware...
- ASUS N4L-VM mainboard
- Intel Core Duo CPU "Genuine Intel(R) CPU T2500 @ 2.00GHz"
... I've encountered the "cpu 1 failed to start" problem. The kernel hangs
after cpu0
is detected; the second core, cpu1, isn't recognized.
There are already several bugs filed for this kind of problem:
4945355 ("cpu 1 failed to start" still happens on Dell, Opteron/Tyan,
Opteron/Arima)
closed, not reproducible
4853044 (3.06GHz hyperthreaded processors fail to start, hang machine)
closed, fixed
4947394 (x86: if a CPU fails to start, machine hangs)
in progress, bug
What's the state of bugs, what kind of additional information is available
for these bugs (especially 4947394) that isn't visible on bugs.opensolaris.org?
Workarounds for the ASUS N4L-VM that I've found so far are:
- boot with kmdb, use F1-A to break into kmdb while the startup attempt for the
second core is hanging, and simply ":c" continue:
system startup continues and both cpu cores are online
(why does dropping into kmdb fix this problem?)
or
- remove the two "cmn_err()" calls from usr/src/uts/i86pc/os/mp_startup.c,
function
init_cpu_info():
http://cvs.opensolaris.org/source/xref/on/usr/src/uts/i86pc/os/mp_startup.c#init_cpu_info
(it seems the problem is that we're somehow stalling in log_enter() when
bringing all
cpu cores online, when sending messages to the console log)
This message posted from opensolaris.org
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
