Hi Wayne,
Good advice. Actually I already RMA the unit yesterday and waiting for replacement unit. Once I get the replaced unit, I will test drive it to see if any of the previous symptoms still there or not.
great to hear that. Just curious whatâs your nv_tegra_release?
cat /etc/nv_tegra_release
Hi @ynjiun,
The version is exactly the same as previously:
R32 (release), REVISION: 4.3, GCID: 21589087, BOARD: t186ref, EABI: aarch64, DATE: Fri Jun 26 04:34:27 UTC 2020) and the same Jetpack version 4.4.
Cheers
Simon
Hi @simon.glet and @WayneWWW,
I received my replacement unit yesterday. Since then, I already run more than 20+ hours with NoMachine connected (internet test), 4X deepstream_test_3.py with 12 videos each at GPU/CPU temperature around 52C without 600W line conditioner (just plug in to a regular UPS). No hiccup, No self reboot any more!
It is confirmed now my previous unit is faulty.
Thank you for your help.
Cheers
I am using Jetson Xavier AGX and reading 6 cameras at the same time. The phenomenal was similar with this topic. My setup environment was:
- USB Hub in which USB 4G ZTE connected to. (eth1)
- Ethernet port also connect to my PC (eth0)
- Camera board which support 6 camera (IP67 Full HD HDR GMSL2 cameras for Jetson AGX Xavierâ˘)
Step to reproduce:
- Power ON Jetson Xavier, read 6 camera at the same time.
- Make the CPU higher (all 8 cores CPU up to 100% by 8 simple bash command âwhile true; do true; doneâ)
- System come to reboot. (This is also relate to another topic of @ynjiun. In bad day, it reboot after 3-30 mins, but good day it can be two or three hours).
What I saw from these topic of ynjiun was that the issue is because of ethernet network is connected? Was it correct? What was the replacement unit did you replace @ynjiun ?
I received my replacement unit yesterday. Since then, I already run more than 20+ hours with NoMachine connected (internet test),
syslog (3.1 MB)
kern.log (3.0 MB)
Please refer my log for more detail.
Thank you very much for your help.
best regards,
Loc Hoang
Hi @v.lochd,
Even after returning the original unit, I still have the same annoying issue.
There seems to be a firmware bug that you could fix by reading this: AGX Xavier freeze in MAXN mode - #33 by WayneWWW
Just in case you successfully apply it, please let us know.
Thanks
Simon
Hi @simon.glet
Thanks for your help. I applied the patches successfully and run overnight with 100% CPU for all 8 cores, and there is no reboot.
We will try two or three more days to make sure the issue is fixed actually.
Will let you know the result.
Best regards,
Loc Hoang
Glad to know it helped.
Cheers
Simon
Hi @simon.glet ,
Until now the system run OK without reboot. It seems that the patches are correct.
Just one thing, whenever we power ON the system, the Jetson Xavier need may be 3-5 minutes to login, It tried to reboot itself for several times, sometime because of kernel panic, sometime because of some failed task on bootup. Are they expected behavior?
At least, it was not reboot again after it was able to login. Thank you very much for your help.
Best regards.
Loc Hoang
Hi, @v.lochd,
Thanks for the update but now I am curious ⌠You now seem to experience a longer boot time. The time you mention seems on par with my AGX.
From the output of the utility dmesg, do you see any errors?
Thanks
Simon
kern.log (268.1 KB)
dmesg.log (96.3 KB)
Hi @simon.glet ,
The time you mention seems on par with my AGX
So you are saying that 3-5mins is normal booting time right? If so thatâs okay for me.
Btw, I have uploaded kernel log and also output of dmesg. Please refer attached file for more detail.
Basically, I saw a lot of failures in dmesg but actually I am not sure which failure took time. Could you please help me to verify the log is similar with yours?
Best regards.
Loc Hoang
Hi, @v.lochd
From your files, your AGX unit seems to have a wireless mouse USB receiver that seems to confuse the boot sequence.
@linuxdev , do you agree?
If the AGX boots without it, is it quicker and without all these errors?
Cheers
Simon
kern.log (7.1 MB)
dmesg.log (92.2 KB)
Hi @simon.glet ,
If the AGX boots without it, is it quicker and without all these errors?
I did try that way, by disconnecting USB Hub with wireless mouse USB receiver connected to, but It tooks more time to bootup (15+ mins).
The weird thing was that once the system ON, we connect the USB Hub again, the mouse was not detected, then I disconnect it again then reboot happened (over 15 mins more).
Please refer the attached log for more detail.
Please also take note that we did connect USB hub again, and tried reboot by ourself, it took 3-5mins like previous comment.
Any information you want to know, just let me know.
Best regards,
Loc Hoang
Hi @v.lochd,
There seems to be a compatibility issue with your wireless mouse. I would suggest trying a wired mouse.
As for the other errors, they seems to be linked to the camera board. I have never used that hardware extension so I canât help you, sorry.
Cheers
Simon
I see errors, but I couldnât say if this has anything to do with boot sequence. It might or might not, but an error of any kind during boot can have unexpected consequences. There is a kernel error, and there is no definition of how the kernel will function during an error (one driver can affect another driver). Whether it is a hardware or software failure wonât much matter.
Hi @linuxdev,
Thanks for your input.
And yes, my wording was wrong for the âboot sequenceâ.
The errors seem to happen at the hardware discovery step of the boot sequence. That might explain the extra time it takes to complete.
As for the AGX stability after these boot errors, @v.lochd will let us know how well his unit fares.
Cheers
Simon
Thank you very much for your help.
Regarding the stability after finish the booting, with AGX Xavier freeze in MAXN mode - #33 by WayneWWW 's patches, and also with Wireless Mouse USB receiver connected, the system was stable since I didnât face any reboot again.
However, the same patches without Wireless Mouse USB receiver, after finish booting (15+ mins), whenever I plug the receiver again, it cannot be detected, so we cannot verify the stability yet. In any case, the Wireless Mouse is needed for me.
Anyway, for now I will apply the first idea with Wireless Mouse and itâs acceptable for me. In parallel I will try to contact Camera supplier for any error from them.
Again, thanks for your help.
Best regards.
Loc Hoang