-
Notifications
You must be signed in to change notification settings - Fork 56
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
[Issue]: Adding -O0 causes HIP error: the operation cannot be performed in the present state #126
Comments
I think this might be a compiler issue. But just to be sure, can you share the logs by setting the environment variable: |
|
Ohh:
I think you might need to enable largebar. It should be in your bios, something like |
resize bar is on + doesn't explain why optimization is affecting this? |
I think, due to inclusion of hip_assert.h header which has hostcall prints in functions like |
More issues - this time failing tests without any error:
|
I think the issue is the same, with -O0, the lingering __assert_fail which requires host call prints, which rely on PCI-e atomics (which are disabled on the system). So if you check the results with |
Ok yeah I can confirm that atomics are disabled - this is a BIOS setting, correct? |
I think so, its mostly system configuration setting. But I guess that does not apply to you. You might need to look up your motherboard bios settings. |
Resize bar is enabled and I don't see anything about atomics. Kernel setting perhaps? My os does report it as off
Sent from Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: Jatin Chaudhary ***@***.***>
Sent: Thursday, January 23, 2025 2:00:26 PM
To: ROCm/clr ***@***.***>
Cc: Paulius Velesko ***@***.***>; Author ***@***.***>
Subject: Re: [ROCm/clr] [Issue]: Adding -O0 causes HIP error: the operation cannot be performed in the present state (Issue #126)
I think so, its mostly system configuration setting.
There is one mentioned for a server class system here: https://rocm.docs.amd.com/en/docs-6.0.0/conceptual/More-about-how-ROCm-uses-PCIe-Atomics.html#bar-memory-overview
But I guess that does not apply to you. You might need to look up your motherboard bios settings.
—
Reply to this email directly, view it on GitHub<#126 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACCJBQOWOMW5CI4POJQGOGL2MDKVVAVCNFSM6AAAAABVGUZJICVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBZGYZDQNRZGM>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Problem Description
Source code:
Operating System
Ubuntu 22.04
CPU
Intel i9
GPU
Vega 20
ROCm Version
ROCm 6.3.0
ROCm Component
No response
Steps to Reproduce
No response
(Optional for Linux users) Output of /opt/rocm/bin/rocminfo --support
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: