dri-devel June 2018

dri-devel@lists.freedesktop.org

241 participants
1687 discussions

[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 105433] Unreliable Modesetting on Tonga with two DVI Screens
by bugzilla-daemon＠freedesktop.org 20 Nov '19

20 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=105433 Bug ID: 105433 Summary: Unreliable Modesetting on Tonga with two DVI Screens Product: DRI Version: DRI git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: freedesktop-bugs(a)digital-trauma.de Two devices connected via DVI, one not coming up (powersave, no signal). On retry , they may swap their working state, or both go to energy save, or rarely, both work. This happens regardless of resolutions set on the screens in question. Screens: 2 x Benq G2222HDL Connected via DVI (both straight to card) Card: ASUS Strix R9285 DC2OC 2GD5 Kernel: amd-staging-drm-next 6e62bc7a123b "drm/amdgpu:Always save uvd vcpu_bo in VM Mode" Bug report as discussed in bug 100919. Possibly related to bug 91202. -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 107079] Black screen after waking from sleep
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=107079 Bug ID: 107079 Summary: Black screen after waking from sleep Product: DRI Version: unspecified Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: g.goltsov(a)gmail.com Created attachment 140397 --> https://bugs.freedesktop.org/attachment.cgi?id=140397&action=edit uname -a After waking from sleep I get black screen on my notebook regardless of whether x-server was starting or no. I am able to type commands blindly. I can also connect to system via ssh. But after adding "nomodeset" to kernel params system suspend and resume work correctly. I probed linux kernels 4.9 and 4.16. I also compiled modules radeon,drm,ttm from recent sources. Situation did not change. -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 106474] "CPU1 stuck for XXs: Xorg" since update to linux-4.16.x
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=106474 Bug ID: 106474 Summary: "CPU1 stuck for XXs: Xorg" since update to linux-4.16.x 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: linuxhippy(a)gmail.com Created attachment 139489 --> https://bugs.freedesktop.org/attachment.cgi?id=139489&action=edit screenshot After updating the Laptop of a friend running Fedora 27 to linux-4.16.4/5/6 it frequently gets stuck when starting Xorg - please see the attached screenshot. The machine is a AMD Beema based Hewlett-Packard HP 355 G2/22C1, BIOS F.10 02/12/2015 running the latest Fedora 27 packages. Graphics stack is default (glamor, radeon kernel module). Linux-4.15.17 works absolutly flawless. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 106471] Radeon HD 3450 acceleration not working
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=106471 Bug ID: 106471 Summary: Radeon HD 3450 acceleration not working 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: jjcogliati-r1(a)yahoo.com Created attachment 139483 --> https://bugs.freedesktop.org/attachment.cgi?id=139483&action=edit full dmesg The Radeon HD 3450 acceleration support does not work on my computer. uname -a: Linux mouse 4.17.0-041700rc4-generic #201805070430 SMP Mon May 7 04:31:46 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux In the dmesg I get: [ 4.007419] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD) [ 4.007433] radeon 0000:02:00.0: disabling GPU acceleration -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 106191] Failure to recognize DisplayPort signal
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=106191 Bug ID: 106191 Summary: Failure to recognize DisplayPort signal 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: francois.jacques(a)gmail.com Created attachment 139004 --> https://bugs.freedesktop.org/attachment.cgi?id=139004&action=edit callstack from DRM/radeon DRM/radeon fails with in drm_dp_link_rate_to_bw_code Driver fails to negotiate video resolution with DP-connected monitor, on any of 4 DP ports. Controller can drive monitor at 2048x1080 through HDMI adapter. Straight DP cable only works in console (low-res) Disconnecting power cable from monitor for 5 minutes trick doesn't help ;) Video controller: FirePro v8800 ChipID 0x6888 (see hardware.txt for details, 4 DPs) DP monitor: Dell U2717DA Workstation: HP xw8600 Kernel messages with backtrace: see var_log_messages_excerpt.txt Max res supported by monitor: 1440p (see Xorg.0.log) -- You are receiving this mail because: You are the assignee for the bug.

