dri-devel December 2015

dri-devel@lists.freedesktop.org

162 participants
1148 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 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 93525] [drm:evergreen_resume [radeon]] *ERROR* evergreen startup failed on resume
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=93525 Bug ID: 93525 Summary: [drm:evergreen_resume [radeon]] *ERROR* evergreen startup failed on resume 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: rafaelrcenteio(a)gmail.com Created attachment 120720 --> https://bugs.freedesktop.org/attachment.cgi?id=120720&action=edit dmesg output. I am receiving the following message on boot: "[ 13.198262] [drm:evergreen_resume [radeon]] *ERROR* evergreen startup failed on resume" uname -a Linux rafael 4.2.0-0.bpo.1-amd64 #1 SMP Debian 4.2.6-3~bpo8+2 (2015-12-14) x86_64 GNU/Linux lspci In attachment: dmesg's output. >From dmidecode: Vendor: Hewlett-Packard Version: F.48 Release Date: 11/09/2011 ROM Size: 2048 kB ... BIOS Revision: 15.48 Firmware Revision: 60.80 Worth mentioning that the behaviour of the fans and the temperatures change a lot after suspension/hibernation. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 93452] kernel crash(3.19 up) DRI_PRIME=1 HP zbook 14
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=93452 Bug ID: 93452 Summary: kernel crash(3.19 up) DRI_PRIME=1 HP zbook 14 Product: DRI Version: XOrg git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: lathanderjk(a)gmail.com I have issue with new kernels since 3.19 up 4.1 distribution openSUSE/Fedora but on Arch works stable for some reasons. Kernels crash when i use DRI_PRIME=1 after few minutes (max. 7) and kdump is not created. I try openSUSE leap with old 3.16.7 and works fine also try AMD only configuration(AMD as primary GPU) and also works fine. 4.2.5/4.3.0 DRI_PRIME=1 works different , crashing randomly ( two times during day test) Some more info https://bugzilla.opensuse.org/show_bug.cgi?id=954783 (drm.debug=0x0e,dmesg -n 8) openSUSE 4.1.13 [ 147.171197] [drm:i915_gem_open] [ 156.538080] [drm] probing gen 2 caps for device 8086:9c18 = 5323c42/0 [ 156.538093] [drm] PCIE gen 2 link speeds already enabled [ 156.542218] [drm] PCIE GART of 1024M enabled (table at 0x0000000000277000). [ 156.542345] radeon 0000:03:00.0: WB enabled [ 156.542349] radeon 0000:03:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff880036d62c00 [ 156.542351] radeon 0000:03:00.0: fence driver on ring 1 use gpu addr 0x0000000040000c04 and cpu addr 0xffff880036d62c04 [ 156.542354] radeon 0000:03:00.0: fence driver on ring 2 use gpu addr 0x0000000040000c08 and cpu addr 0xffff880036d62c08 [ 156.542356] radeon 0000:03:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff880036d62c0c [ 156.542358] radeon 0000:03:00.0: fence driver on ring 4 use gpu addr 0x0000000040000c10 and cpu addr 0xffff880036d62c10 [ 156.543910] radeon 0000:03:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc90001435a18 [ 156.544585] [drm:radeon_crtc_handle_flip] radeon_crtc->flip_status = 0 != RADEON_FLIP_SUBMITTED(2) [ 156.544592] [drm:radeon_crtc_handle_flip] radeon_crtc->flip_status = 0 != RADEON_FLIP_SUBMITTED(2) [ 156.781101] [drm] ring test on 0 succeeded in 1 usecs [ 156.781114] [drm] ring test on 1 succeeded in 1 usecs [ 156.781121] [drm] ring test on 2 succeeded in 1 usecs [ 156.781131] [drm] ring test on 3 succeeded in 5 usecs [ 156.781140] [drm] ring test on 4 succeeded in 4 usecs [ 156.956763] [drm] ring test on 5 succeeded in 2 usecs [ 156.956772] [drm] UVD initialized successfully. [ 156.956811] [drm] ib test on ring 0 succeeded in 0 usecs [ 156.956858] [drm] ib test on ring 1 succeeded in 0 usecs [ 156.956901] [drm] ib test on ring 2 succeeded in 0 usecs [ 156.956932] [drm] ib test on ring 3 succeeded in 0 usecs [ 156.956966] [drm] ib test on ring 4 succeeded in 0 usecs [ 157.605812] [drm] ib test on ring 5 succeeded [ 157.614315] snd_hda_intel 0000:03:00.1: Enabling via VGA-switcheroo [ 157.719256] snd_hda_intel 0000:03:00.1: CORB reset timeout#2, CORBRP = 65535 [ 157.765449] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 163.932378] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 167.286021] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 171.125632] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 174.384673] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 177.111597] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 180.648221] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 183.863776] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 187.519144] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 191.038127] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! --and crash 3.16.7 (stable) [ 75.808416] [drm:intel_crtc_cursor_set] cursor off [ 76.279634] [drm] probing gen 2 caps for device 8086:9c18 = 5323c42/0 [ 76.279644] [drm] PCIE gen 2 link speeds already enabled [ 76.283764] [drm] PCIE GART of 1024M enabled (table at 0x0000000000276000). [ 76.283904] radeon 0000:03:00.0: WB enabled [ 76.283908] radeon 0000:03:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff880238c1dc00 [ 76.283910] radeon 0000:03:00.0: fence driver on ring 1 use gpu addr 0x0000000040000c04 and cpu addr 0xffff880238c1dc04 [ 76.283912] radeon 0000:03:00.0: fence driver on ring 2 use gpu addr 0x0000000040000c08 and cpu addr 0xffff880238c1dc08 [ 76.283915] radeon 0000:03:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff880238c1dc0c [ 76.283917] radeon 0000:03:00.0: fence driver on ring 4 use gpu addr 0x0000000040000c10 and cpu addr 0xffff880238c1dc10 [ 76.285473] radeon 0000:03:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc90011135a18 [ 76.286084] [drm:radeon_crtc_handle_flip] radeon_crtc->flip_status = 0 != RADEON_FLIP_SUBMITTED(2) [ 76.286089] [drm:radeon_crtc_handle_flip] radeon_crtc->flip_status = 0 != RADEON_FLIP_SUBMITTED(2) [ 76.481930] [drm] ring test on 0 succeeded in 1 usecs [ 76.481942] [drm] ring test on 1 succeeded in 1 usecs [ 76.481948] [drm] ring test on 2 succeeded in 1 usecs [ 76.481956] [drm] ring test on 3 succeeded in 4 usecs [ 76.481964] [drm] ring test on 4 succeeded in 4 usecs [ 76.667487] [drm] ring test on 5 succeeded in 2 usecs [ 76.667497] [drm] UVD initialized successfully. [ 76.667531] [drm] ib test on ring 0 succeeded in 0 usecs [ 76.667561] [drm] ib test on ring 1 succeeded in 0 usecs [ 76.667589] [drm] ib test on ring 2 succeeded in 0 usecs [ 76.667617] [drm] ib test on ring 3 succeeded in 0 usecs [ 76.667644] [drm] ib test on ring 4 succeeded in 0 usecs [ 76.818256] [drm] ib test on ring 5 succeeded [ 76.827403] snd_hda_intel 0000:03:00.1: Enabling via VGA-switcheroo [ 76.827546] snd_hda_intel 0000:03:00.1: irq 69 for MSI/MSI-X [ 76.861702] [drm:radeon_info_ioctl] Invalid request 37 [ 76.861713] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 79.192677] [drm:radeon_info_ioctl] Invalid request 37 [ 79.192690] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 83.737880] [drm:radeon_info_ioctl] Invalid request 37 [ 83.737892] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 89.062058] [drm:radeon_info_ioctl] Invalid request 37 [ 89.062070] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 93.254184] [drm:radeon_info_ioctl] Invalid request 37 [ 93.254197] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 96.922265] [drm:radeon_info_ioctl] Invalid request 37 [ 96.922280] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 101.272998] [drm:radeon_info_ioctl] Invalid request 37 [ 101.273015] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 104.574944] [drm:radeon_info_ioctl] Invalid request 37 [ 104.574969] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 108.408574] [drm:radeon_info_ioctl] Invalid request 37 [ 108.408597] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 111.561355] [drm:radeon_info_ioctl] Invalid request 37 [ 111.561369] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 117.931164] [drm:intel_crtc_cursor_set] cursor off [ 123.179592] [drm:intel_crtc_cursor_set] cursor off [ 130.923942] [drm:intel_crtc_cursor_set] cursor off And 4.1.15 on Arch (stable) [ 451.911996] [drm] probing gen 2 caps for device 8086:9c18 = 5323c42/0 [ 451.912004] [drm] PCIE gen 2 link speeds already enabled [ 451.916190] [drm] PCIE GART of 1024M enabled (table at 0x0000000000277000). [ 451.916363] radeon 0000:03:00.0: WB enabled [ 451.916366] radeon 0000:03:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff88023eb98c00 [ 451.916368] radeon 0000:03:00.0: fence driver on ring 1 use gpu addr 0x0000000040000c04 and cpu addr 0xffff88023eb98c04 [ 451.916369] radeon 0000:03:00.0: fence driver on ring 2 use gpu addr 0x0000000040000c08 and cpu addr 0xffff88023eb98c08 [ 451.916371] radeon 0000:03:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff88023eb98c0c [ 451.916373] radeon 0000:03:00.0: fence driver on ring 4 use gpu addr 0x0000000040000c10 and cpu addr 0xffff88023eb98c10 [ 451.917925] radeon 0000:03:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc90004435a18 [ 451.918490] [drm:radeon_crtc_handle_flip] radeon_crtc->flip_status = 0 != RADEON_FLIP_SUBMITTED(2) [ 451.918494] [drm:radeon_crtc_handle_flip] radeon_crtc->flip_status = 0 != RADEON_FLIP_SUBMITTED(2) [ 452.156274] [drm] ring test on 0 succeeded in 1 usecs [ 452.156282] [drm] ring test on 1 succeeded in 1 usecs [ 452.156287] [drm] ring test on 2 succeeded in 1 usecs [ 452.156297] [drm] ring test on 3 succeeded in 5 usecs [ 452.156305] [drm] ring test on 4 succeeded in 5 usecs [ 452.333329] [drm] ring test on 5 succeeded in 2 usecs [ 452.333338] [drm] UVD initialized successfully. [ 452.333379] [drm] ib test on ring 0 succeeded in 0 usecs [ 452.333412] [drm] ib test on ring 1 succeeded in 0 usecs [ 452.333443] [drm] ib test on ring 2 succeeded in 0 usecs [ 452.333474] [drm] ib test on ring 3 succeeded in 0 usecs [ 452.333504] [drm] ib test on ring 4 succeeded in 0 usecs [ 452.982823] [drm] ib test on ring 5 succeeded [ 452.989772] snd_hda_intel 0000:03:00.1: Enabling via VGA-switcheroo [ 453.094277] snd_hda_intel 0000:03:00.1: CORB reset timeout#2, CORBRP = 65535 [ 453.120392] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 453.192020] [drm:drm_mode_addfb2] [FB:75] [ 466.009035] snd_hda_intel 0000:03:00.1: Disabling via VGA-switcheroo -- You are receiving this mail because: You are the assignee for the bug.

1 5

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel December 2015