Bug 97961

Summary: radeon: Failed to allocate virtual address for buffer
Product: Mesa Reporter: Vedran Miletić <vedran>
Component: Drivers/Gallium/radeonsiAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED FIXED QA Contact: Default DRI bug account <dri-devel>
Severity: normal    
Priority: medium Keywords: regression
Version: git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Vedran Miletić 2016-09-28 14:30:22 UTC 
On a Kabini system using kernel 4.8-rc8, Mesa and LLVM git, running GROMACS OpenCL example 1536 from [1] results in

radeon: Failed to allocate virtual address for buffer:
radeon:    size      : 4096 bytes
radeon:    alignment : 4096 bytes
radeon:    domains   : 2
radeon:    va        : 0x000000000948b000
radeon: Failed to deallocate virtual address for buffer:
radeon:    size      : 4096 bytes
radeon:    va        : 0x948b000
radeon: Failed to allocate virtual address for buffer:
radeon:    size      : 4096 bytes
radeon:    alignment : 4096 bytes
radeon:    domains   : 2
radeon:    va        : 0x000000000948b000
radeon: Failed to deallocate virtual address for buffer:
radeon:    size      : 4096 bytes
radeon:    va        : 0x948b000

This is one of the larger examples, so it requires more memory than the previous ones. I will test the largest example (3072) soon, and I expect it to crash the same way.

This is a regression. It will be very hard to bisect LLVM and kernel on this machine as it is really slow, but Mesa is likely bisectable. Let me know if it is worth it.

[1] ftp://ftp.gromacs.org/pub/benchmarks/water_GMX50_bare.tar.gz
Comment 1 Vedran Miletić 2016-09-28 14:32:10 UTC 
GROMACS 2016 runs vanilla on Mesa, but it requires LLVM 4.0, matching libclc, and the following patch for Mesa:

[1] https://lists.freedesktop.org/archives/mesa-dev/2016-September/129305.html
Comment 2 Vedran Miletić 2017-01-25 19:43:17 UTC 
I believe this was fixed somewhere along the way, I don't get the error anymore.

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.