Hi Nvidia:
We are using IGX Orin + IGX OS 1.0.3. However, an abnormal behavior after login were discovered during our test.
These two videos were recorded to show the abnormal behavior. As you can see, after login, we are not able to use mouse to click any things nor using touch screen to click any things.
We use SOL to get the logs, as attached file here: Round 23 .txt (27.7 KB)
The last thing captured were cloud-init Used fallback datasource, as the title saying.
For now, we use sudo touch /etc/cloud/cloud-init.disabled to disable it. We are still testing if this can be a workaround.
Is this a safe way to avoid the issue? What does cloud-init do here?
Exactly. Once we login via console, IGX Orin works like charm.
Precisely, this issue sometimes fix by itself. Means we don’t have to do any thing, and the system went normal. But if the system can’t get it back, it will kick us back to login screen, as shown in the video:
And sorry, we didn’t get the log when it happened. It was the first time we encounter this issue and thus didn’t try to get any of logs.
If we login via console, the system would be normal immediately.
To reproduce the issue, we just kept reboot and reboot. Fail rate is around 3/40. What’s more, after 20 times, the fail rate will raise.
As you can see, we used two different monitor connected to IGX Orin.
The first one is a common monitor. It’s connect to A6000 via DP cable. When the issue happened, mouse clicking does nothing for left nor right clicking.
The second one is a touch screen. It’s connect from A6000 --DP–> DP to HDMI converter --HDMI–> touch screen.
The touch signal is transmitting via USB.
Sorry, we don’t have IGX developer kit, hence we can’t reproduce the issue on it.
As the name of file saying, normalSysLog.txt stands for normal behavior. Nothing bad happened and system run perfectly.
kickoutSyslog.txt stands for abnormal behavior. System kick me out after a few seconds.
“System Kick out” means kick user back to login session, as the video shown.
When the issue happened, the log will show “clound-init used fallback datasource”, as the title said. At the same time, both of mentioned situation will happen.
Our workaround is to disable cloud-init service. We want to make sure that disabling cloud-init would be fine.
So far, our system seems OK after disabling cloud-init service. I think this can be marked as the solution?