From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: 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: Mon, 16 Mar 2015 19:19:00 +0100 [thread overview]
Message-ID: <20150316181900.GA4638@lukather> (raw)
In-Reply-To: <20150217083859.GB26177@linutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1042 bytes --]
Hi,
On Tue, Feb 17, 2015 at 09:38:59AM +0100, Sebastian Andrzej Siewior wrote:
> * Maxime Ripard | 2014-06-13 16:25:06 [+0200]:
>
> >Preemptible hierarchical RCU implementation.
> >NR_IRQS:16 nr_irqs:16 16
> >Unable to handle kernel NULL pointer dereference at virtual address 00000000
> >pgd = c0004000
> >[00000000] *pgd=00000000
> >Internal error: Oops: 5 [#1] PREEMPT ARM
> >Modules linked in:
> >CPU: 0 PID: 0 Comm: swapper Not tainted 3.14.3-rt4+ #11
> >task: c05ecb28 ti: c05e2000 task.ti: c05e2000
> >PC is at wake_up_process+0x8/0x40
> >LR is at kthread_create_on_node+0xb0/0x178
> …
> >Do you know what could be the cause of this, or is this any known issue?
>
> No. This is very early in the boot process. I upgrade the at91's timer
> patches but have no HW to actually check if this is still working.
Do you have a link to these patches?
Maybe we can test them out.
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:[~2015-03-16 18:20 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
2015-02-17 8:38 ` Sebastian Andrzej Siewior
2015-03-16 18:19 ` Maxime Ripard [this message]
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=20150316181900.GA4638@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=bigeasy@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=thomas@free-electrons.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).