dri-devel July 2017

dri-devel@lists.freedesktop.org

212 participants
1542 discussions

[Bug 29095] New: RC410: 3D apps do not run after upgrade to 2.6.35-rc5
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=29095 Summary: RC410: 3D apps do not run after upgrade to 2.6.35-rc5 Product: DRI Version: XOrg CVS Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: tstellar(a)gmail.com Created an attachment (id=37103) --> (https://bugs.freedesktop.org/attachment.cgi?id=37103) Output from glxgears with RADEON_DEBUG=all I just upgraded from 2.6.33 to 2.6.35-rc5, and whenever I try to run glxgears or any of the mesa demos only a black window is displayed. There is nothing interesting in my dmesg log. I am using the latest git versions of libdrm, mesa, xf86-video-ati, and X server 1.8.1.902. My card is a Radeon Xpress 200M IGP (RC410) I can give bisecting the kernel a try, but first I wanted to see if anyone had any ideas about what might be wrong. Previously, I was running a patched version of 2.6.33 to work around this bug: https://bugzilla.kernel.org/show_bug.cgi?id=15626 . The fix for this bug made it into one of the 2.6.35-rc* releases. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 11

[Bug 29026] New: r600: Garbled screen after resuming from suspend (KMS)
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=29026 Summary: r600: Garbled screen after resuming from suspend (KMS) Product: DRI Version: DRI CVS Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: direx(a)betriebsdirektor.de Created an attachment (id=36970) --> (https://bugs.freedesktop.org/attachment.cgi?id=36970) system log Using mesa-git, libdrm-git and xf86-video-ati-git I always get a garbled screen (including framebuffer console) after resume. I took a screenshot, but obviously it looks normal. Video card: Radeon HD3870 Kernel: Linux-git (2.6.35-rc4+), KMS enabled by default There is no crash or lockup, it's just sort of impossible to read anything on the screen after resuming. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 17

[Bug 99815] Power management problems & kernel hangs with Cap Verde
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=99815 Bug ID: 99815 Summary: Power management problems & kernel hangs with Cap Verde Product: DRI Version: unspecified Hardware: Other OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: klaus.kusche(a)computerix.info I recently switched from the radeon kernel driver to the amdgpu kernel driver. As a consequence, battery lifetime of my laptop was more than halved (before I could give *two* 90 minutes lectures in a row running on battery, now the battery is empty after around 70 minutes), i.e. with amdgpu, the graphic card consumes a multiple of the power it needed with radeon. GPU is AMDGPU(0): Chipset: "VERDE" (ChipID = 0x6825) Laptop is Dell Precision M6700 OS is linux 4.9, userland is running latest official releases (Gentoo) Typical load is two screens (internal + VGA-Beamer, both 1024x768 mirrored) with very light load (no 3D & no video at all, just static pdf slides). Power settings in battery mode with the old radeon driver were * no dpm (always was very unstable and consumed by far more power than "classic" pm) * "classic" pm with power_method = profile and power_profile = low Analysis of the problems with amdgpu showed: 1.) There is no "classic" power management: If dpm is turned off with amdgpu, there is no power management at all, and the card permanently runs with high power. Why was "classic" power management dropped completely? Basically, I neither want nor need any dynamic adjustment: When on battery, the gpu should permanently run on minimal power, independent of its load. 2.) The default dpm mode is "balanced" and "auto". "balanced" does not change to "battery" automatically when AC is removed, and it is impossible to set the mode to "battery" manually: Any attempt to set it via sysfs either kills the process doing so or hangs it in a kill-9-immune state (which prevents system shutdown). I then code-changed the default initialization in si_dpm.c from "balanced" to "battery". This hangs the whole kernel hard during early boot: No display, no reaction to Alt-Sysrq, ... only hard power off helps. 3.) It is possible to set the dpm level from "auto" to "low", but that does not seem to result in any measurable effect or power savings? -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 29001] New: latest d-r-t has regular X crashes
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=29001 Summary: latest d-r-t has regular X crashes Product: DRI Version: XOrg CVS Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: aidan(a)cisco.com after updating to latest d-r-t, X crashes regularly, often just by starting firefox and waiting for it to restore all the previous open tabs. xorg-server 1.8.1.902 git libdrm/mesa/ddx kde 4.4.5 on rv790. Backtrace: [ 33638.299] 0: /usr/bin/X (xorg_backtrace+0x28) [0x4a1358] [ 33638.299] 1: /usr/bin/X (0x400000+0x636f9) [0x4636f9] [ 33638.299] 2: /lib/libpthread.so.0 (0x7fc9ad310000+0xf120) [0x7fc9ad31f120] [ 33638.299] 3: /usr/lib/libpixman-1.so.0 (0x7fc9ac3a6000+0x3ce53) [0x7fc9ac3e2e53] [ 33638.299] 4: /usr/lib/libpixman-1.so.0 (0x7fc9ac3a6000+0x31091) [0x7fc9ac3d7091] [ 33638.299] 5: /usr/lib/libpixman-1.so.0 (pixman_image_composite32+0xfe3) [0x7fc9ac3d91c3] [ 33638.299] 6: /usr/lib64/xorg/modules/libfb.so (fbComposite+0x225) [0x7fc9a99ad8b5] [ 33638.299] 7: /usr/lib64/xorg/modules/libexa.so (0x7fc9a9780000+0x10701) [0x7fc9a9790701] [ 33638.299] 8: /usr/lib64/xorg/modules/libexa.so (0x7fc9a9780000+0xe15e) [0x7fc9a978e15e] [ 33638.299] 9: /usr/bin/X (0x400000+0xd4b80) [0x4d4b80] [ 33638.299] 10: /usr/bin/X (0x400000+0xce2ad) [0x4ce2ad] [ 33638.300] 11: /usr/bin/X (0x400000+0x2f5ec) [0x42f5ec] [ 33638.300] 12: /usr/bin/X (0x400000+0x24de5) [0x424de5] [ 33638.300] 13: /lib/libc.so.6 (__libc_start_main+0xfd) [0x7fc9ab9dbbbd] [ 33638.300] 14: /usr/bin/X (0x400000+0x24999) [0x424999] [ 33638.300] Bus error at address 0x7fc99fb86b04 [ 33638.300] Fatal server error: [ 33638.300] Caught signal 7 (Bus error). Server aborting [ 33638.300] [ 33638.300] -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 4

