dri-devel June 2021

dri-devel@lists.freedesktop.org

341 participants
878 discussions

[Bug 213561] New: [bisected] AMD GPU can no longer idle state after commit 1c0b0efd148d5b24c4932ddb3fa03c8edd6097b3
by bugzilla-daemon＠bugzilla.kernel.org 20 Jan '22

20 Jan '22

https://bugzilla.kernel.org/show_bug.cgi?id=213561 Bug ID: 213561 Summary: [bisected] AMD GPU can no longer idle state after commit 1c0b0efd148d5b24c4932ddb3fa03c8edd6097b3 Product: Drivers Version: 2.5 Kernel Version: 5.13rc7 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: untaintableangel(a)hotmail.co.uk Regression: No Nature of the problem: RX 5700 is unable to enter low power state at idle (see below for usual behaviour) Sensors at idle prior to the commit: amdgpu-pci-0f00 Adapter: PCI adapter vddgfx: 775.00 mV fan1: 0 RPM (min = 0 RPM, max = 3200 RPM) edge: +48.0°C (crit = +100.0°C, hyst = -273.1°C) (emerg = +105.0°C) junction: +48.0°C (crit = +110.0°C, hyst = -273.1°C) (emerg = +115.0°C) mem: +52.0°C (crit = +105.0°C, hyst = -273.1°C) (emerg = +110.0°C) power1: 8.00 W (cap = 165.00 W) After the commit, the lowest is: amdgpu-pci-0f00 Adapter: PCI adapter vddgfx: 1.03 V fan1: 0 RPM (min = 0 RPM, max = 3200 RPM) edge: +54.0°C (crit = +100.0°C, hyst = -273.1°C) (emerg = +105.0°C) junction: +56.0°C (crit = +110.0°C, hyst = -273.1°C) (emerg = +115.0°C) mem: +52.0°C (crit = +105.0°C, hyst = -273.1°C) (emerg = +110.0°C) power1: 31.00 W (cap = 165.00 W) This problem wasn't present in rc6 but is present in 5.13rc7 and bisects to: 1c0b0efd148d5b24c4932ddb3fa03c8edd6097b3 is the first bad commit commit 1c0b0efd148d5b24c4932ddb3fa03c8edd6097b3 Author: Yifan Zhang <yifan1.zhang(a)amd.com> Date: Thu Jun 10 10:10:07 2021 +0800 drm/amdgpu/gfx10: enlarge CP_MEC_DOORBELL_RANGE_UPPER to cover full doorbell. If GC has entered CGPG, ringing doorbell > first page doesn't wakeup GC. Enlarge CP_MEC_DOORBELL_RANGE_UPPER to workaround this issue. Signed-off-by: Yifan Zhang <yifan1.zhang(a)amd.com> Reviewed-by: Felix Kuehling <Felix.Kuehling(a)amd.com> Reviewed-by: Alex Deucher <alexander.deucher(a)amd.com> Signed-off-by: Alex Deucher <alexander.deucher(a)amd.com> Cc: stable(a)vger.kernel.org The device is a Sapphire Pulse RX5700 and this problem is seen even with one monitor set at 60Hz. GPU: 0f:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c4) -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.

1 20

[Bug 204559] New: amdgpu: kernel oops with constant gpu resets while using mpv
by bugzilla-daemon＠bugzilla.kernel.org 17 Jan '22

17 Jan '22

