Starting DRIVE AGX takes more than 5 minutes

Autonomous Vehicles DRIVE AGX Xavier DRIVE AGX Xavier General
1

Hi,

I have some problem of booting DRIVE AGX.
Turn on the DRIVE AGX power,
Linux on XavierB boots soon. We are able to use Linux GUI soon.
But Booting Linux on XavierA takes more than 5 minutes and GUI is not available during booting.

Syslog shows continuiously start and stop RoadRunner daemon.
I think RoadRunner might have some problem.
Could you tell me the cause or confirmation points?

excerpt of syslog

Sep 21 10:03:12 tegra-ubuntu systemd[1]: Started RoadRunner daemon service.
Sep 21 10:03:13 tegra-ubuntu systemd[1]: rr-launch.service: Main process exited, code=exited, status=255/n/a
Sep 21 10:03:13 tegra-ubuntu systemd[1]: rr-launch.service: Failed with result ‘exit-code’.
Sep 21 10:03:18 tegra-ubuntu systemd[1]: rr-launch.service: Service hold-off time over, scheduling restart.
Sep 21 10:03:18 tegra-ubuntu systemd[1]: rr-launch.service: Scheduled restart job, restart counter is at 41.
Sep 21 10:03:18 tegra-ubuntu systemd[1]: Stopped RoadRunner daemon service.
Sep 21 10:03:18 tegra-ubuntu systemd[1]: Started RoadRunner daemon service.
Sep 21 10:03:18 tegra-ubuntu systemd[1]: rr-launch.service: Main process exited, code=exited, status=255/n/a
Sep 21 10:03:18 tegra-ubuntu systemd[1]: rr-launch.service: Failed with result ‘exit-code’.
Sep 21 10:03:23 tegra-ubuntu systemd[1]: rr-launch.service: Service hold-off time over, scheduling restart.
Sep 21 10:03:23 tegra-ubuntu systemd[1]: rr-launch.service: Scheduled restart job, restart counter is at 42.
Sep 21 10:03:23 tegra-ubuntu systemd[1]: Stopped RoadRunner daemon service.
Sep 21 10:03:23 tegra-ubuntu systemd[1]: Started RoadRunner daemon service.
Sep 21 10:03:23 tegra-ubuntu dhclient[600]: DHCPDISCOVER on enP4p1s0 to 255.255.255.255 port 67 interval 18 (xid=0x6fbe0168)
Sep 21 10:03:23 tegra-ubuntu sh[573]: DHCPDISCOVER on enP4p1s0 to 255.255.255.255 port 67 interval 18 (xid=0x6fbe0168)
Sep 21 10:03:24 tegra-ubuntu systemd[1]: rr-launch.service: Main process exited, code=exited, status=255/n/a
Sep 21 10:03:24 tegra-ubuntu systemd[1]: rr-launch.service: Failed with result ‘exit-code’.
Sep 21 10:03:29 tegra-ubuntu systemd[1]: rr-launch.service: Service hold-off time over, scheduling restart.
Sep 21 10:03:29 tegra-ubuntu systemd[1]: rr-launch.service: Scheduled restart job, restart counter is at 43.
Sep 21 10:03:29 tegra-ubuntu systemd[1]: Stopped RoadRunner daemon service.
Sep 21 10:03:29 tegra-ubuntu systemd[1]: Started RoadRunner daemon service.
Sep 21 10:03:29 tegra-ubuntu systemd[1]: rr-launch.service: Main process exited, code=exited, status=255/n/a
Sep 21 10:03:29 tegra-ubuntu systemd[1]: rr-launch.service: Failed with result ‘exit-code’.
Sep 21 10:03:34 tegra-ubuntu systemd[1]: rr-launch.service: Service hold-off time over, scheduling restart.
Sep 21 10:03:34 tegra-ubuntu systemd[1]: rr-launch.service: Scheduled restart job, restart counter is at 44.
Sep 21 10:03:34 tegra-ubuntu systemd[1]: Stopped RoadRunner daemon service.
Sep 21 10:03:34 tegra-ubuntu systemd[1]: Started RoadRunner daemon service.
Sep 21 10:03:35 tegra-ubuntu systemd[1]: rr-launch.service: Main process exited, code=exited, status=255/n/a
Sep 21 10:03:35 tegra-ubuntu systemd[1]: rr-launch.service: Failed with result ‘exit-code’.
Sep 21 10:03:40 tegra-ubuntu systemd[1]: rr-launch.service: Service hold-off time over, scheduling restart.
Sep 21 10:03:40 tegra-ubuntu systemd[1]: rr-launch.service: Scheduled restart job, restart counter is at 45.
Sep 21 10:03:40 tegra-ubuntu systemd[1]: Stopped RoadRunner daemon service.

Please provide the following info:
**Hardware Platform:DRIVE AGX Xavier™ Developer Kit
**Software Version: DRIVE Software 10
**Host Machine Version:native Ubuntu 18.04
**SDK Manager Version:1.0.1.5538

2

Dear @Takamitsu.Kano,
Do you see this issue since begining after flashing DS10? Is it possible to check flashing again?

4

Hi SivaRamaKrishnaNV,

No. I flashed DRIVE AGX last December.
the problem of start DRIVE AGX occured from the end of July.
I hope to avoid to flash DRIVE AGX because of big impact to our development.
Is it difficult?

5

Dear @Takamitsu.Kano,
The issue could go away after re-flashing. It is difficult to comment on issue which are not reproducible on our system.