From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: "external abort on linefetch (0x814)" on Kirkwood 6282 SoC
Date: Wed, 26 Jul 2017 17:22:51 +0200 [thread overview]
Message-ID: <20170726152251.GE12049@lunn.ch> (raw)
In-Reply-To: <1500801941.22097.24.camel@hellion.org.uk>
On Sun, Jul 23, 2017 at 10:25:41AM +0100, Ian Campbell wrote:
> Hello kirkwood folks,
>
> We have been seeing reports on the Debian arm list about
> instability/errors running Debian Stretch (4.9 based) on
> various?Kirkwood 6282 based QNAP systems. Errors are things like [0,
> actually one of the earlier pre-4.9 reports, same symptoms as with 4.9
> though]:
>
> [???37.167103] BUG: Bad rss-counter state mm:c0caa1e0 idx:1 val:1
> [??783.570365] BUG: Bad rss-counter state mm:c09e6220 idx:1 val:1
> [??800.172223] BUG: Bad rss-counter state mm:ecbc05e0 idx:1 val:1
> [??829.005336] BUG: Bad rss-counter state mm:c0d4b880 idx:1 val:1
> [??871.773956] BUG: Bad rss-counter state mm:c09e63c0 idx:1 val:1
> [ 1299.565344] BUG: Bad rss-counter state mm:ecaf8c40 idx:1 val:1
>
> and
>
> [???71.033784] Unhandled fault: external abort on linefetch (0x014) at 0xb6c73db0
> [???71.041037] pgd = ead9c000
> [???71.043747] [b6c73db0] *pgd=3fd72831
> [???84.144056] Unhandled fault: external abort on linefetch (0x014) at 0xb6d44db0
> [...]
Hi Ian
I have a 6282 system i can try to reproduce this on. It will probably
be a few days before i get around to it.
Andrew
next parent reply other threads:[~2017-07-26 15:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1500801941.22097.24.camel@hellion.org.uk>
2017-07-26 15:22 ` Andrew Lunn [this message]
2017-07-26 16:18 ` "external abort on linefetch (0x814)" on Kirkwood 6282 SoC Ian Campbell
2017-07-26 17:55 ` Andrew Lunn
2017-07-26 18:40 ` Ian Campbell
2017-07-28 16:33 ` Andrew Lunn
2017-07-29 15:50 ` Andrew Lunn
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=20170726152251.GE12049@lunn.ch \
--to=andrew@lunn.ch \
--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).