From: Paul Burton <paul.burton@mips.com>
To: Aaro Koskinen <aaro.koskinen@iki.fi>
Cc: "linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: MIPS/CI20: BUG: Bad page state
Date: Wed, 24 Apr 2019 19:29:29 +0000 [thread overview]
Message-ID: <20190424192922.ilnn3oxc7ryzhd3l@pburton-laptop> (raw)
In-Reply-To: <20190424182012.GA21072@darkstar.musicnaut.iki.fi>
Hi Aaro,
On Wed, Apr 24, 2019 at 09:20:12PM +0300, Aaro Koskinen wrote:
> I have been trying to get GCC bootstrap to pass on CI20 board, but it
> seems to always crash. Today, I finally got around connecting the serial
> console to see why, and it logged the below BUG.
>
> I wonder if this is an actual bug, or is the hardware faulty?
>
> FWIW, this is 32-bit board with 1 GB RAM. The rootfs is on MMC, as well
> as 2 GB + 2 GB swap files.
>
> Kernel config is at the end of the mail.
I'd bet on memory corruption, though not necessarily faulty hardware.
Unfortunately memory corruption on Ci20 boards isn't uncommon... Someone
did make some tweaks to memory timings configured in the DDR controller
which improved things for them a while ago:
https://github.com/MIPS/CI20_u-boot/pull/18
Would you be up for testing with those tweaks? I'd be happy to help with
updating U-Boot if needed.
Do you know which board revision you have? (Is it square or a funny
shape, green or purple, and does it have a revision number printed on
the silkscreen?)
Thanks,
Paul
next prev parent reply other threads:[~2019-04-24 19:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 18:20 Aaro Koskinen
2019-04-24 19:18 ` Matthew Wilcox
2019-04-24 19:29 ` Paul Burton [this message]
2019-04-24 20:40 ` Aaro Koskinen
2019-04-24 20:50 ` Paul Burton
2019-05-28 23:37 ` Aaro Koskinen
2019-05-30 23:23 ` Aaro Koskinen
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=20190424192922.ilnn3oxc7ryzhd3l@pburton-laptop \
--to=paul.burton@mips.com \
--cc=aaro.koskinen@iki.fi \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mm@kvack.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