From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Alexander Stein <alexander.stein@systec-electronic.com>,
rostedt@goodmis.org
Cc: linux-rt-users@vger.kernel.org
Subject: Re: Triggering BUG on SIGSEGV signaling
Date: Fri, 11 Dec 2015 18:32:54 +0100 [thread overview]
Message-ID: <20151211173254.GK6720@linutronix.de> (raw)
In-Reply-To: <68989327.QRdbeUK3if@ws-stein>
* Alexander Stein | 2015-11-26 13:10:04 [+0100]:
>For the records, it's the same bug which is fixed by https://kernel.googlesource.com/pub/scm/linux/kernel/git/rt/linux-rt-devel/+/v4.1.3-rt3-patches/patches/ARM-enable-irq-in-translation-section-permission-fau.patch
>This also fixes my problem on the old kernel.
Steven has been a good boy and merged this patch and a few others into
the latest v3.10 based -RT kernel. However if prefer to use v3.10.47-rt50
you might run into other bugs as well which are fixed in the meantime.
>Best regards,
>Alexander
Sebastian
prev parent reply other threads:[~2015-12-11 17:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 11:09 Triggering BUG on SIGSEGV signaling Alexander Stein
2015-11-26 12:10 ` Alexander Stein
2015-12-11 17:32 ` Sebastian Andrzej Siewior [this message]
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=20151211173254.GK6720@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=alexander.stein@systec-electronic.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
/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).