On Fri, Mar 6, 2015 at 11:47 AM, Ralf Mardorf <ralf.mardorf@xxxxxxxxxxxxx> wrote: > On Fri, 6 Mar 2015 17:43:36 +0100, Ralf Mardorf wrote: >>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. >>I guess I'm a power user regarding several Linux things, but I'm >>completely lost regarding some issues, since several distros switched >>to systemd. So I just did a quick test with 3.18.9-rt on an athlon x4 64 bit. Did "make localyesconfig" - ensured RT_FULL was on and that booted OK without any triple fault or similar. So unless you can capture some of the log with a camera or a serial port, it is hard for us to help figure out what the problem is. Paul. -- > > Sorry, I didn't keep the thread as wanted, but forgot to change the > subject. Fixed ;). > -- > 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 -- 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
