From: Nathan_Lynch@mentor.com (Nathan Lynch)
To: linux-arm-kernel@lists.infradead.org
Subject: Crash on ARM: 8148/1 flush TLS and thumbee register
Date: Mon, 3 Nov 2014 08:34:42 -0600 [thread overview]
Message-ID: <54579282.8030309@mentor.com> (raw)
In-Reply-To: <20141102221401.GA4042@n2100.arm.linux.org.uk>
On 11/02/2014 04:14 PM, Russell King - ARM Linux wrote:
> On Sun, Nov 02, 2014 at 11:03:14PM +0100, Stefan Agner wrote:
>> Hi all,
>>
>> While working on Vybrid (vf610) Cortex-M4 support I also hit this crash
>> observed by Joachim:
>>
>> ...
>> Freeing unused kernel memory: 16K (8800a000 - 8800e000)
>>
>> Unhandled exception: IPSR = 00000005 LR = fffffff1
>> CPU: 0 PID: 1 Comm: swapper Not tainted 3.18.0-rc1-00041-ga30465a #216
>> task: 8b838000 ti: 8b82a000 task.ti: 8b82a000
>> PC is at flush_thread+0x32/0x40
>> LR is at flush_thread+0x21/0x40
>> pc : [<8f00157a>] lr : [<8f001569>] psr: 4100000b
>> sp : 8b82be20 ip : 00000000 fp : 8b83c000
>> r10: 00000001 r9 : 88018c84 r8 : 8bb85000
>> r7 : 8b838000 r6 : 00000000 r5 : 8bb77400 r4 : 8b82a000
>> r3 : ffff0ff0 r2 : 8b82a000 r1 : 00000000 r0 : 88020354
>> xPSR: 4100000b
>> CPU: 0 PID: 1 Comm: swapper Not tainted 3.18.0-rc1-00041-ga30465a #216
>> [<8f002bc1>] (unwind_backtrace) from [<8f002033>] (show_stack+0xb/0xc)
>> [<8f002033>] (show_stack) from [<8f00265b>] (__invalid_entry+0x4b/0x4c)
>>
>> Can reproduce it on 3.18-rc1, as well as 3.17.
>
> Hmm, I think KUSER_HELPERS needs to depend on MMU. Nathan?
Yes. I'll send a patch today.
prev parent reply other threads:[~2014-11-03 14:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 20:57 Crash on ARM: 8148/1 flush TLS and thumbee register Joachim Eastwood
2014-09-26 21:27 ` Nathan Lynch
2014-11-02 22:03 ` Stefan Agner
2014-11-02 22:14 ` Russell King - ARM Linux
2014-11-03 7:47 ` Uwe Kleine-König
2014-11-03 14:34 ` Nathan Lynch [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=54579282.8030309@mentor.com \
--to=nathan_lynch@mentor.com \
--cc=linux-arm-kernel@lists.infradead.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).