1 16

[Bug 105728] radeon_init takes longer than a few seconds
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=105728 Bug ID: 105728 Summary: radeon_init takes longer than a few seconds Product: DRI Version: DRI git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: pmenzel+bugs.freedesktop(a)molgen.mpg.de On a Asus F2A85-M PRO with an AMD A6-6400K APU with Radeon HD Graphics and Linux 4.14.13 `radeon_init`, according to `initcall_debug`, takes over two seconds to execute. Init functions should not take longer than a few milliseconds to load. ``` $ sudo dmesg | grep -i radeon [ 18.767379] calling radeon_init+0x0/0xab [radeon] @ 292 [ 18.767382] [drm] radeon kernel modesetting enabled. [ 18.809797] radeon 0000:00:01.0: VRAM: 768M 0x0000000000000000 - 0x000000002FFFFFFF (768M used) [ 18.809798] radeon 0000:00:01.0: GTT: 1024M 0x0000000030000000 - 0x000000006FFFFFFF [ 18.811498] [drm] radeon: 768M of VRAM memory ready [ 18.811499] [drm] radeon: 1024M of GTT memory ready. [ 18.812019] radeon 0000:00:01.0: firmware: direct-loading firmware radeon/ARUBA_pfp.bin [ 18.812512] radeon 0000:00:01.0: firmware: direct-loading firmware radeon/ARUBA_me.bin [ 18.812674] radeon 0000:00:01.0: firmware: direct-loading firmware radeon/ARUBA_rlc.bin [ 18.812813] [drm] radeon: dpm initialized [ 18.813730] radeon 0000:00:01.0: firmware: direct-loading firmware radeon/TAHITI_uvd.bin [ 18.814178] radeon 0000:00:01.0: firmware: direct-loading firmware radeon/TAHITI_vce.bin [ 18.867545] radeon 0000:00:01.0: WB enabled [ 18.867549] radeon 0000:00:01.0: fence driver on ring 0 use gpu addr 0x0000000030000c00 and cpu addr 0xffff8a5af9339c00 [ 18.867928] radeon 0000:00:01.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffab8a01435a18 [ 18.888018] radeon 0000:00:01.0: fence driver on ring 6 use gpu addr 0x0000000030000c18 and cpu addr 0xffff8a5af9339c18 [ 18.888021] radeon 0000:00:01.0: fence driver on ring 7 use gpu addr 0x0000000030000c1c and cpu addr 0xffff8a5af9339c1c [ 18.888022] radeon 0000:00:01.0: fence driver on ring 1 use gpu addr 0x0000000030000c04 and cpu addr 0xffff8a5af9339c04 [ 18.888024] radeon 0000:00:01.0: fence driver on ring 2 use gpu addr 0x0000000030000c08 and cpu addr 0xffff8a5af9339c08 [ 18.888025] radeon 0000:00:01.0: fence driver on ring 3 use gpu addr 0x0000000030000c0c and cpu addr 0xffff8a5af9339c0c [ 18.888026] radeon 0000:00:01.0: fence driver on ring 4 use gpu addr 0x0000000030000c10 and cpu addr 0xffff8a5af9339c10 [ 18.916268] radeon 0000:00:01.0: radeon: MSI limited to 32-bit [ 18.917088] radeon 0000:00:01.0: radeon: using MSI. [ 18.917113] [drm] radeon: irq initialized. [ 20.736792] [drm] Radeon Display Connectors [ 21.035055] fbcon: radeondrmfb (fb0) is primary device [ 21.152576] radeon 0000:00:01.0: fb0: radeondrmfb frame buffer device [ 21.172202] [drm] Initialized radeon 2.50.0 20080528 for 0000:00:01.0 on minor 0 [ 21.172314] initcall radeon_init+0x0/0xab [radeon] returned 0 after 2348527 usecs [ 126.973651] radeon_dp_aux_transfer_native: 74 callbacks suppressed ``` -- You are receiving this mail because: You are the assignee for the bug.

1 3

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel June 2018