linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Aaro Koskinen <aaro.koskinen@iki.fi>
To: Paul Burton <paul.burton@mips.com>
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, 29 May 2019 02:37:15 +0300	[thread overview]
Message-ID: <20190528233715.GB24195@darkstar.musicnaut.iki.fi> (raw)
In-Reply-To: <20190424205016.yqtrlygqojii2rs6@pburton-laptop>

Hi,

On Wed, Apr 24, 2019 at 08:50:31PM +0000, Paul Burton wrote:
> On Wed, Apr 24, 2019 at 11:40:55PM +0300, Aaro Koskinen wrote:
> > On Wed, Apr 24, 2019 at 07:29:29PM +0000, Paul Burton wrote:
> > > 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.

I did some testing with CI20_u-boot ef995a1611f0, plus the timing fix
cherry picked. Didn't help, I still get random crashes (every time
different).

> > It's a purple one. Based on quick look all printings are identical to this
> > one:
> > https://images.anandtech.com/doci/8958/purple%20ci20_smaller_678x452.jpg
> 
> OK good to know - so it's a revision B board, which changed from Hynix
> to Samsung DDR:
> 
>   https://elinux.org/CI20_Hardware#Board_Revisions_and_changes
> 
> That's also the revision Gabriele who submitted the U-Boot pull request
> linked above has.

When checking the serial console with the original U-boot on NAND,
it prints:

	U-Boot SPL 2013.10-rc3-gb2e1fea (Dec 24 2014 - 10:24:52)
	SDRAM H5TQ2G83CFR initialization... done

That would suggest Hynix memory? But when checking the small print on
the chips, they clearly say K4B2G0846Q. The new U-Boot prints (for some
reason SPL printouts are missing):

	U-Boot 2013.10-rc3-g54c6a4817 (May 25 2019 - 14:37:07)

	Board: ci20 (r1) (Ingenic XBurst JZ4780 SoC)

So looks like both old and new U-boot are misdetecting the board as r1
board, and then probably using the wrong timings?

A.


  reply	other threads:[~2019-05-28 23:37 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
2019-04-24 20:40   ` Aaro Koskinen
2019-04-24 20:50     ` Paul Burton
2019-05-28 23:37       ` Aaro Koskinen [this message]
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=20190528233715.GB24195@darkstar.musicnaut.iki.fi \
    --to=aaro.koskinen@iki.fi \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=paul.burton@mips.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