[BUG] STM report could not set cpuset when running cgf helloworld sample

[lizhensheng]

Required Info:

• Software Version
  DRIVE OS 6.0.6
• Target OS
  Linux
• SDK Manager Version
  1.9.2.10884
• Host Machine Version
  native Ubuntu Linux 20.04 Host installed with DRIVE OS DOCKER Containers

Describe the bug

STM report could not set cpuset when running cgf helloworld sample.

To Reproduce

# goto target system which is orin devkit
cd ./nv_driveworks_demo/target/aarch64/install/example/dwcgf_helloworld/bin/
sudo ./run_cgf.sh

Expected behavior

Actual behavior

launcher.log, which is in here nv_driveworks_demo/launcher.log at 4a790d93544bee5b60306cc7697b3b6e9a90c546 · ZhenshengLee/nv_driveworks_demo · GitHub

[STM WARNING]:[av/stm/runtime/src/client/thread.c][stmStart] [398]: Could not set cpuset, setCpuset returned an error. errno=2 (No such file or directory)

Additional context

the sample work well with this warning.

[SivaRamaKrishnaNV]

Dear @lizhensheng,
Sample work well means, it exits with code ‘0’? Do you see prints from helloworld node in log?

[lizhensheng]

@SivaRamaKrishnaNV

Sample work well means, it exits with code ‘0’? Do you see prints from helloworld node in log?

@SivaRamaKrishnaNV

you can check helloworld node logs in nv_driveworks_demo/launcher.log at main · ZhenshengLee/nv_driveworks_demo (github.com)

there is also cpu related warnings in helloworld node logs.

ZhenshengLee/nv_driveworks_demo/blob/05c3d815915a221ea4ada1e90876b0b10550c76a/doc/tutorial/dwcgf/helloworld/LogFolder/helloworld_process0_0.log#L397-L399

But all cpuset related issue doesn’t interrupt the helloworld cgf app.

Thanks.

[lizhensheng]

Friendly ping @SivaRamaKrishnaNV for updates.

[SivaRamaKrishnaNV]

Dear @lizhensheng ,

The [STM WARNING]… Could not set cpuset messages are showing up because STM’s client threads are trying to pin themselves to a specific CPU core when the cpuset files are not present on the board.
This message is non-fatal and indicates that STM’s threads are free running threads and that they are not pinned to a specific CPU core. Does this clarify?