dri-devel July 2017

dri-devel@lists.freedesktop.org

212 participants
1542 discussions

[Bug 41561] New: Hotplug detect does not work for HDMI monitor on Fusion E-350 board
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=41561 Summary: Hotplug detect does not work for HDMI monitor on Fusion E-350 board 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: simon.farnsworth(a)onelan.co.uk Using airlied-drm-fixes kernel as of commit 6777a4f6898a53974ef7fe7ce09ec41fae0f32db with Alex Deucher's patch "drm/radeon/kms: use hardcoded dig encoder to transmitter mapping for DCE4.1" on top, I'm not seeing uevents from the kernel when I plug and unplug a HDMI monitor. dmesg with drm.debug=0xf shows me the following when I connect a monitor: # dmesg -c [15202.939581] [drm:evergreen_irq_process], r600_irq_process start: rptr 5872, wptr 5888 [15202.939609] [drm:evergreen_irq_process], IH: HPD2 [15203.050597] [drm:radeon_atombios_connected_scratch_regs], DFP1 connected [15203.050605] [drm:output_poll_execute], [CONNECTOR:15:HDMI-A-1] status updated from 1 to 1 [15203.052661] [drm:output_poll_execute], [CONNECTOR:17:VGA-1] status updated from 2 to 2 radeonreg suggests that the HPD sense bit is correctly set # ./radeonreg regs all | grep 00006028 # DC_HPD2_INT_STATUS 00006028 ff0ff012 (-15732718) When I remove the monitor, I get the following from dmesg and radeonreg: # dmesg -c [15307.075271] [drm:evergreen_irq_process], r600_irq_process start: rptr 5888, wptr 5904 [15307.075300] [drm:evergreen_irq_process], IH: HPD2 [15307.131727] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 192 [15307.131733] Raw EDID: [15307.131738] 3f ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [15307.131742] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [15307.131745] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [15307.131749] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [15307.131752] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [15307.131756] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [15307.131759] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [15307.131763] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [15307.141965] [drm:radeon_dvi_detect] *ERROR* HDMI-A-1: probed a monitor but no|invalid EDID [15307.141975] [drm:radeon_atombios_connected_scratch_regs], DFP1 connected [15307.141981] [drm:output_poll_execute], [CONNECTOR:15:HDMI-A-1] status updated from 1 to 1 [15307.144028] [drm:output_poll_execute], [CONNECTOR:17:VGA-1] status updated from 2 to 2 # ./radeonreg regs all | grep 00006028 # DC_HPD2_INT_STATUS 00006028 ff0ff000 (-15732736) suggesting that HPD sense bits are being updated correctly by the hardware, but that this isn't resulting in uevents following through. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 13

[Bug 41418] New: [RV350] Screen corruption with certain resolutions on LVDS (scaled)
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=41418 Summary: [RV350] Screen corruption with certain resolutions on LVDS (scaled) 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: dev(a)karlchenofhell.org I'm getting a screen corruption with the resolutions 1400x1050 1440x900 on a RV350, using kernel-3.0.4, libdrm-2.4.26. A photograph of the corrupted screen under X is attached, though the corruption also appears using tests/modetest w/o X started. -------- # lspci -nns1:0.0 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc M10 NT [FireGL Mobility T2] [1002:4e54] (rev 80) -------- -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 8

[Bug 101988] blackscreen after modprobe amdgpu on R9M370X mac edition
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=101988 Bug ID: 101988 Summary: blackscreen after modprobe amdgpu on R9M370X mac edition Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: blocker Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: newincpp(a)gmail.com Created attachment 133154 --> https://bugs.freedesktop.org/attachment.cgi?id=133154&action=edit dmesg after `modprobe amdgpu` and getting blackscreen I don't know if this is specific to R9M370X - mac edition but I couldn't reproduce it on other AMD PC I have. This is fairly simple to reproduce, I just have to mount the amdgpu and I get a black screen on my main screen and my main screen only (my second screen is fine) I don't have this problem using radeon with the exact same kernel config. dmesg is saying everything is fine and X11 log is irrelevant because it happen _before_ startx. I am using Linux 4.12.4-gentoo. -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 38657] New: Redwood: power state #4 not used
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=38657 Summary: Redwood: power state #4 not used Product: DRI Version: unspecified Platform: All OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: mkgmafbt(a)gmail.com Created an attachment (id=48390) --> (https://bugs.freedesktop.org/attachment.cgi?id=48390) Part of dmesg with power states It's a Sapphire Radeon HD5670 512MB GDDR5. DRM reports 5 power states, but low profile won't use #4, wich is the 2D profile, nor does dynpm. All kernels with Evergreen pm support are affected by this (possible) bug, including 3.0-rc4. cat /sys/class/drm/card0/device/power_profile low cat /sys/kernel/debug/dri/0/radeon_pm_info default engine clock: 775000 kHz current engine clock: 399990 kHz default memory clock: 950000 kHz current memory clock: 950000 kHz voltage: 1100 mV PCIE lanes: 16 (should be 150/300 MHz 0.9V) lspci -nn | grep VGA 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Redwood [Radeon HD 5670] [1002:68d8] -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 4

