https://bugs.freedesktop.org/show_bug.cgi?id=109628
Martin Peres changed:
What|Removed |Added
Resolution|--- |MOVED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=109628
--- Comment #35 from peter m ---
updated kernel to 5.3.11-200.fc30, problem still exists
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@
https://bugs.freedesktop.org/show_bug.cgi?id=109628
--- Comment #34 from Chris Snook ---
(In reply to Chris Snook from comment #33)
> (In reply to Johannes Hirte from comment #28)
> > From the reports, it seems to be compositor related. For me, kwin with
> > OpenGL 3.1 backend works fine. xfwm4 s
https://bugs.freedesktop.org/show_bug.cgi?id=109628
--- Comment #33 from Chris Snook ---
(In reply to Johannes Hirte from comment #28)
> From the reports, it seems to be compositor related. For me, kwin with
> OpenGL 3.1 backend works fine. xfwm4 seems to trigger the bug, maybe other
> compositor
https://bugs.freedesktop.org/show_bug.cgi?id=109628
--- Comment #32 from peter m ---
updated kernel to 5.3.8-200.fc30, problem still exists
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@l
https://bugs.freedesktop.org/show_bug.cgi?id=109628
Jiri Slaby changed:
What|Removed |Added
CC||b...@atomicbee.cz
--- Comment #31 from Jir
https://bugs.freedesktop.org/show_bug.cgi?id=109628
--- Comment #30 from peter m ---
kernel 5.3.5-200.fc30.x86_64 (mockbu...@bkernel04.phx2.fedoraproject.org)
xfce - 4.14
kernel still crushing
[ cut here ]
WARNING: CPU: 2 PID: 184 at
drivers/gpu/drm/amd/amdgpu/../display
https://bugs.freedesktop.org/show_bug.cgi?id=109628
--- Comment #29 from Michel Dänzer ---
(In reply to Mirek Kratochvil from comment #27)
> Anyway, the latest X driver from git is broken as well. Should the issue be
> reported there, or is it better to fix it in kernel layer?
It should be fixed
https://bugs.freedesktop.org/show_bug.cgi?id=109628
--- Comment #28 from Johannes Hirte ---
(In reply to John Smith from comment #22)
> (In reply to Johannes Hirte from comment #21)
> > Any possibility to test with 5.3 kernel? It seems it's fixed but not
> > backported.
>
> If I'm understanding
https://bugs.freedesktop.org/show_bug.cgi?id=109628
--- Comment #27 from Mirek Kratochvil ---
Confirming the posted X driver workaround fixes it on 2700U. Debian 5.2.*
kernels and vanilla 5.3.1 work perfectly now.
Anyway, the latest X driver from git is broken as well. Should the issue be
report
https://bugs.freedesktop.org/show_bug.cgi?id=109628
--- Comment #26 from Mirek Kratochvil ---
Hello everyone,
reporting the same on thinkpad E585; blackscreen issue is triggered by starting
X with compositor (lightdm works okay though).
Attaching my warning + backtrace + TEST_DEBUG_DATA from de
https://bugs.freedesktop.org/show_bug.cgi?id=109628
--- Comment #25 from devbazilio ---
I have the same problem with kernel 5.3.1 - after opening of lid cower after
suspen the screen is black, however I can ssh to laptop
CPU/GPU AMD Ryzen 3 2300U with Radeon Vega 6 Mobile Gfx
Please let me know
https://bugs.freedesktop.org/show_bug.cgi?id=109628
--- Comment #24 from t...@siduction.org ---
Same problem here on my Ideapad 330
Machine: Type: Laptop System: LENOVO product: 81D2 v: Lenovo ideapad
330-15ARR serial:
Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial: UEFI
https://bugs.freedesktop.org/show_bug.cgi?id=109628
--- Comment #22 from John Smith ---
(In reply to Johannes Hirte from comment #21)
> Any possibility to test with 5.3 kernel? It seems it's fixed but not
> backported.
If I'm understanding it correctly, backported means it already should be in
5
https://bugs.freedesktop.org/show_bug.cgi?id=109628
--- Comment #23 from vlad@ivanov.email ---
I had the same problem with Ryzen 2400G on kernels 5.2, 5.3 and 5.4, but it
would only be reproduced when X was running. If I stop X before going to sleep,
wakeup would work. I managed to fix it by rever
https://bugs.freedesktop.org/show_bug.cgi?id=109628
--- Comment #21 from Johannes Hirte ---
(In reply to John Smith from comment #20)
> Still seeing the warning with 5.4.0-0.rc0.git2.2.fc32.x86_64; waking up
> doesn't work. This is fedora kernel though and there's a possibility those
> patches ar
https://bugs.freedesktop.org/show_bug.cgi?id=109628
--- Comment #20 from vlad@ivanov.email ---
Still seeing the warning with 5.4.0-0.rc0.git2.2.fc32.x86_64; waking up doesn't
work. This is fedora kernel though and there's a possibility those patches
aren't integrated there yet; is there a way to c
https://bugs.freedesktop.org/show_bug.cgi?id=109628
--- Comment #19 from peter m ---
Created attachment 145377
--> https://bugs.freedesktop.org/attachment.cgi?id=145377&action=edit
kernel 5.2.14-200 dmesg output
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=109628
Rohan Lean changed:
What|Removed |Added
CC||ro...@rohanlean.de
--- Comment #18 from Ro
https://bugs.freedesktop.org/show_bug.cgi?id=109628
--- Comment #17 from peter m ---
updated to kernel 5.2.13-200.fc30.x86_64
dmesg prints no more WARNING messages, but screen still black after login
screen
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=109628
--- Comment #16 from Johannes Hirte ---
Seems to be fixed now. Tested with v5.3-rc8-7-g3120b9a6a3f7 and resume from S3
Works without problems. Interestingly even v5.3-rc6-129-g265381004994 works now
without additional patches.
--
You are recei
https://bugs.freedesktop.org/show_bug.cgi?id=109628
--- Comment #15 from peter m ---
(In reply to peter m from comment #14)
> Thread with similar problem
>
> https://bugs.freedesktop.org/show_bug.cgi?id=111459
In my case, screen became black after entering password in welcome screen.
--
You a
https://bugs.freedesktop.org/show_bug.cgi?id=109628
--- Comment #14 from peter m ---
Thread with similar problem
https://bugs.freedesktop.org/show_bug.cgi?id=111459
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-deve
https://bugs.freedesktop.org/show_bug.cgi?id=109628
--- Comment #13 from Johannes Hirte ---
It seems DCC is broken on Raven Ridge. So how about disabling it here, until
the problems are solved?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=109628
--- Comment #12 from Johannes Hirte ---
On top of 5.2.11 it doesn't work either. It get even worse. Without the two
patches, I can shutdown the system. With both patches applied, the system hangs
completely after resume. I have to force it off.
https://bugs.freedesktop.org/show_bug.cgi?id=109628
--- Comment #11 from Johannes Hirte ---
With those two patches on top of v5.3-rc6-129-g265381004994 resume from S3
suspend still hangs with a black screen. I've had to hard reset the system, so
I can't say for sure, if this is the same bug.
--
https://bugs.freedesktop.org/show_bug.cgi?id=109628
--- Comment #10 from Nicholas Kazlauskas ---
(In reply to Johannes Hirte from comment #9)
> git bisect points me to
>
> commit df8368be1382b442384507a5147c89978cd60702 (refs/bisect/bad)
> Author: Nicholas Kazlauskas
> Date: Wed Feb 27 12:56
https://bugs.freedesktop.org/show_bug.cgi?id=109628
--- Comment #9 from Johannes Hirte ---
git bisect points me to
commit df8368be1382b442384507a5147c89978cd60702 (refs/bisect/bad)
Author: Nicholas Kazlauskas
Date: Wed Feb 27 12:56:36 2019 -0500
drm/amdgpu: Bump amdgpu version for per-f
https://bugs.freedesktop.org/show_bug.cgi?id=109628
--- Comment #8 from Johannes Hirte ---
For me it's a regression in the 5.2-development. Testing with 5.1-series show
no errors. Resume after S3 suspend works without problem.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=109628
--- Comment #7 from Johannes Hirte ---
some more infos: I see the mentioned error in the logs during normal work, but
no other problems. When resuming from S3 suspend, the display stays black and I
find dozens of those dcn10_verify_allow_pstate_
https://bugs.freedesktop.org/show_bug.cgi?id=109628
--- Comment #6 from Johannes Hirte ---
seeing similar with a Dell Latitude 5495 with AMD Ryzen 5 PRO 2500U:
kernel is 5.2.10
[ 1795.534761] [ cut here ]
[ 1795.534791] WARNING: CPU: 7 PID: 765 at
drivers/gpu/drm/amd/amd
https://bugs.freedesktop.org/show_bug.cgi?id=109628
--- Comment #5 from Rafał Miłecki ---
Created attachment 143531
--> https://bugs.freedesktop.org/attachment.cgi?id=143531&action=edit
dmesg from 5.0.0-rc7 with WARNINGs
Thanks Nicholas for looking at this.
I kept running 5.0.0-rc7 for few mo
https://bugs.freedesktop.org/show_bug.cgi?id=109628
--- Comment #4 from Nicholas Kazlauskas ---
There were some patches recently for Raven that fixed some programming sequence
issues during changes for dpms / suspend. I wonder if these would help fix what
you're reporting - the pstate warnings us
https://bugs.freedesktop.org/show_bug.cgi?id=109628
--- Comment #3 from Rafał Miłecki ---
Created attachment 143375
--> https://bugs.freedesktop.org/attachment.cgi?id=143375&action=edit
dcn10_verify_allow_pstate_change_high() source with line numbers
--
You are receiving this mail because:
Yo
https://bugs.freedesktop.org/show_bug.cgi?id=109628
--- Comment #2 from Rafał Miłecki ---
Created attachment 143374
--> https://bugs.freedesktop.org/attachment.cgi?id=143374&action=edit
Xorg.0.log
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=109628
--- Comment #1 from Rafał Miłecki ---
Created attachment 143373
--> https://bugs.freedesktop.org/attachment.cgi?id=143373&action=edit
dmesg
I'm attaching my pretty big dmesg. There are many MCE errors reported which
should be harmless:
https:
https://bugs.freedesktop.org/show_bug.cgi?id=109628
Bug ID: 109628
Summary: WARNING at dcn10_hw_sequencer.c:868
dcn10_verify_allow_pstate_change_high()
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
37 matches
Mail list logo