[Bug 28940] New: rv515 (Mobility x1400) Display corruption after some time
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=28940 Summary: rv515 (Mobility x1400) Display corruption after some time Product: DRI Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: gtdev(a)spearhead.de Created an attachment (id=36799) --> (https://bugs.freedesktop.org/attachment.cgi?id=36799) lspci output (graphics only) After some uptime (upwards of an hour so far), I get different kinds of display corruption on a laptop with a Radeon x1400. Currently, I'm looking at a somewhat grainy picture which looks like a badly dithered low-colour version of the screen content. There are noticeable vertical stripes, and the whole image is shimmering. The system is working fine otherwise. In an earlier instance, I had a pulsating green gradient covering the bottom of the screen. In addition, screen response was slow, like the proper content was only updating evers second or so. The effect does not show in screenshots. This is on a Debian-built 2.6.34 686 kernel, running X.org 1.7.7 and the "radeon" driver 6.13.0, libdrm2 2.4.21 from Debian packages. I'm attaching lspci output for the card, as well as dmesg and the Xorg.log from the currently "broken" running system. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 7

[Bug 28928] New: [ati-dri] R100 OpenGL Crash buffer overflow
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=28928 Summary: [ati-dri] R100 OpenGL Crash buffer overflow Product: DRI Version: XOrg CVS Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: redtux2k9(a)gmail.com DRI is working with direct rendering and hardware acceleration, but only working OpenGL application is glxgears and small example written by me using gtkglext. When I try to run yabause or any application that uses OpenGL then I've got this: *********************************WARN_ONCE********************************* File radeon_swtcl.c function r100_swtcl_flush line 322 Rendering was 13 commands larger than predicted size. We might overflow command buffer. *************************************************************************** drmRadeonCmdBuffer: -22. Kernel failed to parse or rejected command stream. See dmesg for more info. And then crash. When I write dmesg I got this: [drm:r100_cs_track_texture_check] *ERROR* No texture bound to unit 0 [drm:radeon_cs_ioctl] *ERROR* Invalid command stream ! I'm using module radeon under ATI Radeon M6 (R100) and packages version under Archlinux i686: ati-dri 7.8.2-1 xf86-video-ati 6.13.0-1 mesa 7.8.2-1 libgl 7.8.2-1 The DRI module is from 20090101, but was working ok with version from 20061018, so with Mesa 7.2 (2008). I've tried to compile Mesa 7.2, but the DRI was not working (only swrast). Please help me, I can't even watch youtube with proper speed. Only alternative for me is Debian Lenny that has everything (DRI) working ok, because it has the old version. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 1

[Bug 28600] New: The LXterminal Window TitleBar does not show up when KMS is enabled
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=28600 Summary: The LXterminal Window TitleBar does not show up when KMS is enabled Product: DRI Version: XOrg CVS Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: minor Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: jjorge(a)free.fr On a R100 Mobility GPU, Mandriva 2010.1 , I can try Radeon Modesetting. All works, except the title bar of LXterminal that appears transparent. I still can move the windo clicking on it. Then WM used is OpenBox. ATI Technologies Inc Radeon Mobility M6 LY -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 4

[Bug 28520] New: X: page allocation failure. 2.6.35-rc3
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=28520 Summary: X: page allocation failure. 2.6.35-rc3 Product: DRI Version: XOrg CVS Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: mikko.cal(a)gmail.com I hit this bug. It was present with 2.6.35-rc2 too. Mesa git, xf86-video-ati git. Xorg-server 1.8.1. X: page allocation failure. order:0, mode:0x4 Pid: 1514, comm: X Not tainted 2.6.35-rc3 #1 Call Trace: [<ffffffff8108ce49>] ? __alloc_pages_nodemask+0x629/0x680 [<ffffffff8108c920>] ? __alloc_pages_nodemask+0x100/0x680 [<ffffffffa00db8f3>] ? ttm_get_pages+0x2c3/0x448 [ttm] [<ffffffffa00d4658>] ? __ttm_tt_get_page+0x98/0xc0 [ttm] [<ffffffffa00d4988>] ? ttm_tt_populate+0x48/0x90 [ttm] [<ffffffffa00d4a26>] ? ttm_tt_bind+0x56/0xa0 [ttm] [<ffffffffa00d5230>] ? ttm_bo_handle_move_mem+0x1d0/0x430 [ttm] [<ffffffffa00d76d6>] ? ttm_bo_move_buffer+0x166/0x180 [ttm] [<ffffffffa00b9736>] ? drm_mm_kmalloc+0x26/0xc0 [drm] [<ffffffff81030ea9>] ? get_parent_ip+0x9/0x20 [<ffffffffa00d7786>] ? ttm_bo_validate+0x96/0x130 [ttm] [<ffffffffa00d7b35>] ? ttm_bo_init+0x315/0x390 [ttm] [<ffffffffa0122eb8>] ? radeon_bo_create+0x118/0x210 [radeon] [<ffffffffa0122fb0>] ? radeon_ttm_bo_destroy+0x0/0xb0 [radeon] [<ffffffffa013704c>] ? radeon_gem_object_create+0x8c/0x110 [radeon] [<ffffffffa013711f>] ? radeon_gem_create_ioctl+0x4f/0xe0 [radeon] [<ffffffffa00b10e6>] ? drm_ioctl+0x3d6/0x470 [drm] [<ffffffffa01370d0>] ? radeon_gem_create_ioctl+0x0/0xe0 [radeon] [<ffffffff810b965f>] ? do_sync_read+0xbf/0x100 [<ffffffff810c8965>] ? vfs_ioctl+0x35/0xd0 [<ffffffff810c8b28>] ? do_vfs_ioctl+0x88/0x530 [<ffffffff81031ed7>] ? sub_preempt_count+0x87/0xb0 [<ffffffff810c9019>] ? sys_ioctl+0x49/0x80 [<ffffffff810ba4fe>] ? sys_read+0x4e/0x90 [<ffffffff810024ab>] ? system_call_fastpath+0x16/0x1b Mem-Info: DMA per-cpu: CPU 0: hi: 0, btch: 1 usd: 0 CPU 1: hi: 0, btch: 1 usd: 0 CPU 2: hi: 0, btch: 1 usd: 0 CPU 3: hi: 0, btch: 1 usd: 0 DMA32 per-cpu: CPU 0: hi: 186, btch: 31 usd: 156 CPU 1: hi: 186, btch: 31 usd: 164 CPU 2: hi: 186, btch: 31 usd: 192 CPU 3: hi: 186, btch: 31 usd: 175 Normal per-cpu: CPU 0: hi: 186, btch: 31 usd: 177 CPU 1: hi: 186, btch: 31 usd: 153 CPU 2: hi: 186, btch: 31 usd: 147 CPU 3: hi: 186, btch: 31 usd: 168 active_anon:248943 inactive_anon:70653 isolated_anon:0 active_file:231008 inactive_file:258837 isolated_file:0 unevictable:1 dirty:5 writeback:0 unstable:0 free:5083 slab_reclaimable:53052 slab_unreclaimable:16244 mapped:45401 shmem:4420 pagetables:6333 bounce:0 DMA free:13036kB min:28kB low:32kB high:40kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15704kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:0kB slab_unreclaimable:8kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? yes lowmem_reserve[]: 0 3255 3760 3760 DMA32 free:5704kB min:6780kB low:8472kB high:10168kB active_anon:915704kB inactive_anon:184904kB active_file:789940kB inactive_file:901472kB unevictable:4kB isolated(anon):0kB isolated(file):0kB present:3333920kB mlocked:4kB dirty:4kB writeback:0kB mapped:114500kB shmem:17136kB slab_reclaimable:197620kB slab_unreclaimable:38500kB kernel_stack:776kB pagetables:12928kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no lowmem_reserve[]: 0 0 505 505 Normal free:1840kB min:1048kB low:1308kB high:1572kB active_anon:80068kB inactive_anon:97708kB active_file:134092kB inactive_file:133876kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:517120kB mlocked:0kB dirty:16kB writeback:0kB mapped:67104kB shmem:544kB slab_reclaimable:14588kB slab_unreclaimable:26468kB kernel_stack:1936kB pagetables:12404kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no lowmem_reserve[]: 0 0 0 0 DMA: 1*4kB 1*8kB 0*16kB 1*32kB 1*64kB 1*128kB 0*256kB 1*512kB 0*1024kB 0*2048kB 3*4096kB = 13036kB DMA32: 200*4kB 10*8kB 1*16kB 0*32kB 1*64kB 1*128kB 1*256kB 1*512kB 0*1024kB 0*2048kB 1*4096kB = 5952kB Normal: 232*4kB 2*8kB 0*16kB 2*32kB 3*64kB 1*128kB 2*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 1840kB 494223 total pagecache pages 66 pages in swap cache Swap cache stats: add 475, delete 409, find 6/7 Free swap = 2094600kB Total swap = 2096476kB 983024 pages RAM 33615 pages reserved 397983 pages shared 655130 pages non-shared [TTM] Unable to allocate page. radeon 0000:01:05.0: object_init failed for (7827456, 0x00000002) [drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM object (7827456, 2, 4096, -12) SysRq : HELP : loglevel(0-9) reBoot Crash terminate-all-tasks(E) memory-full-oom-kill(F) kill-all-tasks(I) thaw-filesystems(J) saK show-backtrace-all-active-cpus(L) show-memory-usage(M) nice-all-RT-tasks(N) powerOff show-registers(P) show-all-timers(Q) unRaw Sync show-task-states(T) Unmount force-fb(V) show-blocked-tasks(W) SysRq : HELP : loglevel(0-9) reBoot Crash terminate-all-tasks(E) memory-full-oom-kill(F) kill-all-tasks(I) thaw-filesystems(J) saK show-backtrace-all-active-cpus(L) show-memory-usage(M) nice-all-RT-tasks(N) powerOff show-registers(P) show-all-timers(Q) unRaw Sync show-task-states(T) Unmount force-fb(V) show-blocked-tasks(W) SysRq : HELP : loglevel(0-9) reBoot Crash terminate-all-tasks(E) memory-full-oom-kill(F) kill-all-tasks(I) thaw-filesystems(J) saK show-backtrace-all-active-cpus(L) show-memory-usage(M) nice-all-RT-tasks(N) powerOff show-registers(P) show-all-timers(Q) unRaw Sync show-task-states(T) Unmount force-fb(V) show-blocked-tasks(W) SysRq : HELP : loglevel(0-9) reBoot Crash terminate-all-tasks(E) memory-full-oom-kill(F) kill-all-tasks(I) thaw-filesystems(J) saK show-backtrace-all-active-cpus(L) show-memory-usage(M) nice-all-RT-tasks(N) powerOff show-registers(P) show-all-timers(Q) unRaw Sync show-task-states(T) Unmount force-fb(V) show-blocked-tasks(W) SysRq : HELP : loglevel(0-9) reBoot Crash terminate-all-tasks(E) memory-full-oom-kill(F) kill-all-tasks(I) thaw-filesystems(J) saK show-backtrace-all-active-cpus(L) show-memory-usage(M) nice-all-RT-tasks(N) powerOff show-registers(P) show-all-timers(Q) unRaw Sync show-task-states(T) Unmount force-fb(V) show-blocked-tasks(W) SysRq : HELP : loglevel(0-9) reBoot Crash terminate-all-tasks(E) memory-full-oom-kill(F) kill-all-tasks(I) thaw-filesystems(J) saK show-backtrace-all-active-cpus(L) show-memory-usage(M) nice-all-RT-tasks(N) powerOff show-registers(P) show-all-timers(Q) unRaw Sync show-task-states(T) Unmount force-fb(V) show-blocked-tasks(W) -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 7

[Bug 28426] New: hardware cursor corruption with radeon+kms
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=28426 Summary: hardware cursor corruption with radeon+kms Product: DRI Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: maillist(a)pnpitalia.it please see also bug #19215, may be related After some days the xorg server is up and running the cursor get corrupted. This is a kde4 desktop on a dual 1920x1080 screen powered by an ATI Radeon HD 4670. The bug happens often, having played a game like Aquaria (in windowed mode) help a lot, but it does not guarantees an immediate trigger. This time xorg was up and running for about four days (not totally sure), yesterday I've played with the already mentioned Aquaria. please feel free to request further information since I don't know where to start I've tried to be broad on covering the system information, here is what the attached zip file contain: - "cursor-gimp.jpeg" cursor as it should be (after a reboot) - "VGA-0-cursor-broken.jpeg" cursor as it's shown in the left monitor VGA-0 - "DVI-0-cursor-broken.jpeg" cursor as it's shown in the right monitor DVI-0 - "Xorg.0.log" log for the server on vt7 whit kde running - "Xorg.1.log" tentative to start another X server on vt8, it also had a broken cursor - "xorg.conf" "SWcursor" is commented out - "radeontool--debug-regs.log" `radeontool debug regs` output - "installed-software.log" radeon and x11 related software installed on this pc - "modinfo-radeon.log" `modinfo radeon` output - "lsmod.log" `lsmod` output - "xrandr--verbose.log" `xrandr -q --verbose` output - "lspci-vvv.log" `lspci -vvv` output - "lshw.log" `lshw` output, it's an hardware lister - "dmesg.log" `dmesg` output -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 17

[Bug 99779] Lenovo Thinkpad E450 (Kaveri A6-7000 Radeon R4) Blank Screen after suspend (displayport link issues)
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=99779 Bug ID: 99779 Summary: Lenovo Thinkpad E450 (Kaveri A6-7000 Radeon R4) Blank Screen after suspend (displayport link issues) Product: DRI Version: XOrg git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: brookskd(a)gmail.com Created attachment 129527 --> https://bugs.freedesktop.org/attachment.cgi?id=129527&action=edit dmesg 4.9.8 If I shut my laptop lit it suspends, then when opening the lid and resuming I get a blank screen and am unable to get the display to work again unless I reboot. I can ssh into computer and I get displayport link errors in the attached dmesg log. This issue does not occur if I use the radeon kernel module instead of amdgpu. This seems very similar to bug 90320 but I filed this one because it is amdgpu not radeon: https://bugs.freedesktop.org/show_bug.cgi?id=90320 I've also attached the Xorg.0.log but it does not have any errors indicated. It indicates successful exit because I stopped the server over ssh and tried to restart gdm a few times which is why there are multiple displayport link status failed messages in dmesg. -- You are receiving this mail because: You are the assignee for the bug.

1 3

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel July 2017