https://bugs.freedesktop.org/show_bug.cgi?id=105018
Julio changed:
What|Removed |Added
See Also||https://bugs.freedesktop.or
|
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #41 from Ainola ---
ecomer, as I suspect we are both experiencing the same issue, here's a new
report you (and anyone else lurking) can follow:
https://bugs.freedesktop.org/show_bug.cgi?id=107863
--
You are receiving this mail bec
https://bugs.freedesktop.org/show_bug.cgi?id=105018
Michel Dänzer changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REOPENED
https://bugs.freedesktop.org/show_bug.cgi?id=105018
ecomer changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #38 from L.S.S. ---
EDIT: Forgot to mention that I'm currently on 4.17.3-1-MANJARO kernel, which is
the latest at the time of writing.
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #37 from L.S.S. ---
Attempted to lock the screen and leave it blank for a while to see what
happens, and it seems for the first time there are still errors related to
VBLANK, but they appear minor as the system woke up just fine.
I
https://bugs.freedesktop.org/show_bug.cgi?id=105018
Harry Wentland changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #35 from Adam Bolte ---
I believe I've been seeing the same bug as of late.
[Sat Jun 23 23:02:04 2018] [ cut here ]
[Sat Jun 23 23:02:04 2018] kernel BUG at
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amd
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #34 from Michel Dänzer ---
While it's good to hear that xf86-video-amdgpu doesn't trigger it, the kernel
BUG is still a kernel driver bug.
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #33 from Öyvind Saether ---
In my case the problem was not having xorg-x11-drv-amdgpu installed (how
embarrassing) which made xorg use xorg-x11-drv-ati. Yes, really. I assumed
Fedora 28 beta installed it along with all the other driv
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #32 from L.S.S. ---
So it seems there definitely is a regression on 4.17 on this issue (the patches
are not required as the lines were already there in 4.17). This time it isn't a
kernel panic, but an "invalid opcode" error caused by
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #31 from Öyvind Saether ---
Kernel 4.17.0-rc3-linus.git-keumjo4.17.0-rc3-linus.git-keumjo on a 2400G with a
RX 560 GPU:
> login to xfce desktop
> type "xset dpms force standby" in a terminal
screens go blank and there is no more res
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #30 from L.S.S. ---
EDIT 2: I couldn't reproduce the issue on 4.17 this time even after 2 wakeups.
However, the issue I encountered was similar (system apparently froze when
trying to wake up the screen).
After looking into it, I f
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #29 from L.S.S. ---
EDIT: Maybe not really fixed in 4.17 (regression again?!)... just now after the
screen went blank, I got another panic and had to reboot... :-(
When the panic occurred, it spawned two errors.
Apr 12 11:32:03 lin
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #28 from L.S.S. ---
Just updated to the 4.17-rc0 kernel and it seems the problem has been mostly
fixed there. The patches are no longer needed (already in there) and trying to
reproduce the issue only resulted in a couple of "Failed
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #27 from L.S.S. ---
(In reply to Mez from comment #25)
> (In reply to L.S.S. from comment #23)
> > EDIT: It seems I'm experiencing some intermittent screen flicker with
> > current 4.16 kernel (on the same system, with only Patch 3 a
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #26 from Mez ---
Also propably related:
https://bugs.freedesktop.org/show_bug.cgi?id=101580
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing
https://bugs.freedesktop.org/show_bug.cgi?id=105018
Mez changed:
What|Removed |Added
CC||mezcalb...@hotmail.com
--- Comment #25 from Mez
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #24 from Ainola ---
My stability has been fine since I last commented. I'm now on 4.15.10+these
patches. However, my monitors won't turn off: When the screen turns off it'll
come right back on after a second.
Just now I also had my
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #23 from L.S.S. ---
EDIT: It seems I'm experiencing some intermittent screen flicker with current
4.16 kernel (on the same system, with only Patch 3 applied as it's the only
patch needed for 4.16), although it doesn't really affect n
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #22 from L.S.S. ---
It seems some of the patches (1, 2, and 4) have entered the 4.16 kernel, from
what I can tell when building the kernel for Manjaro, where these three patches
got rejected, and the exact code changes were found in
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #21 from L.S.S. ---
Another problem: When I woke up the screen, sometimes the system would have
intermittent soft lockups that made the system kind of unusable... This is
after I included the patch to the latest 4.15 kernel, 4.15.5 (
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #20 from Ainola ---
I've been using this patchset on linux 4.15.3 and 4.14.4 and haven't had a
problem since.
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=105018
Ainola changed:
What|Removed |Added
CC||b...@i--b.com
--- Comment #19 from Ainola ---
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #18 from Ainola ---
I applied the patch to 4.15.3 on archlinux and have tested with xset dpms force
{standby,suspend} with success.
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #17 from Harry Wentland ---
Thanks for fixing the patch conflict. I based them on
https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next but
should have based them on the 4.15 kernel.
Thanks as well for testing. The p
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #16 from L.S.S. ---
Just installed and booted the new kernel. It seems to have fixed the issue at
least to the extent that it would not totally crash the system like it used to.
However, I still see these in journalctl. This is afte
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #15 from L.S.S. ---
Never mind, just figured out how to properly adjust the patch file to match the
kernel source I got so the patch file gets to be properly applied... it seems
the rest of the patches went through without complaints
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #14 from L.S.S. ---
The first patch got rejected with the most recent 4.15 kernel source pulled
using the PKGBUILD file (Feb 14, 2018). The reject file contains:
--- drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
+++ drivers/gpu/
https://bugs.freedesktop.org/show_bug.cgi?id=105018
Harry Wentland changed:
What|Removed |Added
Attachment #137323|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #12 from Harry Wentland ---
Are you able to rebuild the kernel with the attached patches and see if that
fixes things?
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #11 from Harry Wentland ---
Created attachment 137325
--> https://bugs.freedesktop.org/attachment.cgi?id=137325&action=edit
Patch 4 Don't blow up if TG is NULL in dce110_vblank_set
--
You are receiving this mail because:
You are
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #10 from Harry Wentland ---
Created attachment 137324
--> https://bugs.freedesktop.org/attachment.cgi?id=137324&action=edit
Patch 3 Clean up formatting in irq_service_dce110.c
--
You are receiving this mail because:
You are the a
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #9 from Harry Wentland ---
Created attachment 137323
--> https://bugs.freedesktop.org/attachment.cgi?id=137323&action=edit
Patch 2 Return success when enabling interrupt
--
You are receiving this mail because:
You are the assigne
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #8 from Harry Wentland ---
Created attachment 137322
--> https://bugs.freedesktop.org/attachment.cgi?id=137322&action=edit
Patch 1 Use crtc enable/disable_vblank hooks
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #7 from L.S.S. ---
And I just crashed my system the same usual way. With those parameters set
there are some additional outputs besides the usual ones.
Feb 13 11:31:55 linuxsys kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]]
amd
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #6 from L.S.S. ---
Created attachment 137308
--> https://bugs.freedesktop.org/attachment.cgi?id=137308&action=edit
dmesg output with amdgpu.dc_log=1 and drm.debug=6, right after login.
I'm not sure to what extent is a "full" dmesg
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #5 from Harry Wentland ---
Can you attach a full dmesg log with amdgpu.dc_log=1 and drm.debug=6 passed as
kernel options?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #4 from L.S.S. ---
Just now I tried reproducing it without dc (passing amdgpu.dc=0) but somehow I
was not able to... the system was able to successfully get back to the lock
screen after letting it blank after an extended period.
As
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #3 from bp8b...@gmail.com ---
Sorry, i'm forget write.
I too have same problem, but on Desktop*.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mai
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #2 from bp8b...@gmail.com ---
l too have same problem.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.org
h
https://bugs.freedesktop.org/show_bug.cgi?id=105018
Michel Dänzer changed:
What|Removed |Added
CC||harry.wentl...@amd.com
--- Comment #1 f
https://bugs.freedesktop.org/show_bug.cgi?id=105018
ragnaros39...@yandex.com changed:
What|Removed |Added
Keywords||regression
Priority
https://bugs.freedesktop.org/show_bug.cgi?id=105018
Bug ID: 105018
Summary: Kernel panic when waking up after screen goes blank.
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
44 matches
Mail list logo
