On Fri, 9 Oct 2020 at 19:24, Naresh Kamboju [off-list ref] wrote:

On Thu, 24 Sep 2020 at 15:26, Joerg Roedel [off-list ref] wrote:

quoted

On Thu, Sep 24, 2020 at 10:36:47AM +0100, Robin Murphy wrote:

quoted

Yes, the issue was introduced by one of the changes in "dma-mapping:
introduce DMA range map, supplanting dma_pfn_offset", so it only existed in
the dma-mapping/for-next branch anyway.

FYI,
The reported problem still exists on 5.9.0-rc8-next-20201009.

[    1.843814] Driver must set ecc.strength when using hardware ECC
[    1.849847] WARNING: CPU: 4 PID: 1 at
drivers/mtd/nand/raw/nand_base.c:5687 nand_scan_with_ids+0x1450/0x1470
[    1.859676] Modules linked in:
[    1.862730] CPU: 4 PID: 1 Comm: swapper/0 Not tainted
5.9.0-rc8-next-20201009 #1
[    1.870125] Hardware name: Freescale Layerscape 2088A RDB Board (DT)
[    1.876478] pstate: 40000005 (nZcv daif -PAN -UAO -TCO BTYPE=--)
[    1.882483] pc : nand_scan_with_ids+0x1450/0x1470
[    1.887183] lr : nand_scan_with_ids+0x1450/0x1470

full test log,
https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20201009/testrun/3284876/suite/linux-log-parser/test/check-kernel-warning-92014/log

quoted

Okay, alright then.

- Naresh