On 13/11/16 09:09 PM, Michael Strobel wrote: > Hi, > > i think i found the problem: it's powerplay. The bisection showed that > 3466904d38ff1e63f0a19cb31166db67f2d05c61 is the commit which introduced > the problem: > > while the code before checked if amdgpu_powerplay > 0 now it checks > equality. The default value is -1 so pp is enabled. I booted with > amdgpu.powerplay=0 and the problem is gone for the testing kernel 4.7. > > I tried a more recent kernel (4.9-rc5) and it seemed that it's not > checked anymore if amdgpu.powerplay equals 0. I'm adding a patch which > re enables the boot parameter. > > Furthermore i'm not sure what causes the problem with my GPU in the > first place. If there is anything i can do please let me know. Adding the amd-gfx mailing list to Cc. This bug report should be reassigned to the kernel package. > On 10/03/2016 04:45 AM, Michel Dänzer wrote: >> On 01/10/16 06:30 PM, Michael Strobel wrote: >>> Package: xserver-xorg-video-amdgpu >>> Version: 1.1.2-1 >>> Severity: normal >>> >>> Dear Maintainer, >>> >>> i'm running debian testing and for quite a while i have problems with my >>> xserver on newer kernels. While linux-image-4.2.0-1-amd64 works fine linux-image-4.6.0-1-amd64 and linux-image-4.7.0-1-amd64 my xserver spends very long time (several minutes) on initialization. >>> The only problem i can spot is a lot of >>> >>> Failed to send Previous Message. >>> Failed to send Message. >>> >>> messages in dmesg. I'm not complete sure if the problem is even xserver >> >> Yeah, unless this doesn't happen with an older version of >> xserver-xorg-video-amdgpu (and possibly related packages), it sounds >> like an amdgpu kernel driver regression. Any chance you can bisect or at >> least narrow down which kernel version introduced the problem? >> >> > -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer
Attachment:
signature.asc
Description: OpenPGP digital signature