-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linux 5.18 kernel unable to read from NAND on i.MX6Q phycore SOM #12
Comments
Thanks for the report! We will have a look at the issue. |
In the mean time I switched back to LTS 5.15 and I am now also experiencing the same issue on 5.15.48 kernel. After investigating and reverting only commit mtd: rawnand: gpmi: fix controller timings setting, the NAND issue was solved. Coincidentally I just stumbled on https://lore.kernel.org/linux-mtd/20220614083138.3455683-1-s.hauer@pengutronix.de/ which I assume will fix the issue (still need to test). I see that commit has just been added to kernels 5.15.51 and 5.18.8 so I think from those kernels on, the phycore i.MX6 NAND SOM will boot again. |
We can reproduce the issue with the 5.15 upstream kernel. |
After doing some additional testing I can confirm your observations. In fact, the issue I encounter is that mounting another ubifs volume fails:
Mounting the rootfs (also ubifs) does work though (after applying "mtd: rawnand: gpmi: Fix setting busy timeout setting") but there is indeed still something going on :( Above issues where not encountered in 5.15.32. |
The Error is reported upstream and will be fixed by Sascha Hauer: |
Hi,
I recently updated the Linux kernel (linux-fslc) on our i.MX6Q phycore SOM to version 5.18 and I encounter some issues. More specifically in the bootlog I see there are no bad block tables found anymore. When comparing to the bootlog of a 5.15 kernel, here are the differences:
I tested the above on 2 devices and both had the same issue so I don't think it's device specific. Also, barebox is still able to read from NAND so the flash is not broken or anything.
With kernel 5.18, after a "failed" boot, barebox also starts to complain about bad block tables not being found:
so for both reading/writing from/to nand, it looks like the 5.18 kernel is doing something but it's having issues.
Could somebody try the 5.18 kernel on a i.MX6Q phycore SOM with NAND and confirm the above issue or is it maybe an issue on our side (incorrect device tree)?
The text was updated successfully, but these errors were encountered: