* Ralf Mardorf | 2015-03-06 17:47:00 [+0100]: >On Fri, 6 Mar 2015 13:24:41 +0100, Sebastian Andrzej Siewior wrote: >>if the system is still responsible you could "dmesg > file" and then >>that file would interresting as long as there is no systemd crap in >>it. > >That's the problem, the system isn't responsive anymore. There also is >no file /var/log/dmesg. I can reboot and run the dmesg command, but it >only shows the messages for the last boot. So if you don't get the crash message anymore then it gets tricky. You could use the serial console and read it there (if you have a serial port and another machine). The other trick might be to use "printk delay" and then memorize it or use a camera :) Sebastian -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
