![]() | |||||||||||||
Messages in this thread |
bootflag.c should not use its own private ACPI table parser/mapper -- this is a bug: http://bugme.osdl.org/show_bug.cgi?id=1922 Elliot, If you add your system info to that bug report and volunteer to help test the fix, I'll be delighted to use your system as an excuse to address this issue promptly. thanks, -Len ps. The reason you enter diag mode when SBF is disabled is because w/o SBF, the BOOTING flag doesn't get cleared, so the BIOS assumes the system didn't boot correctly and when entered next it is in DIAG mode. This is expected. IMO, module load time is probably too early to clear the BOOTING flag anyway. It should be cleared upon completion of successful boot -- though I'm not sure how to identify that point. Come to think about it, maybe we should delay clearing the BOOTING flag until Linux initiates a graceful shutdown, sleep, or reboot? If the system died b/c of bad RAM or something, that would make it run through DIAGS when it next enters POST. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2005-03-22 13:01 [from the cache] ©2003-2008 | |||||||||||||