dri-devel February 2016

dri-devel@lists.freedesktop.org

180 participants
1240 discussions

[Bug 93270] Only one of LVDS and VGA-0 work on HP Pavilion m6 with Radeon HD 7660G
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=93270 Bug ID: 93270 Summary: Only one of LVDS and VGA-0 work on HP Pavilion m6 with Radeon HD 7660G Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: surenkarapetyan(a)gmail.com When I attach an external monitor to my laptop and put it next to the internal one using xrandr, the internal monitor goes blank. If I then disable the external monitor, the internal one starts working. Sometimes (after a lot of switching), they both go blank. Weren't able to make them both work at the same time. Based on the logs, the system thinks that both outputs are working (the screen size gets increased to fit both monitors, the taskbar remains on the primary screen even if it is not working). I'm using the free "radeon" driver. I don't think the version is important, because I have the same issue with Fedora 20 and Fedora 22. The system has a second discreet radeon GPU, but I don't use it. 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660G] [1002:9900] 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840] (rev ff) And from xrandr output it looks like all outputs are connected to the default integrated GPU: [skarap@roadrunner ~]$ xrandr --listproviders Providers: number : 3 Provider 0: id: 0x8c cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 4 outputs: 3 associated providers: 2 name:radeon Provider 1: id: 0x55 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 6 outputs: 0 associated providers: 2 name:radeon Provider 2: id: 0x55 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 6 outputs: 0 associated providers: 2 name:radeon -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 93021] Sometimes External Monitor stays black after resuming from suspend
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=93021 Bug ID: 93021 Summary: Sometimes External Monitor stays black after resuming from suspend Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: holthuis.jan(a)googlemail.com Sometimes my external monitor (Acer X223W) stays black (powersave mode) when resuming from suspend. I'm using a HP ProBook 6465b (Llano/Sumo, AMD A6-APU, Radeon HD6520G). The Monitor is connected to the DVI port of my HP docking station (P/N: VB044AV). My Desktop Environment (GNOME 3) still thinks it's connected, so some windows aren't visible anymore. Workarounds: - Press WIN+P to disable the second monitor and use the Laptop screen only - Power off the external monitor and then switch it on again. It then starts to work again. Some more information: $ dmesg | tail -n 2 [ 7977.467770] [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [ 7977.467815] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed $ uname -a Linux jan-laptop 4.2.5-1-ARCH #1 SMP PREEMPT Tue Oct 27 08:13:28 CET 2015 x86_64 GNU/Linux $ glxinfo | grep OpenGL | grep string OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD SUMO (DRM 2.43.0, LLVM 3.7.0) OpenGL core profile version string: 3.3 (Core Profile) Mesa 11.0.5 OpenGL core profile shading language version string: 3.30 OpenGL version string: 3.0 Mesa 11.0.5 OpenGL shading language version string: 1.30 OpenGL ES profile version string: OpenGL ES 3.0 Mesa 11.0.5 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 $ xrandr Screen 0: minimum 320 x 200, current 3046 x 1050, maximum 8192 x 8192 VGA-0 disconnected (normal left inverted right x axis y axis) LVDS connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 309mm x 173mm 1366x768 60.10*+ 1280x720 59.86 1152x768 59.78 1024x768 59.92 800x600 59.86 848x480 59.66 720x480 59.71 640x480 59.38 DisplayPort-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1 disconnected (normal left inverted right x axis y axis) DisplayPort-2 connected 1680x1050+1366+0 (normal left inverted right x axis y axis) 474mm x 296mm 1680x1050 59.95*+ 1600x1200 60.00 1400x1050 59.95 1280x1024 75.02 1440x900 74.98 59.90 1280x960 60.00 1360x768 59.80 1152x864 75.00 1024x768 75.08 70.07 60.00 832x624 74.55 800x600 72.19 75.00 60.32 56.25 640x480 75.00 72.81 66.67 60.00 720x400 70.08 $ cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 18 model : 1 model name : AMD A6-3410MX APU with Radeon(tm) HD Graphics stepping : 0 microcode : 0x3000027 cpu MHz : 1000.000 cache size : 1024 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 6 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt arat cpb hw_pstate npt lbrv svm_lock nrip_save pausefilter vmmcall bugs : fxsave_leak sysret_ss_attrs bogomips : 3195.26 TLB size : 1536 4K pages clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts ttp tm stc 100mhzsteps hwpstate cpb [... and 3 more times] -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 93017] complete system stalls while changing displays resolutions on a hybrid (intel/radeon) system
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=93017 Bug ID: 93017 Summary: complete system stalls while changing displays resolutions on a hybrid (intel/radeon) system Product: DRI Version: DRI git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: debian(a)onerussian.com Originally reported within DRM/Intel (https://bugs.freedesktop.org/show_bug.cgi?id=92997#c1) and was recommended to seek support with Radeon peopl. The story began a month or so ago whenever I upgraded my Debian testing/sid installation with a new kernel (can dig out later if needed from which version) to 4.3.0 : laptop started to freeze completely, usually when switching displays (to/from external display)/resolution. My laptop is hp zbook 14" with dual GPU: 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b) 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] which sits on the docking station (stalls happen without docking I believe) which has a display connected via display port. Running nightly of git://anongit.freedesktop.org/drm-intel from yesterday I have managed to trigger the stall again: turned on 2nd display attached to the docking station (also via displayport), which xrandr doesn't actually see as connected, and usually it just shows the cloning of the 1st display (I guess docking station does it internally). When I turned it off again, which lead X to reset display and almost come back when it stalled... after reboot journalctl -b -1 showed: Nov 18 14:00:49 hopa /usr/lib/gdm3/gdm-x-session[2354]: (II) intel(0): resizing framebuffer to 1920x1200 Nov 18 14:00:50 hopa /usr/lib/gdm3/gdm-x-session[2354]: (II) RADEON(G0): EDID vendor "HWP", prod id 9977 Nov 18 14:00:50 hopa /usr/lib/gdm3/gdm-x-session[2354]: (II) RADEON(G0): Using hsync ranges from config file Nov 18 14:00:50 hopa /usr/lib/gdm3/gdm-x-session[2354]: (II) RADEON(G0): Using vrefresh ranges from config file Nov 18 14:00:50 hopa /usr/lib/gdm3/gdm-x-session[2354]: (II) RADEON(G0): Printing DDC gathered Modelines: Nov 18 14:00:50 hopa /usr/lib/gdm3/gdm-x-session[2354]: (II) RADEON(G0): Modeline "1920x1200"x0.0 154.00 1920 1968 2000 2080 1200 1203 1209 1235 +hsync -vsync (74.0 kHz eP) Nov 18 14:00:50 hopa /usr/lib/gdm3/gdm-x-session[2354]: (II) RADEON(G0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) Nov 18 14:00:50 hopa /usr/lib/gdm3/gdm-x-session[2354]: (II) RADEON(G0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) Nov 18 14:00:50 hopa /usr/lib/gdm3/gdm-x-session[2354]: (II) RADEON(G0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) Nov 18 14:00:50 hopa /usr/lib/gdm3/gdm-x-session[2354]: (II) RADEON(G0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e) Nov 18 14:00:50 hopa /usr/lib/gdm3/gdm-x-session[2354]: (II) RADEON(G0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e) Nov 18 14:00:50 hopa /usr/lib/gdm3/gdm-x-session[2354]: (II) RADEON(G0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e) Nov 18 14:00:50 hopa /usr/lib/gdm3/gdm-x-session[2354]: (II) RADEON(G0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) Nov 18 14:00:50 hopa /usr/lib/gdm3/gdm-x-session[2354]: (II) RADEON(G0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e) Nov 18 14:00:50 hopa /usr/lib/gdm3/gdm-x-session[2354]: (II) RADEON(G0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e) Nov 18 14:00:50 hopa /usr/lib/gdm3/gdm-x-session[2354]: (II) RADEON(G0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e) Nov 18 14:00:50 hopa /usr/lib/gdm3/gdm-x-session[2354]: (II) RADEON(G0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e) Nov 18 14:00:50 hopa /usr/lib/gdm3/gdm-x-session[2354]: (II) RADEON(G0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e) Nov 18 14:00:50 hopa /usr/lib/gdm3/gdm-x-session[2354]: (II) RADEON(G0): Modeline "1600x1000"x60.0 133.14 1600 1704 1872 2144 1000 1001 1004 1035 -hsync +vsync (62.1 kHz e) Nov 18 14:00:50 hopa /usr/lib/gdm3/gdm-x-session[2354]: (II) RADEON(G0): Modeline "1600x1200"x0.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e) Nov 18 14:00:50 hopa /usr/lib/gdm3/gdm-x-session[2354]: (II) RADEON(G0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e) Nov 18 14:00:50 hopa kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000041 Nov 18 14:00:50 hopa kernel: IP: [<ffffffffa089abeb>] ttm_bo_wait+0x6b/0x170 [ttm] Nov 18 14:00:50 hopa kernel: PGD 35dba067 PUD 35dbb067 PMD 0 Nov 18 14:00:50 hopa kernel: Oops: 0000 [#1] SMP Nov 18 14:00:50 hopa kernel: Modules linked in: fuse ctr ccm rfcomm ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_addrtype br_netfilter bridge stp llc dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio libcrc32c loop bnep pci_stub vboxpci( Nov 18 14:00:50 hopa kernel: iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass pcspkr psmouse serio_raw sg i2c_i801 lpc_ich shpchp evdev tpm_infineon mei_me mei snd_usb_audio snd_usbmidi_lib snd_rawmidi snd_ Nov 18 14:00:50 hopa kernel: sd_mod rtsx_pci_sdmmc mmc_core crct10dif_pclmul crc32_pclmul crc32c_intel jitterentropy_rng sha256_ssse3 sha256_generic hmac drbg ansi_cprng ahci libahci aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_h Nov 18 14:00:50 hopa kernel: CPU: 2 PID: 4571 Comm: kworker/2:0 Tainted: G W O 4.4.0-rc1+ #2 Nov 18 14:00:50 hopa kernel: Hardware name: Hewlett-Packard HP ZBook 14/198F, BIOS L71 Ver. 01.20 07/28/2014 Nov 18 14:00:50 hopa kernel: Workqueue: events ttm_bo_delayed_workqueue [ttm] Nov 18 14:00:50 hopa kernel: task: ffff8804384d7100 ti: ffff880035e14000 task.ti: ffff880035e14000 Nov 18 14:00:50 hopa kernel: RIP: 0010:[<ffffffffa089abeb>] [<ffffffffa089abeb>] ttm_bo_wait+0x6b/0x170 [ttm] Nov 18 14:00:50 hopa kernel: RSP: 0018:ffff880035e17d70 EFLAGS: 00010246 Nov 18 14:00:50 hopa kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000001 Nov 18 14:00:50 hopa kernel: RDX: 0000000000000ea6 RSI: 0000000000000000 RDI: ffff8800a1626068 Nov 18 14:00:50 hopa kernel: RBP: 0000000000000001 R08: ffff8800a5c5cc78 R09: 0000000000000000 Nov 18 14:00:50 hopa kernel: R10: 0000000000000000 R11: ffff8804300f1dc0 R12: 0000000000000000 Nov 18 14:00:50 hopa kernel: R13: 0000000000000001 R14: ffff8804382d76f8 R15: ffff88031b9b6400 Nov 18 14:00:50 hopa kernel: FS: 0000000000000000(0000) GS:ffff88044ea80000(0000) knlGS:0000000000000000 Nov 18 14:00:50 hopa kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Nov 18 14:00:50 hopa kernel: CR2: 0000000000000041 CR3: 000000043018d000 CR4: 00000000001406e0 Nov 18 14:00:50 hopa kernel: Stack: Nov 18 14:00:50 hopa kernel: 0000000000000ea6 ffff8800a1626068 ffff88044ea959c0 ffff8800a1626068 Nov 18 14:00:50 hopa kernel: 0000000000000001 0000000000000001 ffff880437fcef40 0000000000000000 Nov 18 14:00:50 hopa kernel: 0000000000000001 ffffffffa089b327 0000000000000000 0000000000000001 Nov 18 14:00:50 hopa kernel: Call Trace: Nov 18 14:00:50 hopa kernel: [<ffffffffa089b327>] ? ttm_bo_cleanup_refs_and_unlock+0x27/0x170 [ttm] Nov 18 14:00:50 hopa kernel: [<ffffffffa089b52f>] ? ttm_bo_delayed_delete+0xbf/0x200 [ttm] Nov 18 14:00:50 hopa kernel: [<ffffffffa089b687>] ? ttm_bo_delayed_workqueue+0x17/0x40 [ttm] Nov 18 14:00:50 hopa kernel: [<ffffffff810856ff>] ? process_one_work+0x19f/0x3d0 Nov 18 14:00:50 hopa kernel: [<ffffffff8108597d>] ? worker_thread+0x4d/0x450 Nov 18 14:00:50 hopa kernel: [<ffffffff81085930>] ? process_one_work+0x3d0/0x3d0 Nov 18 14:00:50 hopa kernel: [<ffffffff8108b47d>] ? kthread+0xbd/0xe0 Nov 18 14:00:50 hopa kernel: [<ffffffff8108b3c0>] ? kthread_create_on_node+0x170/0x170 Nov 18 14:00:50 hopa kernel: [<ffffffff8155984f>] ? ret_from_fork+0x3f/0x70 Nov 18 14:00:50 hopa kernel: [<ffffffff8108b3c0>] ? kthread_create_on_node+0x170/0x170 Nov 18 14:00:50 hopa kernel: Code: 85 ff 74 71 41 8b 47 10 ba a6 0e 00 00 85 c0 74 64 31 db eb 0e 83 c3 01 48 85 d2 7e 4f 41 39 5f 10 76 52 48 63 c3 49 8b 6c c7 18 <48> 8b 45 40 a8 01 75 e2 48 8b 45 08 48 8b 40 18 48 85 c0 74 11 Nov 18 14:00:50 hopa kernel: RIP [<ffffffffa089abeb>] ttm_bo_wait+0x6b/0x170 [ttm] Not sure if this particular traceback is associated with all the stalls -- I think that in majority of the cases system stalls before any log/journal gets dumped to the drive so it is not usually accessible after reboot. I also setup xrandr providers to enable external displays connected to the docking station: xrandr --setprovideroffloadsink radeon Intel xrandr --setprovideroutputsource radeon Intel but I think I had stalls prior doing that (but it was with older kernels etc) -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 92722] radeon 0000:01:00.0: VCE init error (-22) on Kernel >= 4.2
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=92722 Bug ID: 92722 Summary: radeon 0000:01:00.0: VCE init error (-22) on Kernel >= 4.2 Product: Mesa Version: 11.0 Hardware: Other OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: lblmr(a)yopmail.com QA Contact: dri-devel(a)lists.freedesktop.org Hey guys, When I run any 4.2 kernel, I get this VCE init error Oct 28 21:44:46 hosty kernel: [drm] PCIE gen 3 link speeds already enabled Oct 28 21:44:46 hosty kernel: [drm] PCIE GART of 2048M enabled (table at 0x0000000000040000). Oct 28 21:44:46 hosty kernel: radeon 0000:01:00.0: WB enabled Oct 28 21:44:46 hosty kernel: radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0xffff88021d960c00 Oct 28 21:44:46 hosty kernel: radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and cpu addr 0xffff88021d960c04 Oct 28 21:44:46 hosty kernel: radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and cpu addr 0xffff88021d960c08 Oct 28 21:44:46 hosty kernel: radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0xffff88021d960c0c Oct 28 21:44:46 hosty kernel: radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and cpu addr 0xffff88021d960c10 Oct 28 21:44:46 hosty kernel: radeon 0000:01:00.0: VCE init error (-22). Oct 28 21:44:46 hosty kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). Oct 28 21:44:46 hosty kernel: [drm] Driver supports precise vblank timestamp query. Oct 28 21:44:46 hosty kernel: radeon 0000:01:00.0: radeon: MSI limited to 32-bit Oct 28 21:44:46 hosty kernel: radeon 0000:01:00.0: radeon: using MSI. Oct 28 21:44:46 hosty kernel: [drm] radeon: irq initialized. More info here: https://bugzilla.redhat.com/show_bug.cgi?id=1262649#c4 -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 92258] Opening context menu in Steam could lead to radeon kernel module crash
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=92258 Bug ID: 92258 Summary: Opening context menu in Steam could lead to radeon kernel module crash Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: russianneuromancer(a)ya.ru Created attachment 118630 --> https://bugs.freedesktop.org/attachment.cgi?id=118630&action=edit dmesg log This crash (please look into attached dmesg) happen hot every time when I open context menu in Steam, but could happen like two times per evening. Since I notice this crash lately, this is probably related to some latest changes in Linux 4.2, but I could be wrong here. On Linux 4.3 this crash is also reproducible. This issue seems like related to DRI_PRIME usage (at least I was unable to easily reproduce this if Steam launched without DRI_PRIME) or maybe to particular GPU model (integrated is 6620G, discrete 6650M). DRI3 and GLAMOR is used, that also may be related. Software: Kubuntu 15.10 x86_64 Mesa: 11.0 libdrm-radeon1: 2.4.64 xserver-xorg-video-radeon: 7.5.0+git20150819 xserver-xorg-core: 1.17.2 Hardware: Acer Aspire 7560G laptop, AMD APU A8-3500M with integrated Radeon HD 6620G (SUMO) Discrete AMD Radeon HD 6650M (TURKS) -- You are receiving this mail because: You are the assignee for the bug.

