| Bug ID | 102595 |
|---|---|
| Summary | clpeak |
| Product | Mesa |
| Version | git |
| Hardware | x86-64 (AMD64) |
| OS | Linux (All) |
| Status | NEW |
| Severity | normal |
| Priority | medium |
| Component | Drivers/Gallium/r600 |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | benjiwiebe14@gmail.com |
| QA Contact | dri-devel@lists.freedesktop.org |
When I run 'clpeak --global-bandwidth' I get:
[benji@benji-pc clpeak]$ ./clpeak --global-bandwidth
Platform: Clover
Device: AMD CAYMAN (DRM 2.50.0 / 4.13.0+, LLVM 6.0.0)
Driver version : 17.3.0-devel (Linux x64)
Compute units : 12
Clock frequency : 880 MHz
Global memory bandwidth (GBPS)
float : radeon: Failed to allocate a buffer:
radeon: size : 1073741824 bytes
radeon: alignment : 4096 bytes
radeon: domains : 4
radeon: flags : 4
radeon: Failed to allocate a buffer:
radeon: size : 1073741824 bytes
radeon: alignment : 4096 bytes
radeon: domains : 4
radeon: flags : 4
Segmentation fault (core dumped)
And in dmesg:
[55959.960796] clpeak[16731]: segfault at 1c ip 00007f3d77e5a42a sp
00007fff93152570 error 4 in pipe_r600.so[7f3d77d53000+1c2000]
The clpeak compute-* and kernel-latency tests work fine, and transfer-bandw=
idth
fails with a (I believe) unrelated error message, seemingly due to me runni=
ng
Linux-git.
Created attachment 134=
057 [details]
Stack trace from coredump
| What | Removed | Added |
|---|---|---|
| Blocks | 99553 |
New backtrace with debugging turned on. It appears that the is= sue is a NULL pointer dereference in r600_resource_copy_region (dst). In compute_memory_promote_item, pool->bo is NULL (which is what 'dst' is for r600_resource_copy_region).
Created attachment 134061=
[details]
Better stack trace
| What | Removed | Added |
|---|---|---|
| Summary | clpeak | [clover r600g cayman] segfault when running clpeak --global-= bandwidth |
| What | Removed | Added |
|---|---|---|
| Resolution | --- | MOVED |
| Status | NEW | RESOLVED |
-- 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/610.