All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Brian Norris <computersforpeace@gmail.com>,
	Kamal Dasu <kdasu.kdev@gmail.com>,
	Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	MTD Maling List <linux-mtd@lists.infradead.org>,
	BCM Kernel Feedback <bcm-kernel-feedback-list@broadcom.com>,
	Florian Fainelli <f.fainelli@gmail.com>
Subject: Re: ECC errors after UBI writes with brcmnand (Northstar with v6.1 controller)
Date: Wed, 23 Mar 2022 16:48:00 +0100	[thread overview]
Message-ID: <20220323164800.508c6b0f@xps13> (raw)
In-Reply-To: <2dd15b13-8861-c5b7-b601-890635377c91@gmail.com>

Hi Rafał,

zajec5@gmail.com wrote on Wed, 23 Mar 2022 16:33:48 +0100:

> On 22.03.2022 18:53, Rafał Miłecki wrote:
> > On 18.03.2022 19:02, Rafał Miłecki wrote:  
> >> My problem is that ubifs complains about ECC errors. I spent some time
> >> debugging it and it seems that:
> >> 1. Initially all blocks written by bootloader can be read fine
> >> 2. Few blocks written by ubifs -> ubi -> brcmnand can't be read back

Do you write and read with U-boot or Linux only ? There is either a
regression (maybe look at the different commits on this driver since
last version it worked?) or if you U-boot to write and Linux to read
maybe there is an ECC mismatch because of a core regression when
parsing the DT, or a difference of configuration.

A few ideas... But there is nothing obvious.

Thanks,
Miquèl

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2022-03-23 15:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-18 18:02 ECC errors after UBI writes with brcmnand (Northstar with v6.1 controller) Rafał Miłecki
2022-03-22 17:53 ` Rafał Miłecki
2022-03-23 15:33   ` Rafał Miłecki
2022-03-23 15:48     ` Miquel Raynal [this message]
2022-03-24 16:49 ` Rafał Miłecki

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=20220323164800.508c6b0f@xps13 \
    --to=miquel.raynal@bootlin.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=computersforpeace@gmail.com \
    --cc=f.fainelli@gmail.com \
    --cc=kdasu.kdev@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard@nod.at \
    --cc=vigneshr@ti.com \
    --cc=zajec5@gmail.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 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.