1 55

[Bug 92086] AMD Trinity No screen at HDMI after S3 wakeup
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=92086 Bug ID: 92086 Summary: AMD Trinity No screen at HDMI after S3 wakeup Product: DRI Version: XOrg git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: vinibali(a)freemail.hu Created attachment 118407 --> https://bugs.freedesktop.org/attachment.cgi?id=118407&action=edit trinity_wakeup.log Dear Devs, ive got this really annoying issue with multiple boards: - ASRock FM2A75 Pro4 - ASRock A88M-HD+ - ASUS A78M-E The simptome is the same in every board, but just with A8-7800K Trinity(ARUBA). I've also tested with A10-7700K Kaveri(GCN1.1), but there was no problems at all. So I put the PC to S3 sleep, than wake it up. The monitor which uses DVI connector, works perfectly, but the HDMI one is mostly black,stays at sleep, doesnt displays information(out of range, etc), but sometimes a really flickering screen comes in for a few momements than disappears. I hope its still a non-listed bug, I've checked multiple reports, but doesnt find thisone. Look at the attachments, dmesg log added. Thanks -- You are receiving this mail because: You are the assignee for the bug.

1 18

[Bug 92060] Noise at the right border of the screen
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=92060 Bug ID: 92060 Summary: Noise at the right border of the screen Product: DRI Version: XOrg git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: romain.failliot(a)foolstep.com Hi! Since I've installed Fedora 22 (3 months ago), I've got this yellow/blue line of noise on the right side of my display. This bug arrives mostly when resuming a session (for instance if I went AFK for an hour, got back and move the mouse). When I take a screenshot, the problem doesn't appear, but here is a photo taken with my cellphone: https://framapic.org/36HIBwrfnlN6/4T82xzGW I'd say that 90% of the times I "wake up" my machine, I've got this bug. I didn't have that on Manjaro before. I have a Radeon HD 6870 with a BenQ GW2765 display (2560x1440), running the open source drivers, of course. I don't know what log file to give that would be interesting for you. But please ask if you need one. Cheers! -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 91961] Hard lock after running built-in radeon.ko tests (Linux kernel 4.2.0)
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=91961 Bug ID: 91961 Summary: Hard lock after running built-in radeon.ko tests (Linux kernel 4.2.0) Product: DRI Version: unspecified Hardware: Other OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: ikalvachev(a)gmail.com Created attachment 118192 --> https://bugs.freedesktop.org/attachment.cgi?id=118192&action=edit Kernel logs from running both test at the same time and from running the second test only.. Built-in tests are enabled by the module "option radeon test=3". The integer value bits are used as flags what test to run on the module load. Running both test takes about 1-2 minutes to complete. The first one turns off the display and trashes the system in a way that the first key pressed hangs it hard - no flashing LEDs, no Magic SysRq. --- The first test moves data from system ram to video ram and back. It runs for about a minute. During that time the monitor is turning off and on again (DELLs do that if DPMS signaling is not exactly right, its on DVI port). The rest of the system seems to function. Boot loading seams to finish and sometimes I can salvage complete kernel message log. Pressing CapsLock turns on its LED, but second press have no effect. Even pressing Magic SysRq first doesn't provide any control of the system. It hangs hard and only reset helps. The seconds test is about syncing between GPU rings. It seems to finish without error if run after the first one. However if I run it alone with "test=2", I get a bunch of timeouts, "GPU lockup" and other errors. When run alone the test doesn't prevent setting of working graphic mode. My videocard is Radeon HD5670 (Redwood). I have confirmation that the same happens on Tahiti chipsets. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 91731] ATI RV250/M9 : screen needs to be refreshed after suspend/resume
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=91731 Bug ID: 91731 Summary: ATI RV250/M9 : screen needs to be refreshed after suspend/resume Product: DRI Version: XOrg git Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: lists.jjorge(a)free.fr It looks like the driver needs a xdamage event to redraw the screen after suspend : if I have two windows opened, then suspend/resume, I get a black screen with only the mouse cursor. Than a simple Alt+Tab draws the screen. How to debug the X event that is waited by the driver? -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 91707] Hibernation doesn't work with AMD Radeon R7 265
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=91707 Bug ID: 91707 Summary: Hibernation doesn't work with AMD Radeon R7 265 Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: rogutes+freedesktop(a)gmail.com Created attachment 117828 --> https://bugs.freedesktop.org/attachment.cgi?id=117828&action=edit dmesg output Hibernation works perfectly when using the integrated Intel GPU, but it only works once when using the discrete AMD Radeon R7 265. I am testing different GPUs by changing the primary GPU in BIOS. When trying to hibernate for the second time, I see one of 2 outcomes: 1. Display powers off, but the system stays on and stops responding to ICMP pings and sysrq; after reset the system boots afresh and fsck is run. 2. System powers off, but doesn't resume on next boot: boots afresh and fsck is run. More observations: * Suspend to RAM works every time. * Hibernation works every time as long as X has not been started. * I am running Arch Linux, swap is on an SSD and not encrypted. I usually start hibernation with `systemctl hibernate`, but writing to /sys/power/state has the same effect. I have no idea how to debug this issue, but would be happy to do it with your help. -- You are receiving this mail because: You are the assignee for the bug.

1 1

← Newer
1
2
3
4
5
6
7
...
124
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel February 2016