From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: Unhandled prefetch abort on mirabox with 3.11-rc7
Date: Tue, 3 Sep 2013 18:14:28 +0200 [thread overview]
Message-ID: <20130903181428.150556af@skate> (raw)
In-Reply-To: <52260977.9090103@leahnim.org>
Dear Jochen De Smet,
On Tue, 03 Sep 2013 12:08:23 -0400, Jochen De Smet wrote:
> >>> Keep on posting the oopses though, there may be a pattern to them.
> Another clue in the heat direction might be that with the rain the last
> few days things seem
> at least a bit better, though it's probably too early to draw
> conclusions. First box's been up
> for 2 days 10 hours now, and the with this oops above 18 hours.
Sorry if those questions have already been posted in the previous
thread. What kind of tests / workload are you running on your Mirabox
to trigger the crash? I might be able to get one or two Mirabox running
here, so I could see if the problem is reproducible.
Also, is this something you're seeing only since 3.11-rc7 ? Is the
kernel originally provided with the Mirabox more stable ? Are earlier
kernel versions (such as 3.10 or earlier) more stable ?
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-09-03 16:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 0:49 Unhandled prefetch abort on mirabox with 3.11-rc7 Jochen De Smet
2013-09-03 10:48 ` Jason Cooper
2013-09-03 15:55 ` Russell King - ARM Linux
2013-09-03 16:08 ` Jochen De Smet
2013-09-03 16:14 ` Thomas Petazzoni [this message]
2013-09-03 17:39 ` Jochen De Smet
2013-09-07 23:18 ` Jochen De Smet
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=20130903181428.150556af@skate \
--to=thomas.petazzoni@free-electrons.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.