dri-devel January 2017

dri-devel@lists.freedesktop.org

240 participants
1484 discussions

[Bug 97157] MST displays fail to wake
by bugzilla-daemon＠freedesktop.org 20 Nov '19

20 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=97157 Bug ID: 97157 Summary: MST displays fail to wake Product: DRI Version: XOrg git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: dan.doel(a)gmail.com Created attachment 125450 --> https://bugs.freedesktop.org/attachment.cgi?id=125450&action=edit dmesg output Since moving to kernel 4.6, I've been having regular problems with my MST monitors failing to wake after being put to sleep. This only seems to occur after the machine has been on for a sufficient amount of time, but I usually experience it within a day of booting, and typically after the displays have been powered off for an extended period of time. There are two MST monitors, but typically only one fails to wake. Also, it is more often that the secondary display is the one that fails. However, I have had the primary display fail to come back (while the secondary one succeeds), and I have had both fail to come back as well. Sometimes, only a complete power off is able to make the monitors wake up; a reboot is not always sufficient. The dmesg displays some errors, and I've poked around a bit. It seems likely that this is related to commit f3d58dccdbf9f8c0a229d555d4b295d52e743039, which was first included in 4.6. This commit basically causes dpms to work at all with MST monitors; before it was a no-op that didn't actually put the monitors into power saving. That doesn't help narrow the problem down much, though, since a significant portion of the mst dpms code probably wasn't being exercised before that. Also, it seems notable that the error message (which seems more like a debug message) in the STANDBY/SUSPEND/OFF case keeps reporting higher numbers, as though it keeps going through the ON case, which increments the variable, but not making it through the portion of the OFF case that decrements the variable. I'll attach dmesg journal output that might be relevant. I believe the error/debug messages timestamped 'Jul 31 11:03:49' correspond to the first time one of the displays failed to wake up. I tried various ways of toggling the dpms off and on after that, so those are the subsequent error messages in the log. As far as specs go, I have: Radeon HD7870 (Pitcairn) Kernel 4.6.4 (4.6.3 also affected) 2 UP2414Q mst displays xorg-server 1.18.4 Modesetting driver Let me know if there's any more information I can try to provide. -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 94153] Unresponsive system on boot with radeon + HD 3870
by bugzilla-daemon＠freedesktop.org 20 Nov '19

20 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=94153 Bug ID: 94153 Summary: Unresponsive system on boot with radeon + HD 3870 Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: blocker Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: g47qk(a)ukr.net Created attachment 121755 --> https://bugs.freedesktop.org/attachment.cgi?id=121755&action=edit dmesg.log saved via the serial port I'm using a HD 3870 with Debian 9 Stretch x64 (Testing). When booting to a command line, when drivers are loaded, the screen goes into power saving mode, and the system becomes unresponsive. Booting with `nomodeset' works OK. If I run "#modprobe radeon modeset=1", the screen goes power saving mode, the system stops responding and the caps lock key no longer works (kernel panic?). I've also tested with a Fedora 23 Workstation Live-CD (64-bit), Ubuntu 15.10 Desktop (64-bit) Live-CD, SystemRescueCd-x86-4.7.0 with the same results (unresponsive on driver load). I've tested a ATI X1600 Pro in the same system, and everything works fine. #lspci -nnn | grep VGA 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] RV670 [Radeon HD 3870] [1002:9501] -- You are receiving this mail because: You are the assignee for the bug.

1 13

[Bug 89971] HDMI out *not* working with radeon (mobile 8550g)
by bugzilla-daemon＠freedesktop.org 20 Nov '19

20 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=89971 Bug ID: 89971 Summary: HDMI out *not* working with radeon (mobile 8550g) Product: DRI Version: DRI git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: adrianovidiugabor(a)gmail.com Created attachment 114999 --> https://bugs.freedesktop.org/attachment.cgi?id=114999&action=edit screen's content Hi all. If I'm connecting my laptop's HDMI out to my TV I get a black screen with garbage on top (see attached pic). This is with mirror mode on. If making the second screen primary, the pc blocks and I have to restart it. It won't unblock even if I disconnect the cable. If switching to one of the virtual consoles, everything works correctly as it should, so the problem seems to be related somehow to the display server. The Tv is recognized correctly by xrandr. Specs: Asus laptop, with AMD A8-5550M, Radeon 8550G(Aruba)/8670M(Hainan), OS ArchLinux(x64) Xorg-xerver 1.17, kernel 3.19.3, Mesa-git, xf86-ati-git, llvm-svn. This doesn't seem to be a regression (experienced it with older versions of the kernel and userspace components) and it's reproducible on another machine. HDMI out works on Windows and ChromeOS. Didn't try Catalyst on Linux. -- You are receiving this mail because: You are the assignee for the bug.

1 15

[Bug 80531] New: 3.16-rc2 hdmi output resolution out of range Cape Verde PRO [Radeon HD 7750]
by bugzilla-daemon＠freedesktop.org 20 Nov '19

20 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=80531 Priority: medium Bug ID: 80531 Assignee: dri-devel(a)lists.freedesktop.org Summary: 3.16-rc2 hdmi output resolution out of range Cape Verde PRO [Radeon HD 7750] Severity: normal Classification: Unclassified OS: Linux (All) Reporter: fredrik(a)obra.se Hardware: x86-64 (AMD64) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Created attachment 101759 --> https://bugs.freedesktop.org/attachment.cgi?id=101759&action=edit dmesg with drm.debug=1 With 3.16-rc2 my tripple screen setup breaks. DisplayPort-0 connected 1920x1200 <- ok HDMI-0 connected 1920x1080 <- (tv) resolution out of range DVI-0 connected 1680x1050 <- ok All screens work during bootup before X starts. ddx driver 7.3.0. -- You are receiving this mail because: You are the assignee for the bug.

1 14

[Bug 75992] New: Display freezes & corruption with an r7 260x on 3.14-rc6
by bugzilla-daemon＠freedesktop.org 20 Nov '19

20 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=75992 Priority: medium Bug ID: 75992 Assignee: dri-devel(a)lists.freedesktop.org Summary: Display freezes & corruption with an r7 260x on 3.14-rc6 Severity: major Classification: Unclassified OS: Linux (All) Reporter: edt(a)aei.ca Hardware: x86-64 (AMD64) Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI Created attachment 95520 --> https://bugs.freedesktop.org/attachment.cgi?id=95520&action=edit log of boot I recently added a R7 260X to my system. While the card works with 3.13 its supposed work much better with 14-rc. This is not the case. My system is unstable without radeon.dpm=0 which was the default in .13. linux 3.14-rc6 (with an up to date arch, stable X and mesa-git (10.2) mesa 10.1 and 10.0 also show very similar problems. When X started I did notice some corruption. There are sets of two rectangles about of a height of 2 or 3 mm, width of 25m or so with a second about a cm below. The often occurs in chomium especially when scrolling. Runing the unigine-sanctuary or unigine-tropics demo/benchmark programs also produce the above problems and eventually stall. -- You are receiving this mail because: You are the assignee for the bug.

1 61

[Bug 99368] Full aspect scaling introduces interlacing on specific resolutions
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=99368 Bug ID: 99368 Summary: Full aspect scaling introduces interlacing on specific resolutions 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: gamwizh00(a)gmail.com Created attachment 128897 --> https://bugs.freedesktop.org/attachment.cgi?id=128897&action=edit dmesg log When using full aspect scaling in xrandr on a laptop with an A6-6310 apu the display is showing interlaced lines across the whole display. This happens only on some of the supported resolutions of the integrated display, those being 1280x720 and 1152x768. -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 99326] Boot problem and White dots/noise/speckling/shimmering/corruption on Radeon HD6320
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=99326 Bug ID: 99326 Summary: Boot problem and White dots/noise/speckling/shimmering/corruption on Radeon HD6320 Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: mrj(a)advancedcontrols.com.au A default Gnome install of either Fedora 25 or Fedora 24 (latest spin) Workstation, on a machine with a Radeon HD6320 (AMD G-series T56N) graphics chip running 1360x768@60Hz, has a display that most of the time is black on boot (reboot required -- hangs?), but occasionally completes booting with a display that all over shimmers with white noise, as seen in the following video: https://www.youtube.com/watch?v=dHW6kM4koQ0 The problem has been traced to this Linux kernel commit https://github.com/torvalds/linux/commit/ff0bd441bdfbfa09d05fdba9829a0401a4… , made to fix Bug 95206. Xorg logs and xrandr output seem to indicate the the same modeline is selected after this commit is reversed, even though the boot and display problems no longer occur. The equivalent Red Hat bug is https://bugzilla.redhat.com/show_bug.cgi?id=1402293 -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 99316] Radeon crash when laptop on AC power
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=99316 Bug ID: 99316 Summary: Radeon crash when laptop on AC power Product: DRI Version: unspecified Hardware: Other OS: All Status: NEW Severity: major Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: LordSamanon(a)gmail.com Created attachment 128807 --> https://bugs.freedesktop.org/attachment.cgi?id=128807&action=edit AC Power Unigine Heaven dmesg I have a Dell laptop with an Intel iGPU and a Radeon dGPU (a Firepro W5130M, recognized as a Radeon HD 8830M by lspci). Whenever I attempt to use the Radeon card via DRI_PRIME=1 while the laptop is plugged in, the card crashes. When on battery the card performs fine. One way I have tested this is with glxgears. Often glxgears will work the first time it is run, but if it is closed and then opened a few seconds later, it will crash. I have also tried running programs like Portal 2 and Unigine Heaven. These always hang. Unfortunately the error messages produced in dmesg are not the most consistent. Sometimes I get a backtrace, sometimes even a kernel panic on reboot. I'll post the various logs I have. One thing I have found is that glxgears does not crash if I use radeon.runpm=0, however it still hangs when running something like Portal. -- You are receiving this mail because: You are the assignee for the bug.

1 16

[Bug 99181] RS780 blank screen on boot
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=99181 Bug ID: 99181 Summary: RS780 blank screen on boot 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: chithanh(a)gentoo.org Hardware: BIOSTAR A780L When booting with 3.15 or newer kernels, a monitor connected to the DVI port of the BIOSTAR A780L will stay blank. Kernel 3.14 and older work fine. I tried forcing the output to on with video=HDMI-A-1:e but this made no difference. -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 99049] Machine freeze when clock are set to defaults
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=99049 Bug ID: 99049 Summary: Machine freeze when clock are set to defaults 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: ls(a)maxux.net My laptop contains theses cards: ---- 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07) 01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330] (rev 81) ---- Under Gentoo, I enabled radeon and radeonsi as videos cards, everything looks fine. According to xrandr, I have providers: ---- Provider 0: id: 0x76 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 4 outputs: 3 associated providers: 0 name:Intel Provider 1: id: 0x4f cap: 0xd, Source Output, Source Offload, Sink Offload crtcs: 0 outputs: 0 associated providers: 0 name:HAINAN @ pci:0000:01:00.0 ---- I found on the internet that DPM could cause issue, I tried: radeon.runpm=0 radeon.dpm=0 (see below) Using theses settings, I don't have any freeze when I try to use the Radeon Card (using DRI_PRIME=1), but I found that everything was slow. I checked, and I saw: --- cat /sys/class/drm/card1/device/power_method profile cat /sys/class/drm/card1/device/power_profile default cat /sys/kernel/debug/dri/65/radeon_pm_info default engine clock: 1070000 kHz current engine clock: 299990 kHz default memory clock: 900000 kHz current memory clock: 298990 kHz voltage: 1150 mV PCIE lanes: 4 --- The card is running in low profile by default, don't know why. Setting power_profile to high, mid or low doesn't change anything, but if I set power_profile back to default again, the clock is set to full speed. When clock is set to full speed, my system freeze if I try to run any 3D application (glxgears or a game using wine). Here is the dmesg log: --- radeon 0000:01:00.0: ring 0 stalled for more than 10436msec radeon 0000:01:00.0: GPU lockup (current fence id 0x00000000000014f4 last fence id 0x00000000000014f6 on ring 0) radeon 0000:01:00.0: Saved 49 dwords of commands on ring 0. radeon 0000:01:00.0: GPU softreset: 0x00000049 radeon 0000:01:00.0: GRBM_STATUS = 0xE5D04028 radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0xEE400000 radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000006 radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00018000 radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00008000 radeon 0000:01:00.0: R_008680_CP_STAT = 0x80030243 radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57 radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 radeon 0000:01:00.0: GRBM_SOFT_RESET=0x0000DDFF radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100 radeon 0000:01:00.0: GRBM_STATUS = 0x00003028 radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000006 radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000006 radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000 radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57 radeon 0000:01:00.0: GPU reset succeeded, trying to resume [drm] probing gen 2 caps for device 8086:9d10 = 1724843/e [drm] PCIE gen 3 link speeds already enabled [drm] PCIE GART of 2048M enabled (table at 0x0000000000040000). radeon 0000:01:00.0: WB enabled radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000100000c00 and cpu addr 0xffff88046c66dc00 radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000100000c04 and cpu addr 0xffff88046c66dc04 radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000100000c08 and cpu addr 0xffff88046c66dc08 radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000100000c0c and cpu addr 0xffff88046c66dc0c radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000100000c10 and cpu addr 0xffff88046c66dc10 [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x850C)=0xCAFEDEAD) [drm:si_resume [radeon]] *ERROR* si startup failed on resume --- I found out with theses steps that, if I don't set dpm=0, I hit exactly the same issue, I guess using DPM the clock is set to high when the card is used and it crash. When the card is stuck on that loop, I need to reset the machine (but network still works). I'm using mesa-13.0.2 with a 4.7.6 kernel, I have the same issue using mesa 12.0.1 -- You are receiving this mail because: You are the assignee for the bug.

1 4

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel January 2017