I checked it. On cold boot, it detects sdcard as UHS, but after software reset the same sdcard is detected as HS then I remove and replug the sdcard and it is registered as UHS again.
I think that is a problem but is this a cause of the main problem or another sdmmc problem?
When the card is running in UHS, could you check if this error happens?
Also, could you dump the iozone result with us? Please mount your sd on /mnt and share the result with us.
During this test, please check card is under UHS mode.
Did you try exFAT with hung task panic enabled? Based on what we have here, exFat and ext4 tests were tried with disabled reset panic.
Will iozone still work if the card is in HS mode?
If vmmc-always-on and patch skipping CMD11 are present in the your build, the card is still enumerating in HS mode, This is something we need to debug. Though, it is always recommended to have power cycling support for the SD slot supply. Actually, the latest design guide on NX and NANO both show the GPIO for SDMMC_VDD_EN.
Yes, I tried. Everything is the same for both filesystem on every test for now.
Speed decreased but there is no other problem when using iozone, output attached. iozone_when_HSmode.txt (2.1 KB)
I had turned off that patch for a while, now I reapplied that patch and HS mode issue solved. It is registered as UHS mode on soft and hard reset. But our main issue continue, It resets. Also, there is another print shows up and spamming when I unplug the sdcard. Print is: sdhci-tegra sdhci-tegra.2: Tuning done, restoring the best tap value : 32
I don’t really get the issue of “card reset again” here. You should apply this configuration and try to write big size data to your card and see if kernel panic is still there. Also, in this test, please remember to enable hung task panic timeout.
I had turned off that patch for a while, now I reapplied that patch and HS mode issue solved . It is registered as UHS mode on soft and hard reset.
It sounds you didn’t apply the patch correctly last time.
Actually I didn’t understand :). I made those changes and enabled the hung task panic(mean OS will reset if hung) then I wrote big chunk of data and process hung after 120 second. Because of that OS triggered software reset. Isn’t that normal? Please, correct me if I am wrong.
After the patch applied, I tried the same process again. Please, check the console output attached below.
I removed the applied patch when I open this topic because I thought it wasn’t necessary. Now we have that patch too.
This time I added that argument too, check the output.
Actually I didn’t understand :). I made those changes and enabled the hung task panic(mean OS will reset if hung) then I wrote big chunk of data and process hung after 120 second. Because of that OS triggered software reset. Isn’t that normal? Please, correct me if I am wrong.
Never mind. Actually I was just not able to get your meaning of “card reset again”. It is just kernel panic here.
Wayne, we test out our carrier board with XavierNx module and we didn’t see any problem as nano has. Is there any patch that Nx kernel has but Nano kernel don’t have.
Just the patch and status “okay” on dts. But Nx without patch configuration also tested and there is no kernel panic. The patch only solved that UHS - HS problem.