Re: [PATCH v4 00/14] Implement exec_op for GPMI nand driver

From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Shawn Guo <shawnguo@kernel.org>, Vinod Koul <vkoul@kernel.org>,
	linux-mtd@lists.infradead.org, NXP Linux Team <linux-imx@nxp.com>,
	kernel@pengutronix.de, Richard Weinberger <richard@nod.at>,
	Han Xu <han.xu@nxp.com>, Fabio Estevam <festevam@gmail.com>
Subject: Re: [PATCH v4 00/14] Implement exec_op for GPMI nand driver
Date: Tue, 21 May 2019 10:33:31 +0200	[thread overview]
Message-ID: <20190521103331.0d788c31@xps13> (raw)
In-Reply-To: <20190521081955.hkl2f7lub3euz43k@pengutronix.de>

Hi Sascha,

Sascha Hauer <s.hauer@pengutronix.de> wrote on Tue, 21 May 2019
10:19:55 +0200:

> On Tue, May 21, 2019 at 09:06:29AM +0200, Sascha Hauer wrote:
> > When rebasing on v5.2-rc1 I observe this backtrace:
> > 
> > [   10.789761] WARNING: CPU: 0 PID: 1 at /ptx/work/WORK_OOGHO/sha/backup/linux/linux/drivers/mtd/nand/raw/internals.h:
> > 114 nand_reset_op+0x194/0x1c4
> > [   10.803137] Modules linked in:
> > [   10.806441] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.2.0-rc1-00014-g793f23e5adb0-dirty #676
> > [   10.815297] Hardware name: Freescale i.MX6 Quad/DualLite (Device Tree)
> > [   10.822054] [<c0112928>] (unwind_backtrace) from [<c010d140>] (show_stack+0x10/0x14)
> > [   10.830054] [<c010d140>] (show_stack) from [<c0bd65cc>] (dump_stack+0xd8/0x110)
> > [   10.837609] [<c0bd65cc>] (dump_stack) from [<c0127148>] (__warn+0xe0/0x10c)
> > [   10.844791] [<c0127148>] (__warn) from [<c0127288>] (warn_slowpath_null+0x3c/0x48)
> > [   10.852604] [<c0127288>] (warn_slowpath_null) from [<c070be50>] (nand_reset_op+0x194/0x1c4)
> > [   10.861207] [<c070be50>] (nand_reset_op) from [<c070db44>] (nand_reset+0x58/0xb4)
> > [   10.868924] [<c070db44>] (nand_reset) from [<c070f454>] (nand_scan_with_ids+0x152c/0x1624)
> > [   10.877444] [<c070f454>] (nand_scan_with_ids) from [<c071a8a8>] (gpmi_nand_probe+0x2f8/0x6ac)
> > [   10.886235] [<c071a8a8>] (gpmi_nand_probe) from [<c067c2cc>] (platform_drv_probe+0x48/0x98)
> > [   10.894844] [<c067c2cc>] (platform_drv_probe) from [<c067a15c>] (really_probe+0xec/0x2c8)
> > [   10.903272] [<c067a15c>] (really_probe) from [<c067a494>] (driver_probe_device+0x5c/0x168)
> > [   10.911781] [<c067a494>] (driver_probe_device) from [<c067a748>] (device_driver_attach+0x58/0x60)
> > [   10.920909] [<c067a748>] (device_driver_attach) from [<c067a7d4>] (__driver_attach+0x84/0xc0)
> > [   10.929684] [<c067a7d4>] (__driver_attach) from [<c06785dc>] (bus_for_each_dev+0x70/0xb4)
> > [   10.938107] [<c06785dc>] (bus_for_each_dev) from [<c06795fc>] (bus_add_driver+0x154/0x1e0)
> > [   10.946615] [<c06795fc>] (bus_add_driver) from [<c067b430>] (driver_register+0x74/0x108)
> > [   10.954952] [<c067b430>] (driver_register) from [<c010317c>] (do_one_initcall+0x80/0x330)
> > [   10.963385] [<c010317c>] (do_one_initcall) from [<c11011a0>] (kernel_init_freeable+0x2e8/0x3cc)
> > [   10.972346] [<c11011a0>] (kernel_init_freeable) from [<c0bf0c60>] (kernel_init+0x8/0x114)
> > [   10.980768] [<c0bf0c60>] (kernel_init) from [<c01010b4>] (ret_from_fork+0x14/0x20)
> > 
> > I also reported this as an answer to the original patch introducing
> > this backtrace here:
> > 
> > http://lists.infradead.org/pipermail/linux-mtd/2019-May/089600.html
> > 
> > No idea what goes wrong here, but in the hope that it's not the fault of this
> > series I'm resending this rebased version anyway.  
> 
> Okay, this goes down to an issue orthogonal to this series. With this:

Great. I'm applying this series to my 0-day repository, will push on
kernel.org repo in a few days.

> 
> http://lists.infradead.org/pipermail/linux-mtd/2019-May/089626.html

Thanks,
Miquèl

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