https://bugzilla.kernel.org/show_bug.cgi?id=204559 Bug ID: 204559 Summary: amdgpu: kernel oops with constant gpu resets while using mpv Product: Drivers Version: 2.5 Kernel Version: 5.2.7 Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: shoegaze(a)tutanota.com Regression: No Created attachment 284335 --> https://bugzilla.kernel.org/attachment.cgi?id=284335&action=edit oops.txt While watching a video using mpv (default config) the system will hang eventually - this is actually a kernel oops that happens after lots of GPU resets every second or so (in the span of ~5 minutes; it seems to be alright in the beginning): > Aug 12 00:46:49 mashedpotato kernel: [drm] UVD and UVD ENC initialized > successfully. > Aug 12 00:46:49 mashedpotato kernel: [drm] VCE initialized successfully. > Aug 12 00:46:56 mashedpotato kernel: amdgpu 0000:01:00.0: GPU pci config > reset > Aug 12 00:46:59 mashedpotato kernel: [drm] PCIE GART of 256M enabled (table > at 0x000000F400000000). This block of warnings repeats itself many times and then it is this error: > Aug 12 00:52:20 mashedpotato kernel: amdgpu 0000:01:00.0: > [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring sdma0 test failed (-110) > Aug 12 00:52:20 mashedpotato kernel: [drm:amdgpu_device_resume [amdgpu]] > *ERROR* resume of IP block <sdma_v3_0> failed -110 > Aug 12 00:52:20 mashedpotato kernel: [drm:amdgpu_device_resume [amdgpu]] > *ERROR* amdgpu_device_ip_resume failed (-110). > Aug 12 00:52:25 mashedpotato kernel: BUG: kernel NULL pointer dereference, > address: 0000000000000000 > Aug 12 00:52:25 mashedpotato kernel: #PF: supervisor instruction fetch in > kernel mode > Aug 12 00:52:25 mashedpotato kernel: #PF: error_code(0x0010) - not-present > page In the end it is a kernel oops, log is in the attachment. The system is only recoverable via a hard reset afterwards, though the sound from a video keeps playing just fine. My system is a ASUS laptop, TUF FX505-DY with the latest BIOS. lspci: > 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root > Complex > 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU > 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models > 00h-1fh) PCIe Dummy Host Bridge > 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP > Bridge [6:0] > 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP > Bridge [6:0] > 00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP > Bridge [6:0] > 00:01.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP > Bridge [6:0] > 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models > 00h-1fh) PCIe Dummy Host Bridge > 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal > PCIe GPP Bridge 0 to Bus A > 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev > 61) > 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev > 51) > 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device > 24: Function 0 > 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device > 24: Function 1 > 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device > 24: Function 2 > 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device > 24: Function 3 > 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device > 24: Function 4 > 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device > 24: Function 5 > 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device > 24: Function 6 > 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device > 24: Function 7 > 01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Baffin > [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] (rev e5) > 02:00.0 Non-Volatile memory controller: Kingston Technology Company, Inc. > Device 5008 (rev 01) > 03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE > 802.11ac PCIe Wireless Network Adapter > 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. > RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) > 05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] > Picasso (rev c2) > 05:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] > Raven/Raven2/Fenghuang HDMI/DP Audio Controller > 05:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h > (Models 10h-1fh) Platform Security Processor > 05:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1 > 05:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1 > 05:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models > 10h-1fh) HD Audio Controller I have amdgpu.gpu_reset=1 in my kernel commandline as I want to figure out another issue - sometimes the system hangs after locking and disabling screen, and I guess it is GPU reset-related. -- You are receiving this mail because: You are watching the assignee of the bug.

1 15

[Bug 210263] New: brightness device returns ENXIO (?) on brightness restore at boot, with bootoption "quiet"
by bugzilla-daemon＠bugzilla.kernel.org 12 Jan '22

12 Jan '22

https://bugzilla.kernel.org/show_bug.cgi?id=210263 Bug ID: 210263 Summary: brightness device returns ENXIO (?) on brightness restore at boot, with bootoption "quiet" Product: Drivers Version: 2.5 Kernel Version: 5.9.8 Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: plusfabi(a)gmail.com Regression: No Created attachment 293729 --> https://bugzilla.kernel.org/attachment.cgi?id=293729&action=edit dmesg Following: https://github.com/systemd/systemd/issues/17645 If I set kernel boot option "quiet", systemd fails to restore brightness level with error Failed to start Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0. At boot. full journal output is: journalctl -b -1 -u systemd-backlight@backlight:amdgpu_bl0.service -- Logs begin at Thu 2020-09-17 08:15:00 CEST, end at Tue 2020-11-17 14:19:18 CET. -- Nov 17 14:15:15 frigg systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0... Nov 17 14:15:15 frigg systemd-backlight[325]: amdgpu_bl0: Failed to write system 'brightness' attribute: No such device or address Nov 17 14:15:15 frigg systemd[1]: systemd-backlight@backlight:amdgpu_bl0.service: Main process exited, code=exited, status=1/FAILURE Nov 17 14:15:15 frigg systemd[1]: systemd-backlight@backlight:amdgpu_bl0.service: Failed with result 'exit-code'. Nov 17 14:15:15 frigg systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0. This is an AMD Renoir system, with AMD Ryzen 5 4500U APU, This happens only, if I set 'quiet' as boot option. If I remove it, brightness restore works fine. If I boot with quiet set, after login I can do systemctl start systemd-backlight@backlight:amdgpu_bl0.service And it will successfully restore my brightness level. -- You are receiving this mail because: You are watching the assignee of the bug.

