Hi,
I have a problem with jetson nano’s Sdmmc interface. About development environment:
I use Jetson Nano Production Module(P3448 rev.B01)
Baseboard is own production. (We use Emmc for Jetpack Image, Sdmmc Interface for extra storage).
JetPack 4.3 with kernel 4.9.
I tried different brands and models of sd cards.
The problem is when I try to write big chunks of data to sd card(with UI or dd command) the kernel hung and reset the board with the error below. Smaller data writes (less than 120 seconds) gives no error.
I attached dmesg output and dts file below. Also we produce dtsi file based on these nvidia topics.(Latest dts which I attached could not include all patches below but I tried all of them with different combinations.)
I applied your patch which you post on this post and added nvidia,vmmc-always-on; to tegra210-sdhci.dtsi (Also removed min,max tap delays according to this).
New live dmesg output attached. I copied that from the console so it’s a bit messy but error is the same as the question post.
I think that reset broke filesystem on the sd card(Not sure). After recreating filesystem that error went away.
In your first log here, there is no crc error from mmc1. Actually, this is a perfect boot up log. Why do you say error is still the same? You didn’t capture the error part here.
New live dmesg output attached. I copied that from the console so it’s a bit messy but error is the same as the question post.
This time I saw the kernel panic but I don’t see any error from sdcard driver. Could you remove the “quiet” keyword from extlinux.conf to enable more log from serial console?
I applied debug patch and attached new dmesg.
Also, could you still put the rootfs on emmc first, mount sdcard after boot up and then write big chunk data? Want to see if you have error in this case.
That was my fault; log on the #4 post is old, you are right. So forget that log. The error I mean was that the kernel panic.
I am using dmesg so quiet won’t affect anything but I added debug to bootargs. Attached new log(log1) with debug messages. But again there is no driver debug print when the kernel panic appears.
Attached error log(log2). Again kernel panic occurred. Seems same with log1.
If the issue is still seen, can you help check if the following commands help
sudo sysctl -w vm.dirty_ratio=50
sudo sysctl -w vm.dirty_background_ratio=5
sudo sysctl -p
Verify that above changes are reflected in the system using sudo sysctl -a | grep dirty and write large data the card.
Ensure that all the write tests are run with hung task timeouts enabled.