Skip to content
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

ROCm: Memory Access Fault in Sampling Mode for Various Events #115

Open
dbarry9 opened this issue Nov 9, 2023 · 0 comments
Open

ROCm: Memory Access Fault in Sampling Mode for Various Events #115

dbarry9 opened this issue Nov 9, 2023 · 0 comments

Comments

@dbarry9
Copy link
Contributor

dbarry9 commented Nov 9, 2023

Some events cause a memory fault, as shown below, when using the papi_command_line utility:

${PAPIDIR}/bin/papi_command_line  "rocm:::TCP_TCC_NC_ATOMIC_REQ_sum:device=0"

This utility lets you add events from the command line interface to see if they work.

Successfully added: rocm:::TCP_TCC_NC_ATOMIC_REQ_sum:device=0

Memory access fault by GPU node-2 (Agent handle: 0x4b18cb0) on address 0x7f38e2247000. Reason: Unknown.
Aborted (core dumped)

and

${PAPIDIR}/bin/papi_command_line  "rocm:::TA_BUSY_avr:device=0"

This utility lets you add events from the command line interface to see if they work.

Successfully added: rocm:::TA_BUSY_avr:device=0

Memory access fault by GPU node-2 (Agent handle: 0x55a0ca0) on address 0x7fdaf23d3000. Reason: Unknown.
Aborted (core dumped)

These memory faults do not occur is intercept mode is enabled via the following:
export ROCP_HSA_INTERCEPT=1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant