Long running kernels / GPU watchdog timeout

Robotics & Edge Computing Jetson & Embedded Systems Jetson Nano
1

New to CUDA under Windows, I soon came across the run-time limits on kernels, & the reg edit workarounds to increase the timeout there.

Now new to CUDA under Linux, when porting that code to L4T on the nano, I quickly realised I might be hitting a similar restriction. I’m guessing it’s this, as reducing the kernel workload / iterations per kernel makes things run as expected. But rather than exit with an error as it does under windows, my code seems to hang at the point where the kernel workload has exceeded the imagined limit.

Two questions:

  1. Is the hung code (L4T) v early exit (windows) the correct symptom re too long a kernel run time?
  2. Googling seems to indicate no way under linux/L4T to increase the timeout - correct?

Thanks, Dave.

2

This is a quite old post (this was for TK1) and I haven’t been dealing with such case since then, but there was a time where this might have some relevance for your case. However I can’t tell what would be the sysfs path if any for Nano.