From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Ralf Mardorf <ralf.mardorf@alice-dsl.net>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: Kenrel panic with 3.18.7-rt2 - rootfs at MMC
Date: Fri, 6 Mar 2015 13:24:41 +0100 [thread overview]
Message-ID: <20150306122441.GB10155@linutronix.de> (raw)
In-Reply-To: <20150302043404.13bdf10e@archlinux>
* Ralf Mardorf | 2015-03-02 04:34:04 [+0100]:
>On Sun, 1 Mar 2015 20:25:24 -0500, Paul Gortmaker wrote:
>>In the future, putting the log lines in line (vs attachment) makes
>>it easier to reply and comment - meaning more people will look
>>at the report.
It would be usefull not to reply to this thread since what I read it
does not seem to be MMC related.
>I get kernel panic for 3.18.7-rt2 on an AMD Athlon dual-core x86_64
>machine, but I don't know what log files to post.
The dmesg output / kernel log would be usefull. If you can get it out of
serial or logged on disk, that would be good.
>a high amount of unreadable fast messages scrolled, finished with
>something similar to "recursive fixed, restart is needed".
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.
>Regards,
>Ralf
Sebastian
next prev parent reply other threads:[~2015-03-06 12:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 9:46 Kenrel panic with 3.18.7-rt2 - rootfs at MMC Michal Šmucr
2015-02-26 11:29 ` [RT PATCH] mmc: sdhci: don't provide hard irq handler Sebastian Andrzej Siewior
2015-02-27 9:33 ` Michal Šmucr
2015-03-02 1:25 ` Kenrel panic with 3.18.7-rt2 - rootfs at MMC Paul Gortmaker
2015-03-02 1:31 ` Paul Gortmaker
2015-03-02 11:43 ` Michal Šmucr
2015-03-02 3:34 ` Ralf Mardorf
2015-03-06 12:24 ` Sebastian Andrzej Siewior [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-03-06 16:43 Ralf Mardorf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150306122441.GB10155@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=ralf.mardorf@alice-dsl.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).