[Bug 101976] glmark2 random blank or background only screen freeze over mesa3d 17.1 and 17.3 with radeon rx550 AMD POLARIS12
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=101976 Bug ID: 101976 Summary: glmark2 random blank or background only screen freeze over mesa3d 17.1 and 17.3 with radeon rx550 AMD POLARIS12 Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: pablodav(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 133139 --> https://bugs.freedesktop.org/attachment.cgi?id=133139&action=edit journal -ab log -- You are receiving this mail because: You are the assignee for the bug.

1 18

[Bug 41366] New: HDMI on a Fusion board only comes up when LVDS is already enabled
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=41366 Summary: HDMI on a Fusion board only comes up when LVDS is already enabled Product: DRI Version: XOrg CVS Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: simon.farnsworth(a)onelan.co.uk I'm running airlied's drm-fixes, git revision fdfc61594e6de21c23f955818ef78bcab9bafe40, and experiencing "interesting" times trying to get HDMI to work on a Fusion GPU (detected by X as [ 49.876] (--) RADEON(0): Chipset: "AMD Radeon HD 6310 Graphics" (ChipID = 0x9802)). If I run: xrandr --output HDMI-0 --off xrandr --output LVDS --auto xrandr --output HDMI-0 --mode 1920x1200 the HDMI monitor comes up at 1920x1200 If I run: xrandr --output HDMI-0 --off xrandr --output LVDS --off xrandr --output HDMI-0 --mode 1920x1200 the HDMI monitor immediately enters DPMS Off state, and stays there. I've confirmed with "grep . /sys/class/drm/card0-HDMI-A-1/*" that the kernel thinks the HDMI connector is switched on. The only difference I can see is that HDMI works when it gets CRTC 1, but not when it gets CRTC 0. I have captured logs from the kernel with drm.debug=0x6 during the runs, in case that explains what's going on; I will attach them to this bug. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 8

[Bug 41002] New: Switching doesn't work between plymouth and xorg.
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=41002 Summary: Switching doesn't work between plymouth and xorg. Product: DRI Version: XOrg CVS Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: fabian.deutsch(a)gmx.de When initiating a switch to the discrete card while plymouth is running, the switch doesn't happen completely in the small slot between the end of ply and Xorg's start. This happens with current Fedora 15 (all updates). Note: Maybe this is similar to bug #32970 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 2

[Bug 101946] Rebinding AMDGPU causes initialization errors [R9 290 / 4.10 kernel]
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=101946 Bug ID: 101946 Summary: Rebinding AMDGPU causes initialization errors [R9 290 / 4.10 kernel] Product: DRI Version: XOrg 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: beanow(a)oscp.info Created attachment 133068 --> https://bugs.freedesktop.org/attachment.cgi?id=133068&action=edit The script used to reproduce the error. As I attempted to hotplug my R9 290 for a VM gaming setup, I stumbled on this issue. The main kern.log error to come up is: > [ 160.013733] [drm:ci_dpm_enable [amdgpu]] *ERROR* ci_start_dpm failed > [ 160.014134] [drm:amdgpu_device_init [amdgpu]] *ERROR* hw_init of IP block <amdgpu_powerplay> failed -22 > [ 160.014531] amdgpu 0000:01:00.0: amdgpu_init failed For my setup I use a Kaby Lake iGPU running i915. With the R9 290 using vfio-pci / amdgpu. Ubuntu 17.04 (4.10.0-28-generic). Mesa 17.1.4 from the padoka stable PPA. I'm able to reproduce this as follows. 1. Boot with vfio-pci capturing the card and amdgpu blacklisted. Kernel flags: > intel_iommu=on iommu=pt vfio-pci.ids=1002:67b1,1002:aac8 2. Since I run Gnome3 on Ubuntu 17.04, this will bring me to a wayland greeter which uses my iGPU. Drop to a free TTY, without logging in. This prevents Xorg from responding to the AMD card becoming available. 3. Run the attached script "rebind-amd.sh" as root to bind back and forth between vfio-pci and amdgpu in an infinite loop. This will: A. modprobe both drivers to be sure they're loaded. B. Print information about the driver and card usage. C. Use the new_id > unbind > bind > remove_id sequence to switch drivers. What happens is: vfio-pci -> vfio-pci, Gives no problems, of course. vfio-pci -> amdgpu, This works and the amdgpu driver initializes the card. Attached monitor(s) start searching for signals. amdgpu -> vfio-pci, Since no Xorg is using the dGPU this works without problems. vfio-pci -> amdgpu, Fails to initialize dGPU with the kernel error above. I've attached the script, the output of the script and the full kern.log. -- You are receiving this mail because: You are the assignee for the bug.

1 33

[Bug 40935] New: radeon lockup on resume
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=40935 Summary: radeon lockup on resume Product: DRI Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: hramrach(a)gmail.com The card locked up after resume from suspend. The resume probably happened because suspend failed and the system did not shut down at all meaning the card was not reset to text mode. Initializing radeon from anything but text mode fails but normally does not lock up the card completely. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 10

[Bug 40216] New: X crashes when I open some specific pictures in Firefox. I can reproduce this at reliably.
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=40216 Summary: X crashes when I open some specific pictures in Firefox. I can reproduce this at reliably. Product: DRI Version: XOrg CVS Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: skoutstaal(a)xs4all.nl Created an attachment (id=50368) --> (https://bugs.freedesktop.org/attachment.cgi?id=50368) Xorg.0.log with crash. **Relavant lines in the log file; [146065.387] Backtrace: [146065.387] 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80eab8b] [146065.387] 1: /usr/bin/X (0x8048000+0x5fb38) [0x80a7b38] [146065.387] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xd1440c] [146065.387] 3: /usr/lib/xorg/modules/drivers/radeon_drv.so (0x746000+0xa29f1) [0x7e89f1] [146065.387] 4: /usr/lib/xorg/modules/libexa.so (0x15e000+0x8f4f) [0x166f4f] [146065.387] 5: /usr/bin/X (0x8048000+0xe2905) [0x812a905] [146065.387] 6: /usr/bin/X (0x8048000+0x24988) [0x806c988] [146065.387] 7: /usr/bin/X (0x8048000+0x28167) [0x8070167] [146065.387] 8: /usr/bin/X (0x8048000+0x1a81c) [0x806281c] [146065.387] 9: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xe7) [0x53ee37] [146065.388] 10: /usr/bin/X (0x8048000+0x1a411) [0x8062411] [146065.388] Bus error at address 0xb36d7008 [146065.388] Caught signal 7 (Bus error). Server aborting [146065.388] **My display adapter, according to lspci 01:00.0 VGA compatible controller: ATI Technologies Inc M64-S [Mobility Radeon X2300] **radeon-related dmesg messages # dmesg | grep -i radeon [ 15.353469] [drm] radeon defaulting to kernel modesetting. [ 15.353471] [drm] radeon kernel modesetting enabled. [ 15.353525] radeon 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 15.353531] radeon 0000:01:00.0: setting latency timer to 64 [ 15.354812] radeon 0000:01:00.0: VRAM: 128M 0x0000000000000000 - 0x0000000007FFFFFF (128M used) [ 15.354815] radeon 0000:01:00.0: GTT: 512M 0x0000000008000000 - 0x0000000027FFFFFF [ 15.354868] radeon 0000:01:00.0: irq 46 for MSI/MSI-X [ 15.354873] radeon 0000:01:00.0: radeon: using MSI. [ 15.354895] [drm] radeon: irq initialized. [ 15.359633] [drm] radeon: 128M of VRAM memory ready [ 15.359635] [drm] radeon: 512M of GTT memory ready. [ 15.361088] [drm] radeon: 1 quad pipes, 1 z pipes initialized. [ 15.362373] radeon 0000:01:00.0: WB enabled [ 15.409831] [drm] radeon: ring at 0x0000000008001000 [ 15.410001] [drm] radeon: ib pool ready. [ 15.414531] [drm] Radeon Display Connectors [ 15.541601] [drm] radeon: power management initialized [ 15.775058] fbcon: radeondrmfb (fb0) is primary device [ 15.775648] fb0: radeondrmfb frame buffer device [ 15.775656] [drm] Initialized radeon 2.8.0 20080528 for 0000:01:00.0 on minor 0 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- 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 July 2017