dri-devel November 2018

dri-devel@lists.freedesktop.org

297 participants
2005 discussions

[Bug 89374] Firefox smooth scrolling isn't smooth
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=89374 Bug ID: 89374 Summary: Firefox smooth scrolling isn't smooth Product: DRI Version: XOrg git Hardware: Other OS: Linux (All) Status: NEW Severity: minor Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: sunweb(a)hotmail.ru Kubuntu 14.04 x64, HD5770 glxinfo |grep Open OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD JUNIPER OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.3.2 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.0 Mesa 10.3.2 OpenGL shading language version string: 1.30 OpenGL context flags: (none) Firefox has an option of smooth scrolling(Preferences -> General -> Use smooth scrolling). However it doesn't work on OSS drivers for my card. It does work on Intel ones and closed source though. -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 108644] driver/card crashes with latest polaris11 firmware
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=108644 Bug ID: 108644 Summary: driver/card crashes with latest polaris11 firmware Product: DRI Version: unspecified Hardware: PowerPC OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: dan(a)danny.cz CC: bcrocker(a)redhat.com Created attachment 142356 --> https://bugs.freedesktop.org/attachment.cgi?id=142356&action=edit dmesg-20181102 After updating to the latest polaris11 firmware (from linux-firmware-20181008-88.gitc6b6265d.fc28.noarch) I'm experiencing driver/card crashes. This is on a Power9 system running 4.19.0 kernel. There was no such crashes with the previous firmware and all 4.19-pre kernels (and even earlier). ... lis 02 11:54:00 talos.danny.cz kernel: EEH: Frozen PHB#0-PE#0 detected lis 02 11:54:00 talos.danny.cz kernel: EEH: PE location: N/A, PHB location: N/A lis 02 11:54:00 talos.danny.cz kernel: CPU: 35 PID: 3250 Comm: InputThread Not tainted 4.19.0-1.fc30.op.1.ppc64le #1 lis 02 11:54:00 talos.danny.cz kernel: Call Trace: lis 02 11:54:00 talos.danny.cz kernel: [c0002006af9bf810] [c000000000be3f9c] dump_stack+0xb0/0xf4 (unreliable) lis 02 11:54:00 talos.danny.cz kernel: [c0002006af9bf850] [c000000000040738] eeh_dev_check_failure+0x4a8/0x5d0 lis 02 11:54:00 talos.danny.cz kernel: [c0002006af9bf8f0] [c0000000000408ec] eeh_check_failure+0x8c/0xd0 lis 02 11:54:00 talos.danny.cz kernel: [c0002006af9bf930] [c00800000de61998] amdgpu_mm_rreg+0x240/0x2a0 [amdgpu] lis 02 11:54:00 talos.danny.cz kernel: [c0002006af9bf990] [c00800000df22a68] dce_v11_0_lock_cursor+0x50/0xf0 [amdgpu] lis 02 11:54:00 talos.danny.cz kernel: [c0002006af9bf9d0] [c00800000df236a0] dce_v11_0_crtc_cursor_move+0x38/0x80 [amdgpu] lis 02 11:54:00 talos.danny.cz kernel: [c0002006af9bfa10] [c00800000d11f248] drm_mode_cursor_common+0x1e0/0x2c0 [drm] lis 02 11:54:00 talos.danny.cz kernel: [c0002006af9bfae0] [c00800000d11f6c8] drm_mode_cursor_ioctl+0x50/0x70 [drm] lis 02 11:54:00 talos.danny.cz kernel: [c0002006af9bfb30] [c00800000d0f7f14] drm_ioctl_kernel+0xdc/0x170 [drm] lis 02 11:54:00 talos.danny.cz kernel: [c0002006af9bfb90] [c00800000d0f8414] drm_ioctl+0x20c/0x430 [drm] lis 02 11:54:00 talos.danny.cz kernel: [c0002006af9bfcd0] [c00800000de60078] amdgpu_drm_ioctl+0x70/0xd0 [amdgpu] lis 02 11:54:00 talos.danny.cz kernel: [c0002006af9bfd20] [c00000000040f0f4] do_vfs_ioctl+0xd4/0x8d0 lis 02 11:54:00 talos.danny.cz kernel: [c0002006af9bfdc0] [c00000000040f9b4] ksys_ioctl+0xc4/0x110 lis 02 11:54:00 talos.danny.cz kernel: [c0002006af9bfe10] [c00000000040fa28] sys_ioctl+0x28/0x80 lis 02 11:54:00 talos.danny.cz kernel: [c0002006af9bfe30] [c00000000000b9e4] system_call+0x5c/0x70 lis 02 11:54:00 talos.danny.cz kernel: EEH: Detected PCI bus error on PHB#0-PE#0 lis 02 11:54:00 talos.danny.cz kernel: EEH: This PCI device has failed 1 times in the last hour and will be permanently disabled after 5 failures. lis 02 11:54:00 talos.danny.cz kernel: EEH: Notify device drivers to shutdown lis 02 11:54:00 talos.danny.cz kernel: EEH: Beginning: 'error_detected(IO frozen)' lis 02 11:54:00 talos.danny.cz kernel: EEH: PE#0 (PCI 0000:01:00.1): driver not EEH aware lis 02 11:54:00 talos.danny.cz kernel: EEH: PE#0 (PCI 0000:01:00.0): driver not EEH aware lis 02 11:54:00 talos.danny.cz kernel: EEH: Finished:'error_detected(IO frozen)' with aggregate recovery state:'none' lis 02 11:54:00 talos.danny.cz kernel: EEH: Collect temporary log lis 02 11:54:00 talos.danny.cz kernel: EEH: of node=0000:01:00.1 lis 02 11:54:00 talos.danny.cz kernel: EEH: PCI device/vendor: aae01002 lis 02 11:54:00 talos.danny.cz kernel: EEH: PCI cmd/status register: 00100546 lis 02 11:54:00 talos.danny.cz kernel: EEH: PCI-E capabilities and status follow: lis 02 11:54:00 talos.danny.cz kernel: EEH: PCI-E 00: 0012a010 00008fa1 00002930 00400883 lis 02 11:54:00 talos.danny.cz kernel: EEH: PCI-E 10: 10810000 00000000 00000000 00000000 lis 02 11:54:00 talos.danny.cz kernel: EEH: PCI-E 20: 00000000 lis 02 11:54:00 talos.danny.cz kernel: EEH: PCI-E AER capability register set follows: lis 02 11:54:00 talos.danny.cz kernel: EEH: PCI-E AER 00: 32820001 00000000 00000000 00462030 lis 02 11:54:00 talos.danny.cz kernel: EEH: PCI-E AER 10: 00000000 00002000 000001e0 00000000 lis 02 11:54:00 talos.danny.cz kernel: EEH: PCI-E AER 20: 00000000 00000000 00000000 00000000 lis 02 11:54:00 talos.danny.cz kernel: EEH: PCI-E AER 30: 00000000 00000000 lis 02 11:54:00 talos.danny.cz kernel: EEH: of node=0000:01:00.0 lis 02 11:54:00 talos.danny.cz kernel: EEH: PCI device/vendor: 67e31002 lis 02 11:54:00 talos.danny.cz kernel: EEH: PCI cmd/status register: 00100546 lis 02 11:54:00 talos.danny.cz kernel: EEH: PCI-E capabilities and status follow: lis 02 11:54:00 talos.danny.cz kernel: EEH: PCI-E 00: 0012a010 00008fa1 00002930 00400883 lis 02 11:54:00 talos.danny.cz kernel: EEH: PCI-E 10: 10810000 00000000 00000000 00000000 lis 02 11:54:00 talos.danny.cz kernel: EEH: PCI-E 20: 00000000 lis 02 11:54:00 talos.danny.cz kernel: EEH: PCI-E AER capability register set follows: lis 02 11:54:00 talos.danny.cz kernel: EEH: PCI-E AER 00: 20020001 00000000 00000000 00462030 lis 02 11:54:00 talos.danny.cz kernel: EEH: PCI-E AER 10: 00000000 00002000 000001e0 00000000 lis 02 11:54:00 talos.danny.cz kernel: EEH: PCI-E AER 20: 00000000 00000000 00000000 00000000 lis 02 11:54:00 talos.danny.cz kernel: EEH: PCI-E AER 30: 00000000 00000000 lis 02 11:54:00 talos.danny.cz kernel: PHB4 PHB#0 Diag-data (Version: 1) lis 02 11:54:00 talos.danny.cz kernel: brdgCtl: 00000002 lis 02 11:54:00 talos.danny.cz kernel: RootSts: 00060020 00402000 a0810008 00100107 00000800 lis 02 11:54:00 talos.danny.cz kernel: PhbSts: 0000001c00000000 0000001c00000000 lis 02 11:54:00 talos.danny.cz kernel: Lem: 0000000100000080 0000000000000000 0000000000000080 lis 02 11:54:00 talos.danny.cz kernel: PhbErr: 0000028000000000 0000020000000000 2148000098000240 a008400000000000 lis 02 11:54:00 talos.danny.cz kernel: RxeTceErr: 2000000000000000 2000000000000000 c000000000000000 0000000000000000 lis 02 11:54:00 talos.danny.cz kernel: PblErr: 0000000000020000 0000000000020000 0000000000000000 0000000000000000 lis 02 11:54:00 talos.danny.cz kernel: RegbErr: 0000004000000000 0000004000000000 8800001c00000000 0000000000000200 lis 02 11:54:00 talos.danny.cz kernel: PE[000] A/B: 8300b03800000000 8000000000000000 lis 02 11:54:00 talos.danny.cz kernel: EEH: Reset with hotplug activity lis 02 11:54:00 talos.danny.cz kernel: iommu: Removing device 0000:01:00.1 from group 0 lis 02 11:54:00 talos.danny.cz kernel: pci 0000:01:00.1: Dropping the link to 0000:01:00.0 lis 02 11:54:00 talos.danny.cz kernel: [drm] amdgpu: finishing device. lis 02 11:54:04 talos.danny.cz kernel: EEH: 2100000 reads ignored for recovering device at location=unknown driver=amdgpu pci addr=0000:01:00.0 lis 02 11:54:04 talos.danny.cz kernel: EEH: Might be infinite loop in amdgpu driver lis 02 11:54:04 talos.danny.cz kernel: CPU: 8 PID: 335 Comm: eehd Not tainted 4.19.0-1.fc30.op.1.ppc64le #1 lis 02 11:54:04 talos.danny.cz kernel: Call Trace: lis 02 11:54:04 talos.danny.cz kernel: [c0000007f8516ed0] [c000000000be3f9c] dump_stack+0xb0/0xf4 (unreliable) lis 02 11:54:04 talos.danny.cz kernel: [c0000007f8516f10] [c000000000040640] eeh_dev_check_failure+0x3b0/0x5d0 lis 02 11:54:04 talos.danny.cz kernel: [c0000007f8516fb0] [c0000000000408ec] eeh_check_failure+0x8c/0xd0 lis 02 11:54:04 talos.danny.cz kernel: [c0000007f8516ff0] [c00800000de61998] amdgpu_mm_rreg+0x240/0x2a0 [amdgpu] lis 02 11:54:04 talos.danny.cz kernel: [c0000007f8517050] [c00800000de68904] cail_reg_read+0x2c/0x50 [amdgpu] lis 02 11:54:04 talos.danny.cz kernel: [c0000007f8517070] [c00800000de7123c] atom_get_src_int+0x104/0xa00 [amdgpu] lis 02 11:54:04 talos.danny.cz kernel: [c0000007f8517120] [c00800000de72b10] atom_op_test+0xd8/0x1d0 [amdgpu] lis 02 11:54:04 talos.danny.cz kernel: [c0000007f85171b0] [c00800000de74d7c] amdgpu_atom_execute_table_locked+0x204/0x380 [amdgpu] lis 02 11:54:04 talos.danny.cz kernel: [c0000007f85172a0] [c00800000de75020] atom_op_calltable+0x128/0x1e0 [amdgpu] lis 02 11:54:04 talos.danny.cz kernel: [c0000007f8517320] [c00800000de74d7c] amdgpu_atom_execute_table_locked+0x204/0x380 [amdgpu] lis 02 11:54:04 talos.danny.cz kernel: [c0000007f8517410] [c00800000de758f8] amdgpu_atom_execute_table+0x70/0xb0 [amdgpu] lis 02 11:54:04 talos.danny.cz kernel: [c0000007f8517450] [c00800000de96fc0] amdgpu_atombios_encoder_setup_dig_transmitter+0x1d8/0xc10 [amdgpu] lis 02 11:54:04 talos.danny.cz kernel: [c0000007f8517540] [c00800000de97e58] amdgpu_atombios_encoder_dpms+0x1a0/0x5a0 [amdgpu] lis 02 11:54:04 talos.danny.cz kernel: [c0000007f85175d0] [c00800000df255a4] dce_v11_0_encoder_disable+0x2c/0x160 [amdgpu] lis 02 11:54:04 talos.danny.cz kernel: [c0000007f8517640] [c00800000d4803e8] drm_encoder_disable+0x60/0xc0 [drm_kms_helper] lis 02 11:54:04 talos.danny.cz kernel: [c0000007f8517670] [c00800000d4804c8] __drm_helper_disable_unused_functions+0x80/0x160 [drm_kms_helper] lis 02 11:54:04 talos.danny.cz kernel: [c0000007f85176b0] [c00800000d481ad0] drm_crtc_helper_set_config+0x978/0xb70 [drm_kms_helper] lis 02 11:54:04 talos.danny.cz kernel: [c0000007f85177c0] [c00800000de7f958] amdgpu_display_crtc_set_config+0x70/0x1c0 [amdgpu] lis 02 11:54:04 talos.danny.cz kernel: [c0000007f8517800] [c00800000d0ff274] __drm_mode_set_config_internal+0xac/0x1a0 [drm] lis 02 11:54:04 talos.danny.cz kernel: [c0000007f8517850] [c00800000d0ff450] drm_crtc_force_disable+0x88/0xa0 [drm] lis 02 11:54:04 talos.danny.cz kernel: [c0000007f85178a0] [c00800000d0ff4e4] drm_crtc_force_disable_all+0x7c/0x100 [drm] lis 02 11:54:04 talos.danny.cz kernel: [c0000007f85178e0] [c00800000e0553f4] amdgpu_device_fini+0xa0/0x628 [amdgpu] lis 02 11:54:04 talos.danny.cz kernel: [c0000007f8517990] [c00800000de67b04] amdgpu_driver_unload_kms+0x6c/0x100 [amdgpu] lis 02 11:54:04 talos.danny.cz kernel: [c0000007f85179c0] [c00800000d0fa978] drm_dev_unregister+0x80/0x170 [drm] lis 02 11:54:04 talos.danny.cz kernel: [c0000007f8517a00] [c00800000de6055c] amdgpu_pci_remove+0x34/0x80 [amdgpu] lis 02 11:54:04 talos.danny.cz kernel: [c0000007f8517a30] [c0000000006d91dc] pci_device_remove+0x6c/0x120 lis 02 11:54:04 talos.danny.cz kernel: [c0000007f8517a70] [c000000000790410] device_release_driver_internal+0x290/0x370 lis 02 11:54:04 talos.danny.cz kernel: [c0000007f8517ac0] [c0000000006cc718] pci_stop_bus_device+0xb8/0x110 lis 02 11:54:04 talos.danny.cz kernel: [c0000007f8517b00] [c0000000006cc918] pci_stop_and_remove_bus_device+0x28/0x40 lis 02 11:54:04 talos.danny.cz kernel: [c0000007f8517b30] [c000000000066ac0] pci_hp_remove_devices+0x90/0x130 lis 02 11:54:04 talos.danny.cz kernel: [c0000007f8517bc0] [c000000000045f40] eeh_reset_device+0xa0/0x1f4 lis 02 11:54:04 talos.danny.cz kernel: [c0000007f8517c50] [c0000000000455c8] eeh_handle_normal_event+0x2b8/0x650 lis 02 11:54:04 talos.danny.cz kernel: [c0000007f8517d10] [c000000000046710] eeh_event_handler+0x1c0/0x1e0 lis 02 11:54:04 talos.danny.cz kernel: [c0000007f8517dc0] [c00000000014900c] kthread+0x1ac/0x1c0 lis 02 11:54:04 talos.danny.cz kernel: [c0000007f8517e30] [c00000000000bdd4] ret_from_kernel_thread+0x5c/0x68 lis 02 11:54:05 talos.danny.cz kernel: [drm:atom_op_jump [amdgpu]] *ERROR* atombios stuck in loop for more than 5secs aborting lis 02 11:54:05 talos.danny.cz kernel: [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing D860 (len 824, WS 0, PS 0) @ 0xD9E0 lis 02 11:54:05 talos.danny.cz kernel: [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing D71A (len 326, WS 0, PS 0) @ 0xD80A lis 02 11:54:07 talos.danny.cz kernel: EEH: 4200000 reads ignored for recovering device at location=unknown driver=amdgpu pci addr=0000:01:00.0 lis 02 11:54:07 talos.danny.cz kernel: EEH: Might be infinite loop in amdgpu driver lis 02 11:54:07 talos.danny.cz kernel: CPU: 9 PID: 335 Comm: eehd Not tainted 4.19.0-1.fc30.op.1.ppc64le #1 lis 02 11:54:07 talos.danny.cz kernel: Call Trace: lis 02 11:54:07 talos.danny.cz kernel: [c0000007f8517120] [c000000000be3f9c] dump_stack+0xb0/0xf4 (unreliable) lis 02 11:54:07 talos.danny.cz kernel: [c0000007f8517160] [c000000000040640] eeh_dev_check_failure+0x3b0/0x5d0 lis 02 11:54:07 talos.danny.cz kernel: [c0000007f8517200] [c0000000000408ec] eeh_check_failure+0x8c/0xd0 lis 02 11:54:07 talos.danny.cz kernel: [c0000007f8517240] [c00800000de61998] amdgpu_mm_rreg+0x240/0x2a0 [amdgpu] lis 02 11:54:07 talos.danny.cz kernel: [c0000007f85172a0] [c00800000de68904] cail_reg_read+0x2c/0x50 [amdgpu] lis 02 11:54:07 talos.danny.cz kernel: [c0000007f85172c0] [c00800000de7123c] atom_get_src_int+0x104/0xa00 [amdgpu] lis 02 11:54:07 talos.danny.cz kernel: [c0000007f8517370] [c00800000de72b10] atom_op_test+0xd8/0x1d0 [amdgpu] lis 02 11:54:07 talos.danny.cz kernel: [c0000007f8517400] [c00800000de74d7c] amdgpu_atom_execute_table_locked+0x204/0x380 [amdgpu] lis 02 11:54:07 talos.danny.cz kernel: [c0000007f85174f0] [c00800000de758f8] amdgpu_atom_execute_table+0x70/0xb0 [amdgpu] lis 02 11:54:07 talos.danny.cz kernel: [c0000007f8517530] [c00800000de6c154] amdgpu_atombios_crtc_blank+0x4c/0x70 [amdgpu] lis 02 11:54:07 talos.danny.cz kernel: [c0000007f8517560] [c00800000df23ff8] dce_v11_0_crtc_dpms+0x170/0x1b0 [amdgpu] lis 02 11:54:07 talos.danny.cz kernel: [c0000007f85175a0] [c00800000df28e50] dce_v11_0_crtc_disable+0x38/0x2e0 [amdgpu] lis 02 11:54:07 talos.danny.cz kernel: [c0000007f8517670] [c00800000d48050c] __drm_helper_disable_unused_functions+0xc4/0x160 [drm_kms_helper] lis 02 11:54:07 talos.danny.cz kernel: [c0000007f85176b0] [c00800000d481ad0] drm_crtc_helper_set_config+0x978/0xb70 [drm_kms_helper] lis 02 11:54:07 talos.danny.cz kernel: [c0000007f85177c0] [c00800000de7f958] amdgpu_display_crtc_set_config+0x70/0x1c0 [amdgpu] lis 02 11:54:07 talos.danny.cz kernel: [c0000007f8517800] [c00800000d0ff274] __drm_mode_set_config_internal+0xac/0x1a0 [drm] lis 02 11:54:07 talos.danny.cz kernel: [c0000007f8517850] [c00800000d0ff450] drm_crtc_force_disable+0x88/0xa0 [drm] lis 02 11:54:07 talos.danny.cz kernel: [c0000007f85178a0] [c00800000d0ff4e4] drm_crtc_force_disable_all+0x7c/0x100 [drm] lis 02 11:54:07 talos.danny.cz kernel: [c0000007f85178e0] [c00800000e0553f4] amdgpu_device_fini+0xa0/0x628 [amdgpu] lis 02 11:54:07 talos.danny.cz kernel: [c0000007f8517990] [c00800000de67b04] amdgpu_driver_unload_kms+0x6c/0x100 [amdgpu] lis 02 11:54:07 talos.danny.cz kernel: [c0000007f85179c0] [c00800000d0fa978] drm_dev_unregister+0x80/0x170 [drm] lis 02 11:54:07 talos.danny.cz kernel: [c0000007f8517a00] [c00800000de6055c] amdgpu_pci_remove+0x34/0x80 [amdgpu] lis 02 11:54:07 talos.danny.cz kernel: [c0000007f8517a30] [c0000000006d91dc] pci_device_remove+0x6c/0x120 lis 02 11:54:07 talos.danny.cz kernel: [c0000007f8517a70] [c000000000790410] device_release_driver_internal+0x290/0x370 lis 02 11:54:07 talos.danny.cz kernel: [c0000007f8517ac0] [c0000000006cc718] pci_stop_bus_device+0xb8/0x110 lis 02 11:54:07 talos.danny.cz kernel: [c0000007f8517b00] [c0000000006cc918] pci_stop_and_remove_bus_device+0x28/0x40 lis 02 11:54:07 talos.danny.cz kernel: [c0000007f8517b30] [c000000000066ac0] pci_hp_remove_devices+0x90/0x130 lis 02 11:54:07 talos.danny.cz kernel: [c0000007f8517bc0] [c000000000045f40] eeh_reset_device+0xa0/0x1f4 lis 02 11:54:07 talos.danny.cz kernel: [c0000007f8517c50] [c0000000000455c8] eeh_handle_normal_event+0x2b8/0x650 lis 02 11:54:07 talos.danny.cz kernel: [c0000007f8517d10] [c000000000046710] eeh_event_handler+0x1c0/0x1e0 lis 02 11:54:07 talos.danny.cz kernel: [c0000007f8517dc0] [c00000000014900c] kthread+0x1ac/0x1c0 lis 02 11:54:07 talos.danny.cz kernel: [c0000007f8517e30] [c00000000000bdd4] ret_from_kernel_thread+0x5c/0x68 lis 02 11:54:08 talos.danny.cz kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=134395, emitted seq=134397 lis 02 11:54:08 talos.danny.cz kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma1 timeout, signaled seq=54428, emitted seq=54430 lis 02 11:54:08 talos.danny.cz kernel: [drm] GPU recovery disabled. lis 02 11:54:08 talos.danny.cz kernel: [drm] GPU recovery disabled. lis 02 11:54:10 talos.danny.cz kernel: [drm:atom_op_jump [amdgpu]] *ERROR* atombios stuck in loop for more than 5secs aborting lis 02 11:54:10 talos.danny.cz kernel: [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing C1E0 (len 116, WS 0, PS 0) @ 0xC22D lis 02 11:54:10 talos.danny.cz kernel: EEH: 6300000 reads ignored for recovering device at location=unknown driver=amdgpu pci addr=0000:01:00.0 lis 02 11:54:10 talos.danny.cz kernel: EEH: Might be infinite loop in amdgpu driver lis 02 11:54:10 talos.danny.cz kernel: CPU: 11 PID: 335 Comm: eehd Not tainted 4.19.0-1.fc30.op.1.ppc64le #1 lis 02 11:54:10 talos.danny.cz kernel: Call Trace: lis 02 11:54:10 talos.danny.cz kernel: [c0000007f8517120] [c000000000be3f9c] dump_stack+0xb0/0xf4 (unreliable) lis 02 11:54:10 talos.danny.cz kernel: [c0000007f8517160] [c000000000040640] eeh_dev_check_failure+0x3b0/0x5d0 lis 02 11:54:10 talos.danny.cz kernel: [c0000007f8517200] [c0000000000408ec] eeh_check_failure+0x8c/0xd0 lis 02 11:54:10 talos.danny.cz kernel: [c0000007f8517240] [c00800000de61998] amdgpu_mm_rreg+0x240/0x2a0 [amdgpu] lis 02 11:54:10 talos.danny.cz kernel: [c0000007f85172a0] [c00800000de68904] cail_reg_read+0x2c/0x50 [amdgpu] lis 02 11:54:10 talos.danny.cz kernel: [c0000007f85172c0] [c00800000de7123c] atom_get_src_int+0x104/0xa00 [amdgpu] lis 02 11:54:10 talos.danny.cz kernel: [c0000007f8517370] [c00800000de72b10] atom_op_test+0xd8/0x1d0 [amdgpu] lis 02 11:54:10 talos.danny.cz kernel: [c0000007f8517400] [c00800000de74d7c] amdgpu_atom_execute_table_locked+0x204/0x380 [amdgpu] lis 02 11:54:10 talos.danny.cz kernel: [c0000007f85174f0] [c00800000de758f8] amdgpu_atom_execute_table+0x70/0xb0 [amdgpu] lis 02 11:54:10 talos.danny.cz kernel: [c0000007f8517530] [c00800000de6c0e0] amdgpu_atombios_crtc_enable+0x48/0x70 [amdgpu] lis 02 11:54:10 talos.danny.cz kernel: [c0000007f8517560] [c00800000df24014] dce_v11_0_crtc_dpms+0x18c/0x1b0 [amdgpu] lis 02 11:54:10 talos.danny.cz kernel: [c0000007f85175a0] [c00800000df28e50] dce_v11_0_crtc_disable+0x38/0x2e0 [amdgpu] lis 02 11:54:10 talos.danny.cz kernel: [c0000007f8517670] [c00800000d48050c] __drm_helper_disable_unused_functions+0xc4/0x160 [drm_kms_helper] lis 02 11:54:10 talos.danny.cz kernel: [c0000007f85176b0] [c00800000d481ad0] drm_crtc_helper_set_config+0x978/0xb70 [drm_kms_helper] lis 02 11:54:10 talos.danny.cz kernel: [c0000007f85177c0] [c00800000de7f958] amdgpu_display_crtc_set_config+0x70/0x1c0 [amdgpu] lis 02 11:54:10 talos.danny.cz kernel: [c0000007f8517800] [c00800000d0ff274] __drm_mode_set_config_internal+0xac/0x1a0 [drm] lis 02 11:54:10 talos.danny.cz kernel: [c0000007f8517850] [c00800000d0ff450] drm_crtc_force_disable+0x88/0xa0 [drm] lis 02 11:54:10 talos.danny.cz kernel: [c0000007f85178a0] [c00800000d0ff4e4] drm_crtc_force_disable_all+0x7c/0x100 [drm] lis 02 11:54:10 talos.danny.cz kernel: [c0000007f85178e0] [c00800000e0553f4] amdgpu_device_fini+0xa0/0x628 [amdgpu] lis 02 11:54:10 talos.danny.cz kernel: [c0000007f8517990] [c00800000de67b04] amdgpu_driver_unload_kms+0x6c/0x100 [amdgpu] lis 02 11:54:10 talos.danny.cz kernel: [c0000007f85179c0] [c00800000d0fa978] drm_dev_unregister+0x80/0x170 [drm] lis 02 11:54:10 talos.danny.cz kernel: [c0000007f8517a00] [c00800000de6055c] amdgpu_pci_remove+0x34/0x80 [amdgpu] lis 02 11:54:10 talos.danny.cz kernel: [c0000007f8517a30] [c0000000006d91dc] pci_device_remove+0x6c/0x120 lis 02 11:54:10 talos.danny.cz kernel: [c0000007f8517a70] [c000000000790410] device_release_driver_internal+0x290/0x370 lis 02 11:54:10 talos.danny.cz kernel: [c0000007f8517ac0] [c0000000006cc718] pci_stop_bus_device+0xb8/0x110 lis 02 11:54:10 talos.danny.cz kernel: [c0000007f8517b00] [c0000000006cc918] pci_stop_and_remove_bus_device+0x28/0x40 lis 02 11:54:10 talos.danny.cz kernel: [c0000007f8517b30] [c000000000066ac0] pci_hp_remove_devices+0x90/0x130 lis 02 11:54:10 talos.danny.cz kernel: [c0000007f8517bc0] [c000000000045f40] eeh_reset_device+0xa0/0x1f4 lis 02 11:54:10 talos.danny.cz kernel: [c0000007f8517c50] [c0000000000455c8] eeh_handle_normal_event+0x2b8/0x650 lis 02 11:54:10 talos.danny.cz kernel: [c0000007f8517d10] [c000000000046710] eeh_event_handler+0x1c0/0x1e0 lis 02 11:54:10 talos.danny.cz kernel: [c0000007f8517dc0] [c00000000014900c] kthread+0x1ac/0x1c0 lis 02 11:54:10 talos.danny.cz kernel: [c0000007f8517e30] [c00000000000bdd4] ret_from_kernel_thread+0x5c/0x68 lis 02 11:54:13 talos.danny.cz kernel: EEH: 8400000 reads ignored for recovering device at location=unknown driver=amdgpu pci addr=0000:01:00.0 lis 02 11:54:13 talos.danny.cz kernel: EEH: Might be infinite loop in amdgpu driver lis 02 11:54:13 talos.danny.cz kernel: CPU: 11 PID: 335 Comm: eehd Not tainted 4.19.0-1.fc30.op.1.ppc64le #1 lis 02 11:54:13 talos.danny.cz kernel: Call Trace: lis 02 11:54:13 talos.danny.cz kernel: [c0000007f8517120] [c000000000be3f9c] dump_stack+0xb0/0xf4 (unreliable) lis 02 11:54:13 talos.danny.cz kernel: [c0000007f8517160] [c000000000040640] eeh_dev_check_failure+0x3b0/0x5d0 lis 02 11:54:13 talos.danny.cz kernel: [c0000007f8517200] [c0000000000408ec] eeh_check_failure+0x8c/0xd0 lis 02 11:54:13 talos.danny.cz kernel: [c0000007f8517240] [c00800000de61998] amdgpu_mm_rreg+0x240/0x2a0 [amdgpu] lis 02 11:54:13 talos.danny.cz kernel: [c0000007f85172a0] [c00800000de68904] cail_reg_read+0x2c/0x50 [amdgpu] lis 02 11:54:13 talos.danny.cz kernel: [c0000007f85172c0] [c00800000de7123c] atom_get_src_int+0x104/0xa00 [amdgpu] lis 02 11:54:13 talos.danny.cz kernel: [c0000007f8517370] [c00800000de72b10] atom_op_test+0xd8/0x1d0 [amdgpu] lis 02 11:54:13 talos.danny.cz kernel: [c0000007f8517400] [c00800000de74d7c] amdgpu_atom_execute_table_locked+0x204/0x380 [amdgpu] lis 02 11:54:13 talos.danny.cz kernel: [c0000007f85174f0] [c00800000de758f8] amdgpu_atom_execute_table+0x70/0xb0 [amdgpu] lis 02 11:54:13 talos.danny.cz kernel: [c0000007f8517530] [c00800000de6c0e0] amdgpu_atombios_crtc_enable+0x48/0x70 [amdgpu] lis 02 11:54:13 talos.danny.cz kernel: [c0000007f8517560] [c00800000df24014] dce_v11_0_crtc_dpms+0x18c/0x1b0 [amdgpu] lis 02 11:54:13 talos.danny.cz kernel: [c0000007f85175a0] [c00800000df28e50] dce_v11_0_crtc_disable+0x38/0x2e0 [amdgpu] lis 02 11:54:13 talos.danny.cz kernel: [c0000007f8517670] [c00800000d48050c] __drm_helper_disable_unused_functions+0xc4/0x160 [drm_kms_helper] lis 02 11:54:13 talos.danny.cz kernel: [c0000007f85176b0] [c00800000d481ad0] drm_crtc_helper_set_config+0x978/0xb70 [drm_kms_helper] lis 02 11:54:13 talos.danny.cz kernel: [c0000007f85177c0] [c00800000de7f958] amdgpu_display_crtc_set_config+0x70/0x1c0 [amdgpu] lis 02 11:54:13 talos.danny.cz kernel: [c0000007f8517800] [c00800000d0ff274] __drm_mode_set_config_internal+0xac/0x1a0 [drm] lis 02 11:54:13 talos.danny.cz kernel: [c0000007f8517850] [c00800000d0ff450] drm_crtc_force_disable+0x88/0xa0 [drm] lis 02 11:54:13 talos.danny.cz kernel: [c0000007f85178a0] [c00800000d0ff4e4] drm_crtc_force_disable_all+0x7c/0x100 [drm] lis 02 11:54:13 talos.danny.cz kernel: [c0000007f85178e0] [c00800000e0553f4] amdgpu_device_fini+0xa0/0x628 [amdgpu] lis 02 11:54:13 talos.danny.cz kernel: [c0000007f8517990] [c00800000de67b04] amdgpu_driver_unload_kms+0x6c/0x100 [amdgpu] lis 02 11:54:13 talos.danny.cz kernel: [c0000007f85179c0] [c00800000d0fa978] drm_dev_unregister+0x80/0x170 [drm] lis 02 11:54:13 talos.danny.cz kernel: [c0000007f8517a00] [c00800000de6055c] amdgpu_pci_remove+0x34/0x80 [amdgpu] lis 02 11:54:13 talos.danny.cz kernel: [c0000007f8517a30] [c0000000006d91dc] pci_device_remove+0x6c/0x120 lis 02 11:54:13 talos.danny.cz kernel: [c0000007f8517a70] [c000000000790410] device_release_driver_internal+0x290/0x370 lis 02 11:54:13 talos.danny.cz kernel: [c0000007f8517ac0] [c0000000006cc718] pci_stop_bus_device+0xb8/0x110 lis 02 11:54:13 talos.danny.cz kernel: [c0000007f8517b00] [c0000000006cc918] pci_stop_and_remove_bus_device+0x28/0x40 lis 02 11:54:13 talos.danny.cz kernel: [c0000007f8517b30] [c000000000066ac0] pci_hp_remove_devices+0x90/0x130 lis 02 11:54:13 talos.danny.cz kernel: [c0000007f8517bc0] [c000000000045f40] eeh_reset_device+0xa0/0x1f4 lis 02 11:54:13 talos.danny.cz kernel: [c0000007f8517c50] [c0000000000455c8] eeh_handle_normal_event+0x2b8/0x650 lis 02 11:54:13 talos.danny.cz kernel: [c0000007f8517d10] [c000000000046710] eeh_event_handler+0x1c0/0x1e0 lis 02 11:54:13 talos.danny.cz kernel: [c0000007f8517dc0] [c00000000014900c] kthread+0x1ac/0x1c0 lis 02 11:54:13 talos.danny.cz kernel: [c0000007f8517e30] [c00000000000bdd4] ret_from_kernel_thread+0x5c/0x68 lis 02 11:54:15 talos.danny.cz kernel: [drm:atom_op_jump [amdgpu]] *ERROR* atombios stuck in loop for more than 5secs aborting lis 02 11:54:15 talos.danny.cz kernel: [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing C254 (len 62, WS 0, PS 0) @ 0xC270 lis 02 11:57:13 talos.danny.cz kernel: alsactl[2517]: segfault (11) at 28 nip 122708cfc lr 122708db0 code 1 in alsactl[1226f0000+20000] lis 02 11:57:13 talos.danny.cz kernel: alsactl[2517]: code: 4bfee1f5 e8410018 00000000 01000000 00000280 3c4c0003 3842f220 7c0802a6 lis 02 11:57:13 talos.danny.cz kernel: alsactl[2517]: code: fbc1fff0 f8010010 f821ffc1 7c7e1b78 <81240000> 2f890000 409d0048 fba10028 lis 02 12:01:43 talos.danny.cz kernel: opal-power: Poweroff requested -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 89275] PC sometimes hangs on suspend
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=89275 Bug ID: 89275 Summary: PC sometimes hangs on suspend Product: Mesa Version: 10.3 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: sunweb(a)hotmail.ru QA Contact: dri-devel(a)lists.freedesktop.org Kubuntu 14.04.2, Radeon HD5770. When i am going on suspend mode(RAM) screen goes black and then PC might or might not go into this mode. Sometimes it just hangs on black screen part and thats it. It happened to me with all of the previous drivers(and mesa 10.1) but i've seen once back then so i thought its a rare bug. Filled ram or not, i don't what may be the cause and where to look for errors to post here, so if you'll tell me where to look i'll post them. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 108637] kernel 4.19.0-arch1-1-ARCH - raven ridge
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=108637 Bug ID: 108637 Summary: kernel 4.19.0-arch1-1-ARCH - raven ridge 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: bibitocarlos(a)gmail.com Created attachment 142342 --> https://bugs.freedesktop.org/attachment.cgi?id=142342&action=edit raven ridge 2400 Hi, My computer, Raven ridge 2400G with Asrock X470 Gaming-ITX/ac, BIOS P1.30 07/05/2018. With 4.18, everything worked except failures at boot and suspend to ram. With 4.19.0-arch1-1-ARCH, the failures at boot are gone but i get a lot of warnings in dmesg and failures at use. See my dmesg. Please tell me if you need something else. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 89241] A8-6410 APU with integrated R5 Mullins + dedicated R5 M240 Hainan graphics switching not working
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=89241 Bug ID: 89241 Summary: A8-6410 APU with integrated R5 Mullins + dedicated R5 M240 Hainan graphics switching not working 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: linux5(a)secure-mail.biz Switching graphics between the A8-6410 APU with integrated R5 Mullins + dedicated R5 M240 Hainan is not working(HP 355 G2 notebook). I think it's because the dedicated gpu for some reason can just not be activated, because "/sys/kernel/debug/vgaswitcheroo/switch" and the Radeon Profile tool show two gpus, but changing the gpu state from "off" to something else within Radeon Profile doesn't work for the dedicated one. I tried the gearsongallium livecd with very recent drivers/Xorg/etc. Versions included in the gearsongallium livedvd i tested: Mesa-git – 10.5_git2015.02.04 Kernel – 3.19-rc6 libdrm – 2.4.99_git2015.01.22 Mesa-demos – 9.1.0_git2014.07.06 xorg-server – 1.16.99.9 xf86-video-ati – 7.99.99_2015.01.15 I also tried in Kubuntu 14.10 to switch with DRI_PRIME=1. If i do that i get corrupt window and lower fps than with integrated gpu with es2gears. However "DRI_PRIME=1 glxinfo" says it's using the dedicated gpu. In gearsongallium i get the same output with or without "DRI_PRIME=1 glxinfo" so it seems to not switch at all with recent drivers/Xorg/etc. I can also post Xorg log and dmesg output, but i couldn't spot anything unusual there looking quickly through it. However "dmesg|grep -i vga" might be important: $ dmesg |grep -i vga [ 1.069056] vgaarb: setting as boot device: PCI:0000:00:01.0 [ 1.069061] vgaarb: device added: PCI:0000:00:01.0,decodes=io+mem,owns=io+mem,locks=none [ 1.069077] vgaarb: loaded [ 1.069080] vgaarb: bridge control possible 0000:00:01.0 [ 1.763179] fb0: EFI VGA frame buffer device [ 2.029145] ACPI: Video Device [VGA] (multi-head: yes rom: no post: no) [ 2.115398] VGA switcheroo: detected switching method \_SB_.PCI0.VGA_.ATPX handle [ 2.191102] ACPI: Video Device [VGA1] (multi-head: yes rom: no post: no) [ 2.255714] fb: switching to radeondrmfb from EFI VGA [ 2.440405] [drm] VGA-1 [ 2.527423] vga_switcheroo: enabled -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 89155] Dual monitor setup does not initialize
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=89155 Bug ID: 89155 Summary: Dual monitor setup does not initialize 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: adam.reichold(a)t-online.de Created attachment 113508 --> https://bugs.freedesktop.org/attachment.cgi?id=113508&action=edit journalctl -b | grep "\[drm" I am running Arch Linux on an AMD A6-3500 with Radeon HD 6530D graphics on an Gigabyte A55M-S2V mainboard. I just received updated X server to version 1.17.1 together with a rebuilt version 7.5.0 of the XFree86 ATI driver with the kernel staying at 3.18.6. I do have two Samsung monitors connected to the system, one via DVI and one via VGA. This setup always initialized unreliably and I had to manually add modes for the VGA-connected monitor using xrandr --newmode "1680x1050_60.00" 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync xrandr --addmode VGA-0 "1680x1050_60.00" xrandr --output VGA-0 --mode "1680x1050_60.00" for it to work at all. But after the update described above, the two monitors never initialize properly anymore. Before the update, I sometimes had to power-cycle (meaning switch off power not just a reboot) but it did eventually work after two or three tries. The reason I am reporting this as a Radeon DRM issue instead of an X server problem is that my system log contains errors from the DRM driver about "channel eq" and "clock recovery". I attached those logs grepped for "[drm". Thank for your help and please tell me if I can provide any further information to help diagnose this. -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 108609] vegam_smumgr.c: accessing mvdd_voltage_table.entries[] array out of bounds in function vegam_populate_smc_mvdd_table
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=108609 Bug ID: 108609 Summary: vegam_smumgr.c: accessing mvdd_voltage_table.entries[] array out of bounds in function vegam_populate_smc_mvdd_table 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: rstrube(a)gmail.com Created attachment 142298 --> https://bugs.freedesktop.org/attachment.cgi?id=142298&action=edit Patch to fix accessing mvdd_voltage_table.entries[] array out of bounds in vegam_smumgr.c I believe I've discovered a small bug in the vegam_smumgr.c, specifically the following function: static int vegam_populate_smc_mvdd_table(struct pp_hwmgr *hwmgr, SMU75_Discrete_DpmTable *table) { struct smu7_hwmgr *data = (struct smu7_hwmgr *)(hwmgr->backend); uint32_t count, level; if (SMU7_VOLTAGE_CONTROL_BY_GPIO == data->mvdd_control) { count = data->mvdd_voltage_table.count; if (count > SMU_MAX_SMIO_LEVELS) count = SMU_MAX_SMIO_LEVELS; for (level = 0; level < count; level++) { table->SmioTable2.Pattern[level].Voltage = PP_HOST_TO_SMC_US( data->mvdd_voltage_table.entries[count].value * VOLTAGE_SCALE); /* Index into DpmTable.Smio. Drive bits from Smio entry to get this voltage level.*/ table->SmioTable2.Pattern[level].Smio = (uint8_t) level; table->Smio[level] |= data->mvdd_voltage_table.entries[level].smio_low; } table->SmioMask2 = data->mvdd_voltage_table.mask_low; table->MvddLevelCount = (uint32_t) PP_HOST_TO_SMC_UL(count); } return 0; } With the lines (within the for loop): table->SmioTable2.Pattern[level].Voltage = PP_HOST_TO_SMC_US( data->mvdd_voltage_table.entries[count].value * VOLTAGE_SCALE); If this code was executed it would try to access the mvdd_voltage_table.entries[] array out of bounds, because count > than the max value for level. I believe: data->mvdd_voltage_table.entries[count].value should actually be: data->mvdd_voltage_table.entries[level].value You can see in a similar function within vegam_smumgr.c, this bug is *not* present: static int vegam_populate_smc_vddci_table(struct pp_hwmgr *hwmgr, struct SMU75_Discrete_DpmTable *table) { uint32_t count, level; struct smu7_hwmgr *data = (struct smu7_hwmgr *)(hwmgr->backend); count = data->vddci_voltage_table.count; if (SMU7_VOLTAGE_CONTROL_BY_GPIO == data->vddci_control) { if (count > SMU_MAX_SMIO_LEVELS) count = SMU_MAX_SMIO_LEVELS; for (level = 0; level < count; ++level) { table->SmioTable1.Pattern[level].Voltage = PP_HOST_TO_SMC_US( data->vddci_voltage_table.entries[level].value * VOLTAGE_SCALE); table->SmioTable1.Pattern[level].Smio = (uint8_t) level; table->Smio[level] |= data->vddci_voltage_table.entries[level].smio_low; } } table->SmioMask1 = data->vddci_voltage_table.mask_low; return 0; } I've attached a patch for kernel 4.19, admittedly the change is trivial but I figured I would try to do things the right way :) Thanks! Rob -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 88891] Errors upon/resuming hibernation.
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=88891 Bug ID: 88891 Summary: Errors upon/resuming hibernation. 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: bogy2004(a)abv.bg I'm facing some errors which currently aren't making any problems (not that I know of at least). Still, I'm concerned what do they mean and should I worry. Here's what I get upon entering hibernation state: http://sprunge.us/MZIb And after resuming, I get this: http://sprunge.us/USQb These are both cut from dmesg. Here's my current hardware for more info: OS: Archlinux x86_64 GPU: ATI Mobility Radeon 5145 (today known as 4570). CPU: i3 M350 Mesa version: 10.4.3 Kernel version: 3.18.4 -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 108606] Raven Ridge: constant lockups since latest pull from Linus
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=108606 Bug ID: 108606 Summary: Raven Ridge: constant lockups since latest pull from Linus 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: samantham(a)posteo.net Created attachment 142287 --> https://bugs.freedesktop.org/attachment.cgi?id=142287&action=edit dmesg log My system was stable on Linus's branch until he pulled in a bunch of DRM changes with this merge commit 53b3b6bbfde6. This pull causes the system to freeze just by using the desktop. Oct 30 15:31:11 kernel: [drm:gfx_v9_0_priv_reg_irq [amdgpu]] *ERROR* Illegal register access in command stream Oct 30 15:31:11 kernel: [drm] GPU recovery disabled. Oct 30 15:31:22 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=61066, emitted seq=61068 Oct 30 15:31:22 kernel: [drm] GPU recovery disabled. Full dmesg attached. -- You are receiving this mail because: You are the assignee for the bug.

