dri-devel July 2017

dri-devel@lists.freedesktop.org

212 participants
1542 discussions

[Bug 95574] amdgpu_init fails on xen boot
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=95574 Bug ID: 95574 Summary: amdgpu_init fails on xen boot Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: bpaterni(a)gmail.com Created attachment 124011 --> https://bugs.freedesktop.org/attachment.cgi?id=124011&action=edit xen boot with amdgpu module enabled Hi, I'm trying to boot into a linux dom0 via xen, but when the amdgpu kernel module is loaded, the system hangs, and the graphics card's fan spins up to max speed! To get a better idea of what was happening prior to the hang, I connected to the machine via serial port and captured the attached boot messages which include a kernel backtrace towards the bottom. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 95073] Radeon R8 M365DX not working
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=95073 Bug ID: 95073 Summary: Radeon R8 M365DX not working Product: DRI Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: tomas.wilhelmsson(a)gmail.com Created attachment 123160 --> https://bugs.freedesktop.org/attachment.cgi?id=123160&action=edit dmesg Dual gpu system, AMD A10 8700p with R6 gpu and Radeon R8 M365DX Linux mrsun-E15 4.5.2-1-ARCH #1 SMP PREEMPT Thu Apr 21 18:21:27 CEST 2016 x86_64 GNU/Linux -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 94679] DAL DCE 10 missing CEA interlaced modes
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=94679 Bug ID: 94679 Summary: DAL DCE 10 missing CEA interlaced modes Product: DRI Version: DRI git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: adf.lists(a)gmail.com I don't know if this is a bug or a feature request :-) Testing R9285 Tonga + various agd5f DAL kernels I notice that the CEA interlaced modes of my HDMI connected TV are missing. With "normal" kernels they are listed and though not perfect (or not working at all in the double clocked cases) I did use one of them sometimes as it let me use my TVs de-interlacer. fglrx has all interlaced modes working for my TV, so I was hopeful that DAL would have also had them. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 94530] AMD R9 Nano reset problem
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=94530 Bug ID: 94530 Summary: AMD R9 Nano reset problem Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: creakbeat(a)gmail.com I am trying to passthrough R9 Nano to a VM, and facing some problems. After Windows 7 has been installed, the latest AMD Crimson edition driver is installed. At first time, the driver works properly. There appears to have the problem when I power off the vm and restart it. The driver was not working until I reboot the host. Here is my system. Manufacturer: Supermicro Product Name: X10DAi CPU: Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz memory: 8GB linux kernel: 3.19.0 $ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-3.19.0 root=UUID=fc28306a-e168-406a-805d-cadf70de53ec ro quiet splash intel-iommu=on vfio_iommu_type1.allow_unsafe_interrupts=1 vt.handoff=7 I tried to use qemu version 2.3.1, 2.4.1, and 2.5.1. I also added the device id number into the function vfio_setup_resetfn(), but the problem remains. I start my virtual machine with the following code. qemu-system-x86_64 -enable-kvm \ -M pc -m 4096 -cpu host \ -smp 4,sockets=1,cores=4,threads=1 \ -rtc base=localtime \ -vnc :0 \ -vga none \ -device lsi,id=scsi0,bus=pci.0 \ -device vfio-pci,host=03:00.0,x-vga=on \ -device vfio-pci,host=03:00.1 \ -hda $1 \ -monitor stdio -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 94207] [amdgpu][tonga]kernel BUG during X startup in amdgpu_cgs_get_active_displays_info
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=94207 Bug ID: 94207 Summary: [amdgpu][tonga]kernel BUG during X startup in amdgpu_cgs_get_active_displays_info 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: csaba.halasz(a)gmail.com Created attachment 121836 --> https://bugs.freedesktop.org/attachment.cgi?id=121836&action=edit syslog Sometimes during X startup amdgpu crashes. So far I have only observed this when I restart X after it has been running already, never at boot. System: r9 380, amdgpu git agd5f/drm-fixes-4.5 cc1de6e8 merged with agd5f/drm-next-4.6-wip fa9e6991, llvm git ae316aa0, mesa git fe14110f, Xorg 1.18 -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 94158] [amdgpu][tonga] GPU randomly gets stuck at 100% load and high clocks
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=94158 Bug ID: 94158 Summary: [amdgpu][tonga] GPU randomly gets stuck at 100% load and high clocks 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: csaba.halasz(a)gmail.com I have noticed that my GPU fans start running at high speed after some time. Investigating, I see: # cat /sys/kernel/debug/dri/0/amdgpu_pm_info [ mclk ]: 1425 MHz [ sclk ]: 990 MHz [GPU load]: 100% Of course I am not running any graphics intensive programs and radeontop confirms <1% load. Even shutting down Xorg altogether doesn't help. It may be related to dpms going to "off" state, the last time it happened while the monitors were off, or possibly just as they were switching off. I will try to collect additional data points. Nothing suspicious shows in logs. Powerplay seems to work fine until the issue occurs. Afterwards, I can manually lower clocks, but load stays 100%. Side note: dpms transitions seem to reset the manual power_dpm_force_performance_level back to auto and hence high clock. System: r9 380, amdgpu git agd5f/drm-fixes-4.5 cc1de6e8 merged with agd5f/drm-next-4.6-wip fa9e6991, llvm git ae316aa0, mesa git fe14110f, Xorg 1.18 -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 93893] R9 390 Hawaii fails resuming from hibernation on amdgpu (linux-4.5.0-rc1)
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=93893 Bug ID: 93893 Summary: R9 390 Hawaii fails resuming from hibernation on amdgpu (linux-4.5.0-rc1) Product: DRI Version: XOrg git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: h.judt(a)gmx.at Created attachment 121330 --> https://bugs.freedesktop.org/attachment.cgi?id=121330&action=edit dmesg I've hoped it would work better than with radeon, but unfortunately it is even worse and will not even perform a single cycle. All ring tests fail with CAFEDEAD. Dmesg attached. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 92993] Powerplay: Thermal controller fails to start on R9 Nano (Fiji)
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=92993 Bug ID: 92993 Summary: Powerplay: Thermal controller fails to start on R9 Nano (Fiji) Product: DRI Version: DRI git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: master.homer(a)gmail.com Just got a Sapphire R9 Nano and noticed some problems while running with the latest powerplay kernel from agd5f (commit 256ca780500bc445752763f32b246dc9ee396b62). I don't know how well implemented this is just yet, but it seems like the thermal controller fails to start on my card due to hwmgr->start_thermal_controller->function_list being NULL: [ 2.057417] powerplay: phm_start_thermal_controller [ 2.057419] [ powerplay ] phm_dispatch_table Invalid Parameter! ffff880425cd2000 ffff880425cd2230 (null) The first address refers to hwmgr, the second to rt_table and the last to rt_table->function_list. This, in turn, causes the hwmon interface to not work, and sensors gives me a 0.0 temperature. I'm unsure if this causes the fan to not speed up, but I haven't noticed any sound difference when running valley for example. I've noticed another (possibly unrelated) thing too, checking amdgpu_pm_info I can see that the mclk never changes, just the sclk. I did notice that it fails to find the virtual voltage 65281 in the vdd list, but of course I'm not sure this is related: [ 2.006036] powerplay: us_vdd 900 vs virtual_voltage_id 65281 [ 2.006037] powerplay: us_vdd 65282 vs virtual_voltage_id 65281 [ 2.006038] powerplay: us_vdd 65283 vs virtual_voltage_id 65281 [ 2.006038] powerplay: us_vdd 65284 vs virtual_voltage_id 65281 [ 2.006039] powerplay: us_vdd 65285 vs virtual_voltage_id 65281 [ 2.006040] powerplay: us_vdd 65286 vs virtual_voltage_id 65281 [ 2.006040] powerplay: us_vdd 65287 vs virtual_voltage_id 65281 [ 2.006041] powerplay: us_vdd 65288 vs virtual_voltage_id 65281 [ 2.006042] Can't find requested voltage id in vdd_dep_on_sclk table! -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 92974] Fiji Nano long boot up and long X startup with amdgpu-powerplay enabled
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=92974 Bug ID: 92974 Summary: Fiji Nano long boot up and long X startup with amdgpu-powerplay enabled Product: DRI Version: DRI git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: bug0xa3d2(a)hushmail.com Created attachment 119727 --> https://bugs.freedesktop.org/attachment.cgi?id=119727&action=edit Output of dmesg after startup. With AMD Powerplay enabled in the kernel (cloned from http://cgit.freedesktop.org/~agd5f/linux/?h=amdgpu-powerplay)--when the computer boots there is text, as usual, before modesetting tries to switch to the native resolution of the monitor. At this point, the monitor backlight turns off for about 5 seconds and then stays on for approximately 2 minutes displaying nothing as if the computer locked up with no other boot activity occuring. The Alt+PrintScreen+E/I/U/R button combo still works at this time. If left alone the system finishes booting normally after about 2 minutes. dmesg gives these new error/messages: "Failed to send Previous Message." and ..."[drm] ib test on ring 12 succeeded" that I have not noticed when AMD Powerplay is disabled. Trying to run, "startx" at the console also simulates a system freeze for about 2 minutes or so then X starts normally. To work around the long boot and long X startup bug the kernel option, "Device Drivers/Graphics support/Direct Rendering Manager/Enable legacy fbdev support for your modesetting driver" must be set with, "n". This gives a black screen or no console after the machine boots to log in blind with. X can also be started blind and displayed normally with no startup delay. Another option is to autologin with KDM or such like to boot directly into X after legacy fbdev has been disabled in the kernel options. With AMD Powerplay disabled in the kernel there are no startup issues. Toggling or including/excluding these kernel boot, "lilo.conf" options have no effect on the bug: "amdgpu.enable_scheduler=0 ; radeon.modeset=1 ; radeon.hw_i2c=1 ; radeon.disp_priority=2 ; radeon.fastfb=1 ; radeon.backlight=1 ; radeon.pcie_gen2=-1 ; radeon.hard_reset=0" These patches (applied and not applied) have no effect on the bug: http://people.freedesktop.org/~agd5f/0001-radeonsi-fix-fiji-raster-config.p… http://people.freedesktop.org/~agd5f/0001-drm-amdgpu-update-Fiji-s-tiling-m… Hardware: Fury Nano git: http://cgit.freedesktop.org/~agd5f/linux/commit/?h=amdgpu-powerplay&id=256c… Sidenote: hang check timer is disabled in the kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 18

