On 24/9/2018 8:45 AM, Daniel Mack wrote:
I'm having issues using the new marvell_nand driver on a PXA3xx based platform. My test does a ubiformat on the chip, then creates a volume, mounts it and runs bonnie++ on the file system. After some time (usually less than half a minute), the driver spits out a warning like the one below, and eventually the UBI layer bails out, which leads to a r/o remount and (possibly) file system corruptions.
Okay, I think I figured it out. What happens is that after the controller has been sent a command to process it, it sets the RDY bits before the driver ends up in that marvell_nfc_wait_op(). Enabling the interrupt for RDY does not latch it if the RDY bit already set, so the condition wait times out. IOW, it's a race - the controller is faster than than the driver expects it to be.
I'll send a patch to fix that. With this applied, I wasn't able to reproduce the issue anymore. It could possibly be fixed by other means too, so I'm open for discussions and I can also test other approaches easily. Let me know what you think.
Thanks, Daniel ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/