1 19

[Bug 108605] R9 380 fan speed is either 100% or very low, during moderate usage gets too loud
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=108605 Bug ID: 108605 Summary: R9 380 fan speed is either 100% or very low, during moderate usage gets too loud 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: christos.kotsaris(a)gmail.com Created attachment 142283 --> https://bugs.freedesktop.org/attachment.cgi?id=142283&action=edit Just a few logs from my pc as per AMD reporting bugs instructions I noticed that when i am playing a video game, the gpu fan seems to be quiet for around 10-20 seconds, then gets too loud for around 3-4s, then back to idle, and this repeats until i quit the game. Upon examination i found out that for some reason the automated dpm sets the fan too low until temperature rises too much (around 100C), then it sets the fan speed to 100% (around 3500RPM), it drops rapidly, and the cycle goes on and on like this. I tried setting the fan speed manually through: echo "1" > /sys/class/drm/card0/device/hwmon/hwmon2/pwm1_enable and echo "X" > /sys/class/drm/card0/device/hwmon/hwmon2/pwm1 and found out that for my card the only values that seem to work are: higher than 199 (sets the fan speed to max) and lower than 196 (sets the fan speed to around 150-190RPM, the lowest my fan will go) I think this is a bug, i don't have a Windows partition anymore but i don't remember ever having this issue on Windows. My GPU is a Sapphire R9 380 ITX Compact 2GB. I am using 4.18.16 kernel and 18.2.3 MESA on Archlinux. -- You are receiving this mail because: You are the assignee for the bug.

1 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel November 2018