From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Daniel Mack <daniel@zonque.org>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
linux-mtd@lists.infradead.org,
Chris Packham <chris.packham@alliedtelesis.co.nz>
Subject: Re: Trouble with new marvell_nand driver on PXA3xx
Date: Mon, 24 Sep 2018 11:04:33 +0200 [thread overview]
Message-ID: <20180924110433.2cd5fb3a@bbrezillon> (raw)
In-Reply-To: <0e773d54-a2c2-63be-12e3-5da6caabd215@zonque.org>
On Mon, 24 Sep 2018 10:30:47 +0200
Daniel Mack <daniel@zonque.org> wrote:
> >> Interestingly, I can't seem to reproduce the bug with any of the mtd
> >> kernel tests, I've tried all of them, several times, and all succeed. So
> >> a file system test that includes the UBI/UBIFS layers seems to trigger
> >> different things in the driver than the the tests that operate on the
> >> mtd device directly.
> >
> > Looking at the backtrace, it seems to fail on a high PEB num. Are you
> > interfacing with a dual-die chip? Can you share the part number of your
> > chip?
>
> The chip is a NAND01GR3B2BZA which is identified like this during probe:
Okay, so it's definitely not caused by a missing R/B pin on a multi-die
chip (this chip only has one die).
next prev parent reply other threads:[~2018-09-24 9:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 6:45 Trouble with new marvell_nand driver on PXA3xx Daniel Mack
2018-09-24 7:20 ` Miquel Raynal
2018-09-24 8:14 ` Daniel Mack
2018-09-24 19:57 ` Daniel Mack
2018-09-24 8:09 ` Boris Brezillon
2018-09-24 8:30 ` Daniel Mack
2018-09-24 9:04 ` Boris Brezillon [this message]
2018-09-26 21:19 ` Daniel Mack
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=20180924110433.2cd5fb3a@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=daniel@zonque.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.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