[Bug 92827] Tonga: No Sound over HDMI with connected AV receiver
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=92827 Bug ID: 92827 Summary: Tonga: No Sound over HDMI with connected AV receiver 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: winlux(a)gmail.com Created attachment 119417 --> https://bugs.freedesktop.org/attachment.cgi?id=119417&action=edit cat /proc/asound/card1/eld#0.0 I'm using the new amdgpu driver on Linux 4.2 and 4.3 RC7 with my new Radeon R9 380. I want to use my 5.1 receiver to get audio over HDMI, it works just fine under Windows 8.1. Under Manjaro Linux, I have configured a standard FullHD output on HDMI with 60 Hz – with my former Radeon HD 7770 using radeonsi this was the rule to get audio (don't get me started on broken HDMI audio on radeonsi. With Linux 4.0+ until now, I needed to use the 3.18 kernel to *not* see only "unplugged" outputs in PulseAudio. See bug 90777.). In fortunate distinction to radeonsi on Linux 4.0+, PulseAudio shows 2.0, 5.1 and 7.1 output over HDMI as plugged in and available. But I don't get any output. No HDMI audio output on Tonga using amdgpu on Linux 4.2 and 4.3 RC7. -- You are receiving this mail because: You are the assignee for the bug.

1 13

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel July 2017