1 8

[PATCH 1/3] drm/dp/mst: Handle errors from drm_atomic_get_private_obj_state() correctly
by ville.syrjala＠linux.intel.com 12 Jan '22

12 Jan '22

From: Ville Syrjälä <ville.syrjala(a)linux.intel.com> On failure drm_atomic_get_private_obj_state() returns and error pointer instead of NULL. Adjust the checks in the callers to match. Cc: stable(a)vger.kernel.org Cc: Dhinakaran Pandiyan <dhinakaran.pandiyan(a)intel.com> Cc: Harry Wentland <harry.wentland(a)amd.com> Cc: Maarten Lankhorst <maarten.lankhorst(a)linux.intel.com> Fixes: edb1ed1ab7d3 ("drm/dp: Add DP MST helpers to atomically find and release vcpi slots") Signed-off-by: Ville Syrjälä <ville.syrjala(a)linux.intel.com> --- drivers/gpu/drm/drm_dp_mst_topology.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/gpu/drm/drm_dp_mst_topology.c b/drivers/gpu/drm/drm_dp_mst_topology.c index bfd237c15e76..18cecd94acb6 100644 --- a/drivers/gpu/drm/drm_dp_mst_topology.c +++ b/drivers/gpu/drm/drm_dp_mst_topology.c @@ -2515,8 +2515,8 @@ int drm_dp_atomic_find_vcpi_slots(struct drm_atomic_state *state, int req_slots; topology_state = drm_atomic_get_mst_topology_state(state, mgr); - if (topology_state == NULL) - return -ENOMEM; + if (IS_ERR(topology_state)) + return PTR_ERR(topology_state); port = drm_dp_get_validated_port_ref(mgr, port); if (port == NULL) @@ -2555,8 +2555,8 @@ int drm_dp_atomic_release_vcpi_slots(struct drm_atomic_state *state, struct drm_dp_mst_topology_state *topology_state; topology_state = drm_atomic_get_mst_topology_state(state, mgr); - if (topology_state == NULL) - return -ENOMEM; + if (IS_ERR(topology_state)) + return PTR_ERR(topology_state); /* We cannot rely on port->vcpi.num_slots to update * topology_state->avail_slots as the port may not exist if the parent -- 2.13.0

4 7

[Bug 206475] New: amdgpu under load drop signal to monitor until hard reset
by bugzilla-daemon＠bugzilla.kernel.org 06 Jan '22

06 Jan '22

https://bugzilla.kernel.org/show_bug.cgi?id=206475 Bug ID: 206475 Summary: amdgpu under load drop signal to monitor until hard reset Product: Drivers Version: 2.5 Kernel Version: 5.5.2 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: rodomar705(a)protonmail.com Regression: No Created attachment 287265 --> https://bugzilla.kernel.org/attachment.cgi?id=287265&action=edit dmesg for the amdgpu hardware freeze While gaming the monitor goes blank randomly, only with this error in the logs of the system kernel: amdgpu: [powerplay] last message was failed ret is 65535 kernel: amdgpu: [powerplay] failed to send message 200 ret is 65535 kernel: amdgpu: [powerplay] last message was failed ret is 65535 kernel: amdgpu: [powerplay] failed to send message 282 ret is 65535 kernel: amdgpu: [powerplay] last message was failed ret is 65535 kernel: amdgpu: [powerplay] failed to send message 201 ret is 65535 with the occasional kernel: [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:47:crtc-0] flip_done timed out kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=5275264, emitted seq=5275266 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Hand of Fate 2. pid 682062 thread Hand of Fa:cs0 pid 682064 kernel: amdgpu 0000:06:00.0: GPU reset begin! over and over again. If I reset the system no video output is seen until the system is fully shut off. B450 chipset + Ryzen 5 2600 + Radeon RX580 GPU Full log is attached to this post. Can anyone at AMD give me some pointers to what the problem is? Thanks, Marco. -- You are receiving this mail because: You are watching the assignee of the bug.

1 22

[Bug 212019] New: [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:67:crtc-0] flip_done timed out
by bugzilla-daemon＠bugzilla.kernel.org 28 Dec '21

28 Dec '21

https://bugzilla.kernel.org/show_bug.cgi?id=212019 Bug ID: 212019 Summary: [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:67:crtc-0] flip_done timed out Product: Drivers Version: 2.5 Kernel Version: 5.11.0 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: clemens(a)endorphin.org Regression: No Created attachment 295569 --> https://bugzilla.kernel.org/attachment.cgi?id=295569&action=edit Hardware I get the following display freeze on my T495 AMD Thinkpad: Mar 02 09:24:50 duncan kernel: [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:67:crtc-0] flip_done timed out Mar 02 09:25:02 duncan kernel: [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:67:crtc-0] flip_done timed out Mar 02 09:36:25 duncan kernel: [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:55:plane-3] flip_done timed out followed by this stack trace: Mar 02 09:36:25 duncan kernel: WARNING: CPU: 7 PID: 1636 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:7754 amdgpu_dm_atomic_commit_tail+0x238b/0x2420 [amdgpu] Mar 02 09:36:25 duncan kernel: Modules linked in: fuse ctr ccm wireguard curve25519_x86_64 libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libblake2s blake2s_x86_64 ip6_udp_tunnel udp_tunnel libcurve25519_generic libchacha libblake2s_generic af_packet msr ip6table_nat iptable_nat nf_nat joydev mousedev xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip6t_rpfilter ipt_rpfilter amdgpu ip6table_raw iptable_raw xt_pkttype intel_rapl_msr nf_log_ipv6 nf_log_ipv4 nf_log_common xt_LOG xt_tcpudp wmi_bmof iwlmvm snd_hda_codec_realtek iommu_v2 mac80211 snd_hda_codec_generic gpu_sched drm_ttm_helper snd_hda_codec_hdmi ttm btusb snd_hda_intel edac_mce_amd uvcvideo btrtl btbcm libarc4 btintel edac_core videobuf2_vmalloc drm_kms_helper nls_iso8859_1 intel_rapl_common deflate videobuf2_memops evdev crc32_pclmul nls_cp437 snd_intel_dspcfg mac_hid videobuf2_v4l2 iwlwifi bluetooth ip6table_filter vfat videobuf2_common snd_hda_codec ghash_clmulni_intel fat snd_hda_core ip6_tables thinkpad_acpi videodev Mar 02 09:36:25 duncan kernel: r8169 drm snd_hwdep efi_pstore nvram rapl psmouse realtek mdio_devres ledtrig_audio mc serio_raw snd_pcm pstore cfg80211 agpgart i2c_algo_bit fb_sys_fops ecdh_generic syscopyarea snd_timer sysfillrect ecc sch_fq_codel iptable_filter sysimgblt ipmi_devintf k10temp sp5100_tco watchdog snd_rn_pci_acp3x i2c_piix4 ucsi_acpi snd_pci_acp3x libphy ipmi_msghandler rfkill snd 8250_pci typec_ucsi soundcore ac typec battery wmi video i2c_scmi backlight i2c_core pinctrl_amd tiny_power_button acpi_cpufreq button loop tun tap macvlan bridge stp llc kvm_amd kvm irqbypass efivarfs ip_tables x_tables autofs4 ext4 crc32c_generic crc16 mbcache jbd2 dm_crypt cbc sha256_ssse3 sha256_generic encrypted_keys trusted tpm rng_core rtsx_pci_sdmmc input_leds led_class mmc_core atkbd libps2 xhci_pci xhci_pci_renesas xhci_hcd crc32c_intel ehci_pci aesni_intel ehci_hcd libaes crypto_simd cryptd usbcore glue_helper nvme nvme_core rtsx_pci t10_pi usb_common crc_t10dif crct10dif_generic crct10dif_pclmul Mar 02 09:36:25 duncan kernel: crct10dif_common i8042 rtc_cmos serio dm_mod Mar 02 09:36:25 duncan kernel: CPU: 7 PID: 1636 Comm: X Not tainted 5.11.0 #1-NixOS Mar 02 09:36:25 duncan kernel: Hardware name: LENOVO 20NJCTO1WW/20NJCTO1WW, BIOS R12ET55W(1.25 ) 07/06/2020 Mar 02 09:36:25 duncan kernel: RIP: 0010:amdgpu_dm_atomic_commit_tail+0x238b/0x2420 [amdgpu] Mar 02 09:36:25 duncan kernel: Code: a8 fd ff ff 01 c7 85 a4 fd ff ff 37 00 00 00 c7 85 ac fd ff ff 20 00 00 00 e8 61 83 12 00 e9 e0 fa ff ff 0f 0b e9 30 f9 ff ff <0f> 0b e9 7f f9 ff ff 0f 0b 0f 0b e9 95 f9 ff ff 49 8b 06 41 0f b6 Mar 02 09:36:25 duncan kernel: RSP: 0018:ffffbd1043ae3928 EFLAGS: 00010002 Mar 02 09:36:25 duncan kernel: RAX: 0000000000000002 RBX: 000000000004bffc RCX: ffff976a603c9118 Mar 02 09:36:25 duncan kernel: RDX: 0000000000000001 RSI: 0000000000000297 RDI: ffff976a62660188 Mar 02 09:36:25 duncan kernel: RBP: ffffbd1043ae3c20 R08: 0000000000000005 R09: 0000000000000000 Mar 02 09:36:25 duncan kernel: R10: ffffbd1043ae3888 R11: ffffbd1043ae388c R12: 0000000000000297 Mar 02 09:36:25 duncan kernel: R13: ffff976e3132aa00 R14: ffff976a5dee9780 R15: ffff976a603c9000 Mar 02 09:36:25 duncan kernel: FS: 00007f993d92c980(0000) GS:ffff9772d8bc0000(0000) knlGS:0000000000000000 Mar 02 09:36:25 duncan kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 02 09:36:25 duncan kernel: CR2: 00007f30c85b5ff8 CR3: 000000013e056000 CR4: 00000000003506e0 Mar 02 09:36:25 duncan kernel: Call Trace: Mar 02 09:36:25 duncan kernel: commit_tail+0x94/0x130 [drm_kms_helper] Mar 02 09:36:25 duncan kernel: drm_atomic_helper_commit+0x113/0x140 [drm_kms_helper] Mar 02 09:36:25 duncan kernel: drm_atomic_helper_set_config+0x70/0xb0 [drm_kms_helper] Mar 02 09:36:25 duncan kernel: drm_mode_setcrtc+0x1d3/0x6f0 [drm] Mar 02 09:36:25 duncan kernel: ? amdgpu_cs_wait_ioctl+0xd2/0x160 [amdgpu] Mar 02 09:36:25 duncan kernel: ? drm_mode_getcrtc+0x180/0x180 [drm] Mar 02 09:36:25 duncan kernel: drm_ioctl_kernel+0xaa/0xf0 [drm] Mar 02 09:36:25 duncan kernel: drm_ioctl+0x1ec/0x390 [drm] Mar 02 09:36:25 duncan kernel: ? drm_mode_getcrtc+0x180/0x180 [drm] Mar 02 09:36:25 duncan kernel: amdgpu_drm_ioctl+0x49/0x80 [amdgpu] Mar 02 09:36:25 duncan kernel: __x64_sys_ioctl+0x83/0xb0 Mar 02 09:36:25 duncan kernel: do_syscall_64+0x33/0x40 Mar 02 09:36:25 duncan kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Mar 02 09:36:25 duncan kernel: RIP: 0033:0x7f993dd37b07 Mar 02 09:36:25 duncan kernel: Code: c0 75 b5 48 8d 3c 2b e8 17 ff ff ff 85 c0 78 b6 48 89 d8 5b 5d 41 5c c3 66 2e 0f 1f 84 00 00 00 00 00 90 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 39 73 0c 00 f7 d8 64 89 01 48 Mar 02 09:36:25 duncan kernel: RSP: 002b:00007ffdd63e1ed8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 Mar 02 09:36:25 duncan kernel: RAX: ffffffffffffffda RBX: 00007ffdd63e1f10 RCX: 00007f993dd37b07 Mar 02 09:36:25 duncan kernel: RDX: 00007ffdd63e1f10 RSI: 00000000c06864a2 RDI: 000000000000000f Mar 02 09:36:25 duncan kernel: RBP: 00000000c06864a2 R08: 0000000000000000 R09: 0000000002fad090 Mar 02 09:36:25 duncan kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 Mar 02 09:36:25 duncan kernel: R13: 000000000000000f R14: 00000000021b4290 R15: 0000000000000000 Mar 02 09:36:25 duncan kernel: ---[ end trace 3bd64ee8f9aa76ff ]--- lshw and full kernel log attached. The first kernel that I saw this problem with was the 5.9. series. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.

1 3

[PATCH] drm/ast: Support 1600x900 with 108MHz PCLK
by KuoHsiang Chou 23 Dec '21

23 Dec '21

[New] Create the setting for 1600x900 @60Hz refresh rate by 108MHz pixel-clock. Signed-off-by: KuoHsiang Chou <kuohsiang_chou(a)aspeedtech.com> --- drivers/gpu/drm/ast/ast_tables.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/gpu/drm/ast/ast_tables.h b/drivers/gpu/drm/ast/ast_tables.h index d665dd5af5dd..8414e543f260 100644 --- a/drivers/gpu/drm/ast/ast_tables.h +++ b/drivers/gpu/drm/ast/ast_tables.h @@ -282,6 +282,8 @@ static const struct ast_vbios_enhtable res_1360x768[] = { }; static const struct ast_vbios_enhtable res_1600x900[] = { + {1800, 1600, 24, 80,1000, 900, 1, 3, VCLK108, /* 60Hz */ + (SyncPP | Charx8Dot | LineCompareOff | WideScreenMode | NewModeInfo), 60, 3, 0x3A }, {1760, 1600, 48, 32, 926, 900, 3, 5, VCLK97_75, /* 60Hz CVT RB */ (SyncNP | Charx8Dot | LineCompareOff | WideScreenMode | NewModeInfo | AST2500PreCatchCRT), 60, 1, 0x3A }, -- 2.18.4

5 6

[Bug 207763] New: Noisy Screen in Linux with kernel 5
by bugzilla-daemon＠bugzilla.kernel.org 12 Dec '21

12 Dec '21

https://bugzilla.kernel.org/show_bug.cgi?id=207763 Bug ID: 207763 Summary: Noisy Screen in Linux with kernel 5 Product: Drivers Version: 2.5 Kernel Version: 5.0.0-23-generic Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: xunilarium(a)gmail.com Regression: No Created attachment 289165 --> https://bugzilla.kernel.org/attachment.cgi?id=289165&action=edit My Noisy Screen As linux kernel was updated to version 5 my laptop screen become noisy, I have same problem with all linux distros with kernel 5 and above. The problem is available both in graphic and text mode. windows works fine so my graphic card is OK. Ubunut 18.04.02: -------------------------------------------------------------------------------- Kernel Ver: 4.18.0-15-generic VGA Driver: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV620/M82 [Mobility Radeon HD 3450/3470] Subsystem: Sony Corporation RV620/M82 [Mobility Radeon HD 3450/3470] Kernel driver in use: radeon Kernel modules: radeon Screen Status: OK ________________________________________________________________________________ Ubuntu 18.04.03: -------------------------------------------------------------------------------- Kernel Ver: 5.0.0-23-generic VGA Driver: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV620/M82 [Mobility Radeon HD 3450/3470] Subsystem: Sony Corporation RV620/M82 [Mobility Radeon HD 3450/3470] Kernel driver in use: radeon Kernel modules: radeon Screen Status: Noisy -- You are receiving this mail because: You are watching the assignee of the bug.

1 10

[Bug 210787] New: amdgpu fan NA on multi gpu R9 nano
by bugzilla-daemon＠bugzilla.kernel.org 12 Dec '21

12 Dec '21

https://bugzilla.kernel.org/show_bug.cgi?id=210787 Bug ID: 210787 Summary: amdgpu fan NA on multi gpu R9 nano Product: Drivers Version: 2.5 Kernel Version: 5.9.12-5.10.1 Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: janpieter.sollie(a)edpnet.be Regression: No Created attachment 294229 --> https://bugzilla.kernel.org/attachment.cgi?id=294229&action=edit dmesg with manual GPU loading when running sensors, the 1st GPU fan (this GPU has the display attached) is unavailable: > amdgpu-pci-0700 > Adapter: PCI adapter > vddgfx: 900.00 mV > fan1: N/A (min = 1000 RPM, max = 4200 RPM) > edge: +23.0°C (crit = +89.0°C, hyst = -273.1°C) > power1: 10.23 W (cap = 150.00 W) > > amdgpu-pci-4300 > Adapter: PCI adapter > vddgfx: 850.00 mV > fan1: 1544 RPM (min = 1000 RPM, max = 4200 RPM) > edge: +26.0°C (crit = +89.0°C, hyst = -273.1°C) > power1: 10.08 W (cap = 150.00 W) blacklisting amdgpu did not help, but when breaking the config (specifying an invalid parameter in /etc/modprobe.d/amdgpu.conf), and loading it manually with correct parameters, it works. We're talking about a ryzen 1950x setup here with 2x r9 nano GPUs -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.

1 7

[syzbot] WARNING in drm_wait_one_vblank
by syzbot 12 Dec '21

12 Dec '21

Hello, syzbot found the following issue on: HEAD commit: d2b6f8a1 Merge tag 'xfs-5.13-merge-3' of git://git.kernel... git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=12c5b2c3d00000 kernel config: https://syzkaller.appspot.com/x/.config?x=65c207250bba4efe dashboard link: https://syzkaller.appspot.com/bug?extid=6f7fe2dbc479dca0ed17 Unfortunately, I don't have any reproducer for this issue yet. IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+6f7fe2dbc479dca0ed17(a)syzkaller.appspotmail.com ------------[ cut here ]------------ platform vkms: vblank wait timed out on crtc 0 WARNING: CPU: 0 PID: 11785 at drivers/gpu/drm/drm_vblank.c:1269 drm_wait_one_vblank+0x2be/0x500 drivers/gpu/drm/drm_vblank.c:1269 Modules linked in: CPU: 0 PID: 11785 Comm: syz-executor.0 Not tainted 5.12.0-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:drm_wait_one_vblank+0x2be/0x500 drivers/gpu/drm/drm_vblank.c:1269 Code: 85 f6 0f 84 a3 01 00 00 e8 6f f0 32 fd 4c 89 ef e8 97 68 13 00 44 89 e1 4c 89 f2 48 c7 c7 e0 eb d6 89 48 89 c6 e8 57 35 86 04 <0f> 0b e9 87 fe ff ff e8 46 f0 32 fd 31 ff 4c 89 ee e8 5c f8 32 fd RSP: 0018:ffffc90008f7fb40 EFLAGS: 00010282 RAX: 0000000000000000 RBX: 00000000000038f8 RCX: 0000000000000000 RDX: 0000000000040000 RSI: ffffffff815c7bd5 RDI: fffff520011eff5a RBP: ffff8881437b0000 R08: 0000000000000000 R09: 0000000000000000 R10: ffffffff815c1a3e R11: 0000000000000000 R12: 0000000000000000 R13: ffff88801a1c4010 R14: ffff8880161746b8 R15: ffff888142ddc830 FS: 00007f8eba6e2700(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000014a53ad CR3: 0000000021583000 CR4: 00000000001506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: drm_fb_helper_ioctl+0x159/0x1a0 drivers/gpu/drm/drm_fb_helper.c:1197 do_fb_ioctl+0x1d5/0x690 drivers/video/fbdev/core/fbmem.c:1171 fb_ioctl+0xe7/0x150 drivers/video/fbdev/core/fbmem.c:1185 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:1069 [inline] __se_sys_ioctl fs/ioctl.c:1055 [inline] __x64_sys_ioctl+0x193/0x200 fs/ioctl.c:1055 do_syscall_64+0x3a/0xb0 arch/x86/entry/common.c:47 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x4665f9 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 bc ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f8eba6e2188 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 000000000056bf60 RCX: 00000000004665f9 RDX: 0000000000000000 RSI: 0000000040044620 RDI: 0000000000000006 RBP: 00000000004bfce1 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 000000000056bf60 R13: 0000000000a9fb1f R14: 00007f8eba6e2300 R15: 0000000000022000 --- This report is generated by a bot. It may contain errors. See https://goo.gl/tpsmEJ for more information about syzbot. syzbot engineers can be reached at syzkaller(a)googlegroups.com. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

1 1

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel June 2021