Bug 104604 - [amdgpu/radeon][regression, CIK] Prefetch the compute shader to TC L2 (4a4ff66dbe) causes GPU VM errors when running OpenCL kernels on Hawaii
Summary: [amdgpu/radeon][regression, CIK] Prefetch the compute shader to TC L2 (4a4ff6...
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/radeonsi (show other bugs)
Version: 17.1
Hardware: All All
: medium critical
Assignee: Default DRI bug account
QA Contact: Default DRI bug account
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 99553
  Show dependency treegraph
 
Reported: 2018-01-12 16:25 UTC by Vedran Miletić
Modified: 2019-09-25 18:02 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Vedran Miletić 2018-01-12 16:25:21 UTC
Commit 4a4ff66dbe radeonsi: also prefetch compute shaders enabled prefetching the compute shader to TC L2 for CIK+. This causes GPU VM errors on Hawaii, Kabini, and likely other CIK GPUs when running certain OpenCL programs (it seems that the key is to call clCreateContext() twice or more, see below) with Clover, both with amdgpu and radeon kernel drivers. I have tested with

01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii XT GL [FirePro W9100] [1002:67a0]

on Fedora rawhide (28) with kernel 4.15.0-0.rc7.git2.1.fc28.x86_64.

I'll minimize the example program that causes this (right now using GROMACS tests, but that's unnecessarily complex), and provide the details (grepped + full dmesg) in the comments for both amdgpu and radeon kernel drivers.
Comment 1 GitLab Migration User 2019-09-25 18:02:28 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1300.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.