On 2012-02-08 at 09:34:14 [+0100], Paavo Nurminen <paavo.nurminen@xxxxxxxx> wrote: > Theory and practice does not seem to meet. Step by step, valid, > instructions, please. > > I read from User Guide, Boot Loader section: > "If "debug syslog" is enabled, a warm reboot after a crash (PANIC??) shows > these additional options: > -Display syslog from previous session > -Save syslog from previous session" > > These options are not shown upon reboot. The feature had been broken for while, IIRC including the alpha 3 release. So if you're still testing with that one, that would explain it. With a recent revision the feature should work though (at least it does on my machines). I seem to recall a report that it still doesn't on some hardware, for which I don't have an explanation ATM. > I have made one experiment where I chose 'Display syslog on screen'. > Several screen fulls were shown and it showed that my system was > correctly identified. After AHCI section came PANIC, showing this > message: > PANIC: acquire_spinlock(): Failed to acquire spinlock 0x80175a08 for a > long time! That is a known issue. Disabling SMP might help. Since you get to KDL anyway, using the "syslog" command yields better results, though. CU, Ingo