dmesg |
text/plain
|
2019-02-20 17:30:54 UTC |
256.16 KB |
no flags
|
Details |
yet another dmesg |
text/plain
|
2019-02-20 21:01:21 UTC |
296.81 KB |
no flags
|
Details |
yet another dmesg |
text/plain
|
2019-02-20 21:01:39 UTC |
1.06 MB |
no flags
|
Details |
[drm:amdgpu_ctx_mgr_entity_fini [amdgpu]] *ERROR* - kernel log |
text/plain
|
2019-02-26 10:43:46 UTC |
406.65 KB |
no flags
|
Details |
"suspicious RCU usage" the commits 3741540 and 222b5f0 is reverted |
text/plain
|
2019-02-27 04:25:56 UTC |
132.91 KB |
no flags
|
Details |
"amd-staging-drm-next" + commits 3741540, 222b5f0 and 5936131 is reverted |
text/plain
|
2019-02-28 16:45:43 UTC |
155.05 KB |
no flags
|
Details |
0001-drm-scheduler-rework-job-destruction.patch |
patch
|
2019-04-05 20:41:52 UTC |
10.30 KB |
no flags
|
Details |
0002-drm-sched-Adapt-drivers-to-new-job-destruction-logic.patch |
patch
|
2019-04-05 20:51:04 UTC |
5.12 KB |
no flags
|
Details |
dmesg from patched kernel [0001 + 0002] |
text/plain
|
2019-04-06 14:44:12 UTC |
143.25 KB |
no flags
|
Details |
[PATCH] drm_amd_display: wait for fence without holding reservation lock.eml |
patch
|
2019-04-08 14:46:25 UTC |
11.18 KB |
no flags
|
Details |
[PATCH] drm_amd_display: wait for fence without holding reservation lock.patch |
patch
|
2019-04-08 14:48:19 UTC |
1.56 KB |
no flags
|
Details |
dmesg from patched kernel [0001 + 0002 + 3] |
text/plain
|
2019-04-09 03:15:01 UTC |
145.67 KB |
no flags
|
Details |
dmesg without patches |
text/plain
|
2019-04-10 03:41:52 UTC |
146.42 KB |
no flags
|
Details |
dmesg (with successfull GPU reset after applying patches from Comment 34) |
text/plain
|
2019-04-11 03:53:30 UTC |
471.80 KB |
no flags
|
Details |
Demonstration how message "drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!" get a real pain |
image/jpeg
|
2019-04-11 04:03:30 UTC |
2.42 MB |
no flags
|
Details |
dmesg of another GPU reset issue |
text/plain
|
2019-05-12 21:00:22 UTC |
111.42 KB |
no flags
|
Details |
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.