-
Notifications
You must be signed in to change notification settings - Fork 362
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Q: are these dmesg messages expected? #343
Comments
These messages are normal. The evicting/restoring messages are a bit verbose, and we could probably turn them into debug messages that aren't printed in the log by default. The "Failed to get user pages" happens if userptr memory is freed while it's still mapped for GPU access. This can result from an optimization in the OpenCL runtime that tries to keep user pages mapped to avoid repeatedly mapping and unmapping them unnecessarily. These messages aren't a problem as long as the GPU doesn't try to access this invalid memory mapping. Again, this could probably be turned into debug messages. |
Thanks! I was sort of guessing they are benign, because everything seemed to function correctly when they were present. Closing then. |
Yep, the AMD driver is too chatty, Ubuntu kernel 5.2.7-050207-lowlatency + rocm-opencl 1.2.0-2019070446. Every time I'm running OpenCL examples I'm getting this in kernel logs:
They should present in debug builds |
During normal usage, especially if jobs are started and stopped in rapid succession, the kernel log is filled with messages like this: [38732.522910] Restoring PASID 0x8003 queues [38732.666767] Evicting PASID 0x8003 queues [38732.714074] Restoring PASID 0x8003 queues [38732.815633] Evicting PASID 0x8003 queues [38732.834961] Restoring PASID 0x8003 queues [38732.840536] Evicting PASID 0x8003 queues [38732.869846] Restoring PASID 0x8003 queues [38732.893655] Evicting PASID 0x8003 queues [38732.927975] Restoring PASID 0x8003 queues According to [1], these messages are expected, but they carry little value for the end user, so turn them into debug messages. [1] ROCm/ROCm#343 Signed-off-by: Julian Sax <jsbc@gmx.de>
Ubuntu 17.10, ROCm 1.7, Vega64
When I run my OpenCL app, I see plenty of such entries appearing in dmesg. Are these normal/expected and nothing to worry about, or do they signal some problem?
The text was updated successfully, but these errors were encountered: