-
Notifications
You must be signed in to change notification settings - Fork 32
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
Rocminfo Fails #38
Comments
Sounds like an installation or configuration problem. Can you post dmesg output and "ls -l /dev/kfd" for a start? |
The problem is permission to access the device driver interface file as indicated here "Unable to open /dev/kfd". The permissions /group membership needed depends on your specific environment. Running 'ls -l /dev/kfd' will show the owning group and it's permissions. Ensure that you are a member of that group. |
This is the output of 'ls -l /dev/kfd'. When I run tensorflow I get this error. |
That looks like HIP is not installed. Did you install the complete set of rocm packages? What is in /opt/rocm/lib and /opt/rocm/bin? |
Yes I did installed. this are files in /opt/rocm/lib
/opt/rocm/bin
|
Hello, I ran into the same problem using the rocm/dev-ubuntu-18.04 docker image inside a CI machine. It took me quite a bit of digging to find this because I noticed another thing, though I'm not sure where to report this:
|
@BemusedCat @zyzzyxdonta Apologies for the lack of response. Can you please test with the latest ROCm 6.2? If issue is resolved, please close the ticket. Thanks! |
@BemusedCat @zyzzyxdonta Closing ticket. Please re-open the ticket if you still encounter the same issue with the latest ROCm. Thanks! |
I tried everything to run rocm-tensorflow but unable to do so .
Tried everything but nothing works
My rocminfo
ROCk module is loaded
Unable to open /dev/kfd read-write: Bad address
abhigyan is member of render group
hsa api call failure at: /src/rocminfo/rocminfo.cc:1142
Call returned HSA_STATUS_ERROR_OUT_OF_RESOURCES: The runtime failed to allocate the necessary resources. This error may also occur when the core runtime library needs to spawn threads or create internal OS-specific events.
`
The text was updated successfully, but these errors were encountered: