dri-devel February 2016

dri-devel@lists.freedesktop.org

180 participants
1240 discussions

[PATCH 0/2] drm/mipi-dsi: support low power transmission
by Inki Dae 20 Nov '19

20 Nov '19

This patch considers low power transmisson to two clock behaviors, non-continuous and continuous clock mode. These two clock behaviors can transmit data in high speed or low power. So this patch series adds a new flag, MIPI_DSI_MODE_LPM so that each host driver can setup its host controller properly. Patch 1: Add MIPI_DSI_MODE_LPM flag. If panel driver sets this flag, then msg->flags will have MIPI_DSI_MSG_USE_LPM so that host driver can transmit data in low power. Patch 2: Just exynos part for supporting non-continuous and continuous clock mode. Inki Dae (2): drm/mipi-dsi: consider low power transmission drm/exynos: mipi-dsi: consider non-continuous clock mode drivers/gpu/drm/drm_mipi_dsi.c | 6 ++++++ drivers/gpu/drm/exynos/exynos_drm_dsi.c | 19 +++++++++++++++++++ include/drm/drm_mipi_dsi.h | 2 ++ 3 files changed, 27 insertions(+) -- 1.7.9.5

3 6

[Bug 80684] New: I2C-over-AUX drops single bytes
by bugzilla-daemon＠freedesktop.org 20 Nov '19

20 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=80684 Priority: medium Bug ID: 80684 Assignee: dri-devel(a)lists.freedesktop.org Summary: I2C-over-AUX drops single bytes Severity: normal Classification: Unclassified OS: All Reporter: stefan.bruens(a)rwth-aachen.de Hardware: Other Status: NEW Version: DRI CVS Component: DRM/Radeon Product: DRI I get frequent errors for the EDID checksum, obviously single bytes are dropped from the EDID. Good EDID: Raw EDID: 02 03 1d f1 50 90 05 04 03 02 07 16 01 06 11 12 15 13 14 1f 20 23 09 7f 07 83 01 00 00 02 3a 80 18 71 38 2d 40 58 2c 25 00 55 50 21 00 00 1e 01 1d 80 18 71 1c 16 20 58 2c 25 00 55 50 21 00 00 <-- 9e 01 1d 00 72 51 d0 1e 20 6e 28 55 00 55 50 21 00 00 1e 8c 0a d0 8a 20 e0 2d 10 10 3e 96 00 55 50 21 00 00 18 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 5d Bad EDID example: Raw EDID: 02 03 1d f1 50 90 05 04 03 02 07 16 01 06 11 12 15 13 14 1f 20 23 09 7f 07 83 01 00 00 02 3a 80 18 71 38 2d 40 58 2c 25 00 55 50 21 00 00 1e 01 1d 80 18 1c 16 20 58 2c 25 00 55 50 21 00 00 9e <-- 0x71 is missing 01 1d 00 72 51 d0 1e 20 6e 28 55 00 55 50 21 00 00 1e 8c 0a d0 8a 20 e0 2d 10 10 3e 96 00 55 50 21 00 00 18 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 5d 00 The position of the dropped byte changes, sometimes the EDID is complete, sometimes several bytes are dropped. The bad EDIDs are *often* accompanied with [drm:radeon_process_aux_ch] dp_aux_ch flags not zero messages. Most probably the common i2c-over-aux code drops the byte, as it starts the transfer again in case of -EBUSY. If I change radeon_process_aux_ch to return -EIO in case of (ReplyStatus == 2), I no longer have any bad checksums. Hardware is Radeon 7750 + Dell U2713HM, connected via DP. Same monitor with Intel Haswell and different cable works without any errors. Kernel is 3.15.1, i.e. without the i2c bus mutex, dont know if this fixes the problems as well. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 92977] Display artifacts when using MST
by bugzilla-daemon＠freedesktop.org 20 Nov '19

20 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=92977 Bug ID: 92977 Summary: Display artifacts when using MST 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: dan.doel(a)gmail.com Created attachment 119730 --> https://bugs.freedesktop.org/attachment.cgi?id=119730&action=edit image 1 - half of window uses different colors I've been trying out the support for tiled MST monitors on Radeon drivers, and seem to be encountering some visual anomalies that seem like they are likely to be related to this component. My setup is two UP2414Q monitors, which have native resolutions of 3840x2160. Over DisplayPort 1.2, they are capable of running as two 1920x2160@60 displays each. I have a nvidia card that is capable of driving them in this mode, so I am reasonably sure that the hardware isn't the problem (unless it is the Radeon card, but that seems unlikely). First, there seems to be a color anomaly with the primary display. The right half of the display has different colors from the left (see first image). I noticed that this may be due to the left half displaying a different color depth than the right. The second image shows the gnome overlay, and while the shadows are smooth on the right, there is banding on the left. My second monitor seems to have both sides in this reduced color mode, and enough fiddling with settings after a boot causes both halves of the primary monitor to be configured that way as well, but needless to say, the reduced color depth (if that's what it is) is undesirable. Second, the secondary monitor has some visual artifacts to the left of center (a vertical band about an inch wide) as well as to the far right (a vertical band around 1/4 inch wide). The third image should give some idea what it looks like. A better photo might show that things in that region look somewhat interlaced, and are repeated horizontally. I apologize for the poor quality of the images, but screenshots don't capture these artifacts, so I had to use my phone. I'm running with packages from Fedora 23, so xorg-server 1.18.0, xf86-video-ati 7.6.0-0.4.20150729git5510cd6, kernel 4.2.5-300. If you'd like any other information, let me know. -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 32556] New: screen flickers all the time with desktop image appearing only briefly
by bugzilla-daemon＠freedesktop.org 20 Nov '19

20 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=32556 Summary: screen flickers all the time with desktop image appearing only briefly Product: DRI Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: critical Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: 3ntr0p13(a)gmail.com Created an attachment (id=41344) --> (https://bugs.freedesktop.org/attachment.cgi?id=41344) dmesg Machine is the same as in bug report 28331 although with different software components: Acer Aspire L5100 with an AMD Athlon 64 X2 Dual Core Processor 4000+, this time running a 64 bits debian squeeze. The machine is a small factor desktop machine designed around laptop components, so the graphic card is an integrated radeon x1200. When running a linux vanilla kernel 2.6.37-rc6, the screen flickers all the time making the machine unusable, while with debian kernel 2.6.32-5 such "flick to black" event occur from time to time, making it annoying but usable. While booting with radeon.modeset=0 the problem doesn't exhibits itself The following packages version from debian squeeze are installed: xserver-xorg 1:7.5+8 xserver-xorg-core 2:1.7.7-10 xserver-xorg-video-radeon 1:6.13.1-2+squeeze1 Please find attached Xorg.0.log, dmesg, register dumps for ums and kms for that machine (when booted on 2.6.37-rc6). Regards, Gildas -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 38

[Bug 32422] New: Large images displayed in Firefox appear corrupted
by bugzilla-daemon＠freedesktop.org 20 Nov '19

20 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=32422 Summary: Large images displayed in Firefox appear corrupted 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: da_fox(a)mad.scientist.com Created an attachment (id=41150) --> (https://bugs.freedesktop.org/attachment.cgi?id=41150) Picture describing a thousand words. "A picture says more than a thousand words" (aka see attachment) This is what happens when I try to view the XKCD "Online Communities 2" map (http://xkcd.com/802_large/) or other large images in firefox. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 21

[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 93895] GPU lockup on AMD A4-3400 APU when starting X server on opensource drivers. (works fine with fglrx)
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=93895 Bug ID: 93895 Summary: GPU lockup on AMD A4-3400 APU when starting X server on opensource drivers. (works fine with fglrx) 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: azari4096(a)gmail.com I've had this lockup on this machine for the past few years, across several different kernel versions, different distributions, etc. Booting with KMS works fine, but the second a graphical environment starts (whether X or wayland-based), it locks up. Booting Ubuntu with user-space mode-setting works, and then I can install FGLRX from there and everything works fine. After speaking with airlied on IRC, they suggested it could be a workaround that AMD has put into FGLRX that never made it into the opensource drivers, and that AMD might have to look into it. CPU/GPU : A4-3400 Motherboard : GA-A75M-D2H ( http://www.gigabyte.com/products/product-page.aspx?pid=3930#ov ) journalctl log of the lockup: ------------------------------------------------------------ Jan 27 18:28:32 miku dbus-daemon[374]: Successfully activated service 'org.freedesktop.systemd1' Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: ring 0 stalled for more than 10000msec Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GPU lockup (current fence id 0x0000000000000001 last fence id 0x0000000000000003 on ring 0) Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: Saved 55 dwords of commands on ring 0. Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GPU softreset: 0x00000009 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GRBM_STATUS = 0xB1403828 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GRBM_STATUS_SE0 = 0x28000007 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GRBM_STATUS_SE1 = 0x00000007 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: SRBM_STATUS = 0x20000840 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: SRBM_STATUS2 = 0x00000000 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: R_008674_CP_STALLED_STAT1 = 0x00000000 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: R_008678_CP_STALLED_STAT2 = 0x40000000 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: R_00867C_CP_BUSY_STAT = 0x00008000 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: R_008680_CP_STAT = 0x80228643 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GRBM_SOFT_RESET=0x00007F6B Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: SRBM_SOFT_RESET=0x00000100 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GRBM_STATUS = 0x00003828 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GRBM_STATUS_SE0 = 0x00000007 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GRBM_STATUS_SE1 = 0x00000007 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: SRBM_STATUS = 0x20000040 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: SRBM_STATUS2 = 0x00000000 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: R_008674_CP_STALLED_STAT1 = 0x00000000 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: R_008678_CP_STALLED_STAT2 = 0x00000000 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: R_00867C_CP_BUSY_STAT = 0x00000000 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: R_008680_CP_STAT = 0x00000000 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: GPU reset succeeded, trying to resume Jan 27 18:28:42 miku kernel: [drm] Found smc ucode version: 0x00011100 Jan 27 18:28:42 miku kernel: [drm] PCIE GART of 1024M enabled (table at 0x0000000000274000). Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: WB enabled Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: fence driver on ring 0 use gpu addr 0x0000000020000c00 and cpu addr 0xffff8800c613fc00 Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: fence driver on ring 3 use gpu addr 0x0000000020000c0c and cpu addr 0xffff8800c613fc0c Jan 27 18:28:42 miku kernel: radeon 0000:00:01.0: fence driver on ring 5 use gpu addr 0x0000000000072118 and cpu addr 0xffffc90002432118 Jan 27 18:28:42 miku kernel: [drm] ring test on 0 succeeded in 1 usecs Jan 27 18:28:42 miku kernel: [drm] ring test on 3 succeeded in 3 usecs Jan 27 18:28:42 miku kernel: [drm] ring test on 5 succeeded in 1 usecs Jan 27 18:28:42 miku kernel: [drm] UVD initialized successfully. Jan 27 18:28:52 miku kernel: radeon 0000:00:01.0: ring 0 stalled for more than 10370msec Jan 27 18:28:52 miku kernel: radeon 0000:00:01.0: GPU lockup (current fence id 0x0000000000000002 last fence id 0x0000000000000004 on ring 0) Jan 27 18:28:52 miku kernel: [drm:r600_ib_test [radeon]] *ERROR* radeon: fence wait failed (-35). Jan 27 18:28:52 miku kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on GFX ring (-35). Jan 27 18:29:22 miku systemd[1]: Started Getty on tty2. ------------------------------------------------------------ -- You are receiving this mail because: You are the assignee for the bug.

1 11

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel February 2016