From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: jordan <triplesquarednine@gmail.com>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Thomas Petazzoni <thomas@free-electrons.com>
Subject: Re: 3.14.3-rt5: at91: Crash early at boot
Date: Fri, 13 Jun 2014 17:28:01 +0200 [thread overview]
Message-ID: <20140613152801.GM3448@lukather> (raw)
In-Reply-To: <CAOcfFMw9e3_=Yz0jyU7HdYx4Kod=9-X5T9JPNcUjoVC4jBtS9Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 991 bytes --]
Hi Jordan,
On Fri, Jun 13, 2014 at 10:48:05AM -0400, jordan wrote:
> Maxim,
>
> You may be one of the people affected by some upstream RT changes
> [dating back to 3.12-rt] that causes linux-rt to fail to boot on some
> H/W.
>
> I myself, am affected, i know of lots of AMD users and the some ARM
> h/w that doesn't boot, without reverting a couple of these changes.
> [as noted here;
> http://www.spinics.net/lists/linux-rt-users/msg11655.html]... You
> could try this patch; http://pastebin.com/jb4tuNna - which is applied
> after the rt patchset ... This is how i have been able to use RT on my
> machines for many RT releases now.
>
> your problem may or may not be the same. but it's probably worth a try.
I just gave your patch a try, and unfortunately, it doesn't change
anything, I still get the same panic at the same moment.
Thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-06-13 15:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 14:25 3.14.3-rt5: at91: Crash early at boot Maxime Ripard
2014-06-13 14:48 ` jordan
2014-06-13 15:28 ` Maxime Ripard [this message]
2015-02-17 8:38 ` Sebastian Andrzej Siewior
2015-03-16 18:19 ` Maxime Ripard
2015-03-16 18:30 ` Alexandre Belloni
2015-04-13 13:37 ` Christian Jann
2015-04-16 7:50 ` Sebastian Andrzej Siewior
2015-04-16 9:55 ` Christian Jann
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=20140613152801.GM3448@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=thomas@free-electrons.com \
--cc=triplesquarednine@gmail.com \
/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).