Kenrel panic with 3.18.7-rt2 - rootfs at MMC
Quoted 2 lines · Sebastian Andrzej Siewior
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.
Kenrel panic with 3.18.7-rt2 - Was: Kenrel panic with 3.18.7-rt2 - rootfs at MMC
Quoted 11 lines · Ralf Mardorf
Quoted 3 lines · Sebastian Andrzej Siewior
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.
Sorry, I didn't keep the thread as wanted, but forgot to change the subject. Fixed ;).
Re: Kenrel panic with 3.18.7-rt2 - Was: Kenrel panic with 3.18.7-rt2 - rootfs at MMC
Quoted 8 lines · * Ralf Mardorf | 2015-03-06 17:47:00 [+0100]:
Quoted 3 lines · Sebastian Andrzej Siewior
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
Re: Kenrel panic with 3.18.7-rt2 - Was: Kenrel panic with 3.18.7-rt2 - rootfs at MMC
In reply to Ralf MardorfQuoted 6 lines · Ralf Mardorf
Quoted 5 lines · Ralf Mardorf
Quoted 3 lines · Sebastian Andrzej Siewior
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.
Quoted 6 lines
Quoted 6 lines
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.
--
Quoted 7 lines
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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Kenrel panic with 3.18.7-rt2 - Was: Kenrel panic with 3.18.7-rt2 - rootfs at MMC
Quoted 1 line · Paul Gortmaker
unless you can capture some of the log with a camera
Hi,
in the meanwhile I noticed that 3.14.28-rt25 works on my machine and 3.14.34-rt31 already doesn't work on my machine.
Can I send a pic as attachment or should I paste a link?
Regards,
Ralf
Re: Kenrel panic with 3.18.7-rt2 - Was: Kenrel panic with 3.18.7-rt2 - rootfs at MMC
Quoted 7 lines · [Re: Kenrel panic with 3.18.7-rt2 - Was: Kenrel panic with 3.18.7-rt2 - rootfs…
Quoted 1 line · Paul Gortmaker
unless you can capture some of the log with a camera
Hi,
in the meanwhile I noticed that 3.14.28-rt25 works on my machine and 3.14.34-rt31 already doesn't work on my machine.
Not a lot changed in there ; mostly stable merges, so if you could test the interim points, that might give a clue as to what happened.
Quoted 2 lines
Can I send a pic as attachment or should I paste a link?
Not sure the list will pass through an attachment that isn't just a plain text patch or similar; you might need a link instead.
P.
--
Quoted 3 lines
Regards,
Ralf