Dear AMD Developers,
I am building your amd-staging-drm-next kernels for more than 2 years now and patch this up with the official kernel patches and ubuntu's sauce patches: https://github.com/M-Bab/linux-kernel-amdgpu-binaries
Dear AMD Developers,I am building your amd-staging-drm-next kernels for more than 2 years now and patch this up with the official kernel patches and ubuntu's sauce patches: https://github.com/M-Bab/linux-kernel-amdgpu-binariesOne of the kernel users reports about hibernation problems since quite a
Dear AMD Developers,At first congratulations for the DC code submission to the 4.15 kernel.Unfortunately the major regression which I reported on 29.09., 06.10.,02.11. and 05.11. still exists. But this time I got additionaldebugging information maybe this helps to fix it.Summary: I am running Xubu
Dear AMD Developers,
At first congratulations for the DC code submission to the 4.15 kernel.
Unfortunately the major regression which I reported on 29.09., 06.10.,
02.11. and 05.11. still exists. But this time I got additional
debugging information maybe this helps to fix it.
Summary: I am runnin
Dear AMD developers,
I wanted to mention that the regression in amd-staging-drm-next which I
reported on the 29.09. and the 06.10. still exists with the latest tree
state of the branch.
A crash/freeze occurs after the screen is re-enabled either from
suspend or from screen locking (which shuts of
Dear AMD developers,Are there no comments/questions on this issue or did the mail just got lost in between the flood of patches?Many regards,Martin-- Ursprüngliche Nachricht --Von: Martin Babutzka An: amd-gfx@lists.freedesktop.orgDatum: 6. Oktober 2017 um 18:43Betreff: Regression
Hello there,
Sorry it is me again with another regression. I just built the latest
amd-staging-drm-next and the issue which was already reported here:
https://github.com/M-Bab/linux-kernel-amdgpu-binaries/issues/29
and which I can confirm is still existing.
The issue is caused occasionally when r
@Steven Falco: This behavior was EXACTLY the same with my R9 380 caused
by commit e37a7b4088da ("drm/amd/powerplay: tidy up ret checks in
amd_powerplay.c"). This is reverted now since a few days - are you sure
your kernel build already includes commit adc6af2349f0
("drm/amd/powerplay: fix ret check
Hello,
Today I tracked down 2 regressions with git bisect:
1. Crash: the most recent amd-drm-staging-next code based kernels
result in a complete crash on boot with no interaction possible. The
cause is a "tidy up" commit which actually inverts the logical
behavior. Went through the amd-gfx list t
Hello,
At first congrats for submitting the pull request. I hope the dc code
is accepted and included in the 4.15 kernel.
Me and some other users of my kernel builds (https://github.com/M-Bab/l
inux-kernel-amdgpu-binaries) found further regressions in builds based
on amd-staging-4.12 and amd-stag
gards,
Martin Babutzka
Am Montag, den 24.07.2017, 18:12 + schrieb Deucher, Alexander:
> > -Original Message-
> > From: amd-gfx [mailto:amd-gfx-boun...@lists.freedesktop.org] On
> > Behalf
> > Of Martin Babutzka
> > Sent: Monday, July 24, 2017 1:06 PM
&g
ain.
Many regards,
Martin Babutzka
___
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
I hope this helps you to find the regression. Just tell me if I canprovide further details or testing.Kind regards,Martin Babutzka
commit cdd8afd871683b14821a12377441c190ec9f9ac7
Merge: d87db1b2c751 931e0fabb75a
Author: Martin Babutzka
Date: Thu Jun 8 19:44:44 2017 +0200
Merge branch '
13 matches
Mail list logo
