dri-devel January 2019

dri-devel@lists.freedesktop.org

279 participants
2022 discussions

[Bug 108934] [Dualscreen] "No signal" issues when booting with DVI and HDMI screens both plugged in
by bugzilla-daemon＠freedesktop.org 20 Nov '19

20 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=108934 Bug ID: 108934 Summary: [Dualscreen] "No signal" issues when booting with DVI and HDMI screens both plugged in 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 … [View More]

1 3

[Bug 107465] Weird resolution
by bugzilla-daemon＠freedesktop.org 20 Nov '19

20 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=107465 Bug ID: 107465 Summary: Weird resolution 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: germano.massullo(a)gmail.com Videocard: RX480 OS: Fedora 28 KDE Kernel 4.17.9-200.fc28.x86_64 … [View More]

1 7

[Bug 107456] WARNING: CPU: 11 PID: 1137 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_mst_types.c:88 dm_dp_aux_transfer+0xa5/0xc0 [amdgpu]
by bugzilla-daemon＠freedesktop.org 20 Nov '19

20 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=107456 Bug ID: 107456 Summary: WARNING: CPU: 11 PID: 1137 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu _dm_mst_types.c:88 dm_dp_aux_transfer+0xa5/0xc0 [amdgpu] Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: … [View More]

1 2

[Bug 107278] Raven: pci_pm_resume takes over 1 second
by bugzilla-daemon＠freedesktop.org 20 Nov '19

20 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=107278 Bug ID: 107278 Summary: Raven: pci_pm_resume takes over 1 second 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: pmenzel+bugs.freedesktop(a)molgen.mpg.de Created attachment 140700 --&… [View More]gt; https://bugs.freedesktop.org/attachment.cgi?id=140700&action=edit Linux 4.18-rc5+ messages Profiling the suspend and resume time [1] on a MSI B350M MORTAR (MS-7A37) with AMD Ryzen 3 2200G with Radeon Vega Graphics with Linux 4.18-rc5+, `pci_pm_suspend()` takes over one second, which is too long. [ 76.483494] amdgpu 0000:38:00.0: calling pci_pm_resume+0x0/0xa0 @ 1731, parent: 0000:00:08.1 [ 76.483499] pcieport 0000:16:01.0: pci_pm_resume+0x0/0xa0 returned 0 after 14 usecs [ 76.483514] pci 0000:38:00.2: calling pci_pm_resume+0x0/0xa0 @ 1672, parent: 0000:00:08.1 [ 76.483528] reg-dummy reg-dummy: calling platform_pm_resume+0x0/0x40 @ 1653, parent: platform [ 76.483530] pci 0000:38:00.2: pci_pm_resume+0x0/0xa0 returned 0 after 9 usecs [ 76.483540] xhci_hcd 0000:38:00.3: calling pci_pm_resume+0x0/0xa0 @ 1672, parent: 0000:00:08.1 [ 76.483543] reg-dummy reg-dummy: platform_pm_resume+0x0/0x40 returned 0 after 5 usecs [ 76.483667] button PNP0C0C:00: calling acpi_button_resume+0x0/0x40 [button] @ 1653, parent: LNXSYBUS:00 [ 76.483679] button PNP0C0C:00: acpi_button_resume+0x0/0x40 [button] returned 0 after 5 usecs [ 76.483724] xhci_hcd 0000:38:00.3: pci_pm_resume+0x0/0xa0 returned 0 after 173 usecs [ 76.483727] platform PNP0800:00: calling platform_pm_resume+0x0/0x40 @ 1653, parent: 0000:00:14.3 [ 76.483733] xhci_hcd 0000:38:00.4: calling pci_pm_resume+0x0/0xa0 @ 1672, parent: 0000:00:08.1 [ 76.483739] platform PNP0800:00: platform_pm_resume+0x0/0x40 returned 0 after 5 usecs [ 76.483748] platform PNP0C0C:00: calling platform_pm_resume+0x0/0x40 @ 1653, parent: platform [ 76.483759] platform PNP0C0C:00: platform_pm_resume+0x0/0x40 returned 0 after 4 usecs [ 76.483767] platform AMDI0030:00: calling platform_pm_resume+0x0/0x40 @ 1653, parent: platform [ 76.483778] platform AMDI0030:00: platform_pm_resume+0x0/0x40 returned 0 after 4 usecs [ 76.483791] platform PNP0103:00: calling platform_pm_resume+0x0/0x40 @ 1653, parent: platform [ 76.483802] platform PNP0103:00: platform_pm_resume+0x0/0x40 returned 0 after 4 usecs [ 76.483813] button LNXPWRBN:00: calling acpi_button_resume+0x0/0x40 [button] @ 1653, parent: LNXSYSTM:00 [ 76.483825] button LNXPWRBN:00: acpi_button_resume+0x0/0x40 [button] returned 0 after 5 usecs [ 76.483841] system 00:00: calling pnp_bus_resume+0x0/0x90 @ 1653, parent: pnp0 [ 76.483854] system 00:00: pnp_bus_resume+0x0/0x90 returned 0 after 6 usecs [ 76.483862] system 00:01: calling pnp_bus_resume+0x0/0x90 @ 1653, parent: pnp0 [ 76.483875] system 00:01: pnp_bus_resume+0x0/0x90 returned 0 after 6 usecs [ 76.483883] rtc_cmos 00:02: calling pnp_bus_resume+0x0/0x90 @ 1653, parent: pnp0 [ 76.483934] xhci_hcd 0000:38:00.4: pci_pm_resume+0x0/0xa0 returned 0 after 190 usecs [ 76.483943] snd_hda_intel 0000:38:00.6: calling pci_pm_resume+0x0/0xa0 @ 1672, parent: 0000:00:08.1 [ 76.484150] ahci 0000:39:00.0: calling pci_pm_resume+0x0/0xa0 @ 1730, parent: 0000:00:08.2 [ 76.484222] ahci 0000:39:00.0: pci_pm_resume+0x0/0xa0 returned 0 after 66 usecs [ 76.484234] r8169 0000:18:00.0: calling pci_pm_resume+0x0/0xa0 @ 1729, parent: 0000:16:01.0 [ 76.484291] rtc_cmos 00:02: pnp_bus_resume+0x0/0x90 returned 0 after 393 usecs [ 76.484296] system 00:03: calling pnp_bus_resume+0x0/0x90 @ 1653, parent: pnp0 [ 76.484302] system 00:03: pnp_bus_resume+0x0/0x90 returned 0 after 3 usecs [ 76.484307] parport_pc 00:04: calling pnp_bus_resume+0x0/0x90 @ 1653, parent: pnp0 [ 76.485185] [drm] PCIE GART of 1024M enabled (table at 0x000000F400900000). [ 76.485220] [drm] PSP is resuming... [ 76.486099] parport_pc 00:04: activated [ 76.486105] parport_pc 00:04: pnp_bus_resume+0x0/0x90 returned 0 after 1751 usecs [ 76.486111] serial 00:05: calling pnp_bus_resume+0x0/0x90 @ 1653, parent: pnp0 [ 76.487493] serial 00:05: activated [ 76.487975] snd_hda_intel 0000:38:00.6: pci_pm_resume+0x0/0xa0 returned 0 after 3933 usecs [ 76.487995] ata1: calling ata_port_pm_resume+0x0/0x50 [libata] @ 1672, parent: 0000:15:00.1 [ 76.488016] ata1: ata_port_pm_resume+0x0/0x50 [libata] returned 0 after 12 usecs [ 76.488025] ata2: calling ata_port_pm_resume+0x0/0x50 [libata] @ 1672, parent: 0000:15:00.1 [ 76.488043] ata2: ata_port_pm_resume+0x0/0x50 [libata] returned 0 after 10 usecs [ 76.488052] ata3: calling ata_port_pm_resume+0x0/0x50 [libata] @ 1672, parent: 0000:15:00.1 [ 76.488070] ata3: ata_port_pm_resume+0x0/0x50 [libata] returned 0 after 9 usecs [ 76.488079] ata4: calling ata_port_pm_resume+0x0/0x50 [libata] @ 1672, parent: 0000:15:00.1 [ 76.488096] ata4: ata_port_pm_resume+0x0/0x50 [libata] returned 0 after 9 usecs [ 76.488105] ata5: calling ata_port_pm_resume+0x0/0x50 [libata] @ 1672, parent: 0000:15:00.1 [ 76.488122] ata5: ata_port_pm_resume+0x0/0x50 [libata] returned 0 after 9 usecs [ 76.488131] ata6: calling ata_port_pm_resume+0x0/0x50 [libata] @ 1672, parent: 0000:15:00.1 [ 76.488149] ata6: ata_port_pm_resume+0x0/0x50 [libata] returned 0 after 10 usecs [ 76.488158] ata7: calling ata_port_pm_resume+0x0/0x50 [libata] @ 1672, parent: 0000:15:00.1 [ 76.488175] ata7: ata_port_pm_resume+0x0/0x50 [libata] returned 0 after 9 usecs [ 76.488184] ata8: calling ata_port_pm_resume+0x0/0x50 [libata] @ 1672, parent: 0000:15:00.1 [ 76.488201] ata8: ata_port_pm_resume+0x0/0x50 [libata] returned 0 after 9 usecs [ 76.488212] scsi host0: calling scsi_bus_resume+0x0/0x20 [scsi_mod] @ 1672, parent: ata1 [ 76.488226] scsi host0: scsi_bus_resume+0x0/0x20 [scsi_mod] returned 0 after 6 usecs [ 76.488236] scsi host1: calling scsi_bus_resume+0x0/0x20 [scsi_mod] @ 1672, parent: ata2 [ 76.488250] scsi host1: scsi_bus_resume+0x0/0x20 [scsi_mod] returned 0 after 6 usecs [ 76.488260] scsi host2: calling scsi_bus_resume+0x0/0x20 [scsi_mod] @ 1672, parent: ata3 [ 76.488274] scsi host2: scsi_bus_resume+0x0/0x20 [scsi_mod] returned 0 after 6 usecs [ 76.488284] scsi host3: calling scsi_bus_resume+0x0/0x20 [scsi_mod] @ 1672, parent: ata4 [ 76.488297] scsi host3: scsi_bus_resume+0x0/0x20 [scsi_mod] returned 0 after 6 usecs [ 76.488307] scsi host4: calling scsi_bus_resume+0x0/0x20 [scsi_mod] @ 1672, parent: ata5 [ 76.488320] scsi host4: scsi_bus_resume+0x0/0x20 [scsi_mod] returned 0 after 6 usecs [ 76.488330] scsi host5: calling scsi_bus_resume+0x0/0x20 [scsi_mod] @ 1672, parent: ata6 [ 76.488343] scsi host5: scsi_bus_resume+0x0/0x20 [scsi_mod] returned 0 after 6 usecs [ 76.488353] scsi host6: calling scsi_bus_resume+0x0/0x20 [scsi_mod] @ 1672, parent: ata7 [ 76.488366] scsi host6: scsi_bus_resume+0x0/0x20 [scsi_mod] returned 0 after 6 usecs [ 76.488376] scsi host7: calling scsi_bus_resume+0x0/0x20 [scsi_mod] @ 1672, parent: ata8 [ 76.488389] scsi host7: scsi_bus_resume+0x0/0x20 [scsi_mod] returned 0 after 6 usecs [ 76.488400] ata9: calling ata_port_pm_resume+0x0/0x50 [libata] @ 1672, parent: 0000:39:00.0 [ 76.488417] ata9: ata_port_pm_resume+0x0/0x50 [libata] returned 0 after 9 usecs [ 76.488426] scsi host8: calling scsi_bus_resume+0x0/0x20 [scsi_mod] @ 1672, parent: ata9 [ 76.488443] scsi host8: scsi_bus_resume+0x0/0x20 [scsi_mod] returned 0 after 8 usecs [ 76.494515] usb usb3: calling usb_dev_resume+0x0/0x10 [usbcore] @ 1686, parent: 0000:38:00.3 [ 76.494902] usb usb3: usb_dev_resume+0x0/0x10 [usbcore] returned 0 after 366 usecs [ 76.494961] usb usb4: calling usb_dev_resume+0x0/0x10 [usbcore] @ 1725, parent: 0000:38:00.3 [ 76.495281] usb usb4: usb_dev_resume+0x0/0x10 [usbcore] returned 0 after 294 usecs [ 76.495320] usb usb5: calling usb_dev_resume+0x0/0x10 [usbcore] @ 1725, parent: 0000:38:00.4 [ 76.505392] usb usb6: calling usb_dev_resume+0x0/0x10 [usbcore] @ 1698, parent: 0000:38:00.4 [ 76.505518] usb usb6: usb_dev_resume+0x0/0x10 [usbcore] returned 0 after 105 usecs [ 76.505552] scsi target8:0:0: calling scsi_bus_resume+0x0/0x20 [scsi_mod] @ 1721, parent: host8 [ 76.505577] scsi target8:0:0: scsi_bus_resume+0x0/0x20 [scsi_mod] returned 0 after 10 usecs [ 76.505583] snd_hda_codec_realtek hdaudioC1D0: calling pm_runtime_force_resume+0x0/0xc0 @ 181, parent: 0000:38:00.6 [ 76.505598] snd_hda_codec_realtek hdaudioC1D0: pm_runtime_force_resume+0x0/0xc0 returned 0 after 7 usecs [ 76.505612] sd 8:0:0:0: calling scsi_bus_resume+0x0/0x20 [scsi_mod] @ 1696, parent: target8:0:0 [ 76.505644] sd 8:0:0:0: scsi_bus_resume+0x0/0x20 [scsi_mod] returned 0 after 14 usecs [ 76.505645] sd 8:0:0:0: [sda] Starting disk [ 76.521990] r8169 0000:18:00.0: pci_pm_resume+0x0/0xa0 returned 0 after 36861 usecs [ 76.539426] xhci_hcd 0000:15:00.0: pci_pm_resume+0x0/0xa0 returned 0 after 54692 usecs [ 76.539456] usb usb1: calling usb_dev_resume+0x0/0x10 [usbcore] @ 1672, parent: 0000:15:00.0 [ 76.539484] usb usb2: calling usb_dev_resume+0x0/0x10 [usbcore] @ 1712, parent: 0000:15:00.0 [ 76.541850] r8169 0000:18:00.0 enp24s0: link down [ 76.553242] usb usb5: usb_dev_resume+0x0/0x10 [usbcore] returned 0 after 56543 usecs [ 76.553269] usb 5-1: calling usb_dev_resume+0x0/0x10 [usbcore] @ 1722, parent: usb5 [ 76.555075] usb 5-1: usb_dev_resume+0x0/0x10 [usbcore] returned 0 after 1755 usecs [ 76.646442] usb usb2: usb_dev_resume+0x0/0x10 [usbcore] returned 0 after 104432 usecs [ 76.753730] usb usb1: usb_dev_resume+0x0/0x10 [usbcore] returned 0 after 209240 usecs [ 76.754226] usb 1-10: calling usb_dev_resume+0x0/0x10 [usbcore] @ 1723, parent: usb1 [ 76.796293] ata6: SATA link down (SStatus 0 SControl 300) [ 76.796728] ata1: SATA link down (SStatus 0 SControl 300) [ 76.797665] ata5: SATA link down (SStatus 0 SControl 300) [ 76.808565] ata2: SATA link down (SStatus 0 SControl 300) [ 76.957819] ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 76.958976] ata9.00: supports DRM functions and may not be fully accessible [ 76.959799] ata9.00: supports DRM functions and may not be fully accessible [ 76.960392] ata9.00: configured for UDMA/133 [ 77.021998] usb 1-10: reset low-speed USB device number 2 using xhci_hcd [ 77.194278] amdgpu: [powerplay] dpm has been enabled [ 77.465520] usb 1-10: usb_dev_resume+0x0/0x10 [usbcore] returned 0 after 694599 usecs [ 77.669669] [drm] VCN decode and encode initialized successfully. [ 77.669702] amdgpu 0000:38:00.0: ring 0(gfx) uses VM inv eng 4 on hub 0 [ 77.669709] amdgpu 0000:38:00.0: ring 1(comp_1.0.0) uses VM inv eng 5 on hub 0 [ 77.669710] amdgpu 0000:38:00.0: ring 2(comp_1.1.0) uses VM inv eng 6 on hub 0 [ 77.669712] amdgpu 0000:38:00.0: ring 3(comp_1.2.0) uses VM inv eng 7 on hub 0 [ 77.669714] amdgpu 0000:38:00.0: ring 4(comp_1.3.0) uses VM inv eng 8 on hub 0 [ 77.669715] amdgpu 0000:38:00.0: ring 5(comp_1.0.1) uses VM inv eng 9 on hub 0 [ 77.669717] amdgpu 0000:38:00.0: ring 6(comp_1.1.1) uses VM inv eng 10 on hub 0 [ 77.669719] amdgpu 0000:38:00.0: ring 7(comp_1.2.1) uses VM inv eng 11 on hub 0 [ 77.669721] amdgpu 0000:38:00.0: ring 8(comp_1.3.1) uses VM inv eng 12 on hub 0 [ 77.669722] amdgpu 0000:38:00.0: ring 9(kiq_2.1.0) uses VM inv eng 13 on hub 0 [ 77.669724] amdgpu 0000:38:00.0: ring 10(sdma0) uses VM inv eng 4 on hub 1 [ 77.669726] amdgpu 0000:38:00.0: ring 11(vcn_dec) uses VM inv eng 5 on hub 1 [ 77.669727] amdgpu 0000:38:00.0: ring 12(vcn_enc0) uses VM inv eng 6 on hub 1 [ 77.669729] amdgpu 0000:38:00.0: ring 13(vcn_enc1) uses VM inv eng 7 on hub 1 [ 77.673927] amdgpu 0000:38:00.0: pci_pm_resume+0x0/0xa0 returned 0 after 1162525 usecs ``` According to the trace the time is spent in `amdgpu_device_ip_resume_phase2()`. It’d be great to reduce the time. Best would a few milliseconds. [1]: https://github.com/01org/pm-graph/ -- You are receiving this mail because: You are the assignee for the bug. [View Less]

1 7

[Bug 107376] Raven: `flush_delayed_work()` takes 500 ms
by bugzilla-daemon＠freedesktop.org 20 Nov '19

20 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=107376 Bug ID: 107376 Summary: Raven: `flush_delayed_work()` takes 500 ms 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: pmenzel+bugs.freedesktop(a)molgen.mpg.de Created attachment 140811 --… [View More]

1 2

[Bug 105433] Unreliable Modesetting on Tonga with two DVI Screens
by bugzilla-daemon＠freedesktop.org 20 Nov '19

20 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=105433 Bug ID: 105433 Summary: Unreliable Modesetting on Tonga with two DVI Screens Product: DRI Version: DRI git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: freedesktop-bugs(a)digital-trauma.de Two … [View More]

1 12

[Bug 109366] NULL pointer at pcie_capability_read_dword with Radeon SI vfio passthrough
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=109366 Bug ID: 109366 Summary: NULL pointer at pcie_capability_read_dword with Radeon SI vfio passthrough 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:… [View More]

1 6

[Bug 108956] After 11 seconds, 3 second video freeze
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=108956 Bug ID: 108956 Summary: After 11 seconds, 3 second video freeze Product: DRI Version: XOrg git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: lawsa(a)indiana.edu I run XFCE4 on arch linux on a … [View More]Dell Precision 7710. lspci reports: 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 07) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 07) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 07) 00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31) 00:14.2 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Thermal Subsystem (rev 31) 00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 (rev 31) 00:17.0 RAID bus controller: Intel Corporation SATA Controller [RAID mode] (rev 31) 00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #2 (rev f1) 00:1c.2 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #3 (rev f1) 00:1c.4 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #5 (rev f1) 00:1f.0 ISA bridge: Intel Corporation CM236 Chipset LPC/eSPI Controller (rev 31) 00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller (rev 31) 00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller (rev 31) 00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus (rev 31) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-LM (rev 31) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Venus XTX [Radeon HD 8890M / R9 M275X/M375X] (rev 83) 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] 02:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a) 03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) Here is a snatch of journalctl --follow; when running XFCE. Dec 05 14:23:15 zwingli kernel: [drm] PCIE gen 3 link speeds already enabled Dec 05 14:23:15 zwingli kernel: [drm] PCIE GART of 2048M enabled (table at 0x00000000001D6000). Dec 05 14:23:15 zwingli kernel: radeon 0000:01:00.0: WB enabled Dec 05 14:23:15 zwingli kernel: radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0x0000000030f06385 Dec 05 14:23:15 zwingli kernel: radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and cpu addr 0x0000000095c9ebc9 Dec 05 14:23:15 zwingli kernel: radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and cpu addr 0x00000000bde04402 Dec 05 14:23:15 zwingli kernel: radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0x00000000283a3851 Dec 05 14:23:15 zwingli kernel: radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and cpu addr 0x0000000095834e0e Dec 05 14:23:15 zwingli kernel: radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0x00000000f51f7fd6 Dec 05 14:23:15 zwingli kernel: radeon 0000:01:00.0: fence driver on ring 6 use gpu addr 0x0000000080000c18 and cpu addr 0x000000001fdca925 Dec 05 14:23:15 zwingli kernel: radeon 0000:01:00.0: fence driver on ring 7 use gpu addr 0x0000000080000c1c and cpu addr 0x00000000a6e7009c Dec 05 14:23:16 zwingli kernel: [drm] ring test on 0 succeeded in 1 usecs Dec 05 14:23:16 zwingli kernel: [drm] ring test on 1 succeeded in 1 usecs Dec 05 14:23:16 zwingli kernel: [drm] ring test on 2 succeeded in 1 usecs Dec 05 14:23:16 zwingli kernel: [drm] ring test on 3 succeeded in 9 usecs Dec 05 14:23:16 zwingli kernel: [drm] ring test on 4 succeeded in 3 usecs Dec 05 14:23:16 zwingli kernel: [drm] ring test on 5 succeeded in 2 usecs Dec 05 14:23:16 zwingli kernel: [drm] UVD initialized successfully. Dec 05 14:23:16 zwingli kernel: [drm] ring test on 6 succeeded in 13 usecs Dec 05 14:23:16 zwingli kernel: [drm] ring test on 7 succeeded in 5 usecs Dec 05 14:23:16 zwingli kernel: [drm] VCE initialized successfully. Dec 05 14:23:16 zwingli kernel: [drm] ib test on ring 0 succeeded in 0 usecs Dec 05 14:23:16 zwingli kernel: [drm] ib test on ring 1 succeeded in 0 usecs Dec 05 14:23:16 zwingli kernel: [drm] ib test on ring 2 succeeded in 0 usecs Dec 05 14:23:16 zwingli kernel: [drm] ib test on ring 3 succeeded in 0 usecs Dec 05 14:23:16 zwingli kernel: [drm] ib test on ring 4 succeeded in 0 usecs Dec 05 14:23:17 zwingli kernel: [drm] ib test on ring 5 succeeded Dec 05 14:23:17 zwingli kernel: [drm] ib test on ring 6 succeeded Dec 05 14:23:18 zwingli kernel: [drm] ib test on ring 7 succeeded Dec 05 14:23:29 zwingli kernel: [drm] PCIE gen 3 link speeds already enabled Dec 05 14:23:29 zwingli kernel: [drm] PCIE GART of 2048M enabled (table at 0x00000000001D6000). Dec 05 14:23:29 zwingli kernel: radeon 0000:01:00.0: WB enabled Dec 05 14:23:29 zwingli kernel: radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0x0000000030f06385 Dec 05 14:23:29 zwingli kernel: radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and cpu addr 0x0000000095c9ebc9 Dec 05 14:23:29 zwingli kernel: radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and cpu addr 0x00000000bde04402 Dec 05 14:23:29 zwingli kernel: radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0x00000000283a3851 Dec 05 14:23:29 zwingli kernel: radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and cpu addr 0x0000000095834e0e Dec 05 14:23:29 zwingli kernel: radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0x00000000f51f7fd6 Dec 05 14:23:29 zwingli kernel: radeon 0000:01:00.0: fence driver on ring 6 use gpu addr 0x0000000080000c18 and cpu addr 0x000000001fdca925 Dec 05 14:23:29 zwingli kernel: radeon 0000:01:00.0: fence driver on ring 7 use gpu addr 0x0000000080000c1c and cpu addr 0x00000000a6e7009c Dec 05 14:23:29 zwingli kernel: [drm] ring test on 0 succeeded in 1 usecs Dec 05 14:23:29 zwingli kernel: [drm] ring test on 1 succeeded in 1 usecs Dec 05 14:23:29 zwingli kernel: [drm] ring test on 2 succeeded in 1 usecs Dec 05 14:23:29 zwingli kernel: [drm] ring test on 3 succeeded in 9 usecs Dec 05 14:23:29 zwingli kernel: [drm] ring test on 4 succeeded in 3 usecs Dec 05 14:23:29 zwingli kernel: [drm] ring test on 5 succeeded in 2 usecs Dec 05 14:23:29 zwingli kernel: [drm] UVD initialized successfully. Dec 05 14:23:29 zwingli kernel: [drm] ring test on 6 succeeded in 14 usecs Dec 05 14:23:29 zwingli kernel: [drm] ring test on 7 succeeded in 5 usecs Dec 05 14:23:29 zwingli kernel: [drm] VCE initialized successfully. Dec 05 14:23:29 zwingli kernel: [drm] ib test on ring 0 succeeded in 0 usecs Dec 05 14:23:29 zwingli kernel: [drm] ib test on ring 1 succeeded in 0 usecs Dec 05 14:23:29 zwingli kernel: [drm] ib test on ring 2 succeeded in 0 usecs Dec 05 14:23:29 zwingli kernel: [drm] ib test on ring 3 succeeded in 0 usecs Dec 05 14:23:29 zwingli kernel: [drm] ib test on ring 4 succeeded in 0 usecs Dec 05 14:23:30 zwingli kernel: [drm] ib test on ring 5 succeeded Dec 05 14:23:31 zwingli kernel: [drm] ib test on ring 6 succeeded Dec 05 14:23:31 zwingli kernel: [drm] ib test on ring 7 succeeded At 14:23:15 and 14:23:29, the video side of the machine experiences a video freeze. The mouse continues to be rendered, but everything else freezes. Everything catches up when the freeze is over, so the effect of Alt+Tab and typing is registered after the freeze. I just booted adding the following kernel parameters: radeon.si_support=0 amdgpu.si_support=1 and the problem does not manifest. Please let me know what other information would be helpful. Thank you! -- You are receiving this mail because: You are the assignee for the bug. [View Less]

1 2

[Bug 108361] Radeon/Xorg crash during boot with Radeon R5 M230
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=108361 Bug ID: 108361 Summary: Radeon/Xorg crash during boot with Radeon R5 M230 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: jian-hong(a)endlessm.com Created … [View More]attachment 142025 --> https://bugs.freedesktop.org/attachment.cgi?id=142025&action=edit journal log when radeon/Xorg crash This is found on Acer Veriton Z4660G desktop equipped with Intel(R) Core(TM) i7-8700 CPU and an AMD/ATI Jet PRO Radeon R5 M230 graphic card. 01:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Jet PRO [Radeon R5 M230] [1002:6665] (rev 83) Subsystem: PC Partner Limited / Sapphire Technology Jet PRO [Radeon R5 M230] [174b:e332] Flags: bus master, fast devsel, latency 0, IRQ 127 Memory at 90000000 (64-bit, prefetchable) [size=256M] Memory at 7c300000 (64-bit, non-prefetchable) [size=256K] I/O ports at 4000 [size=256] Expansion ROM at 7c340000 [disabled] [size=128K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [58] Express Legacy Endpoint, MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [150] Advanced Error Reporting Capabilities: [200] #15 Capabilities: [270] #19 Kernel driver in use: radeon Kernel modules: radeon, amdgpu I have tested it with Linux kernel 4.19-rc7. System (radeon module) sometimes hits the error during boot, then Xorg crashes. Oct 12 17:28:52 endless kernel: [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting Oct 12 17:28:52 endless kernel: [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing 67C0 (len 254, WS 0, PS 4) @ 0x67CE Oct 12 17:28:52 endless kernel: [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing 612C (len 78, WS 12, PS 8) @ 0x6165 Oct 12 17:28:52 endless kernel: iwlwifi 0000:00:14.3: HCMD_ACTIVE already clear for command SCAN_REQ_UMAC Oct 12 17:28:52 endless kernel: [drm] PCIE gen 3 link speeds already enabled Oct 12 17:28:54 endless kernel: radeon 0000:01:00.0: Wait for MC idle timedout ! Oct 12 17:28:54 endless kernel: radeon 0000:01:00.0: Wait for MC idle timedout ! Oct 12 17:28:54 endless eos-metrics-ins[606]: Failed to start GeoClue2 client: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying. Oct 12 17:28:54 endless kernel: [drm] PCIE GART of 2048M enabled (table at 0x0000000000040000). Oct 12 17:28:54 endless kernel: radeon 0000:01:00.0: WB enabled Oct 12 17:28:54 endless kernel: radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0x000000007d0c53c5 Oct 12 17:28:54 endless kernel: radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and cpu addr 0x000000006e1c12be Oct 12 17:28:54 endless kernel: radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and cpu addr 0x00000000a603d5e9 Oct 12 17:28:54 endless kernel: radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0x0000000039a9e421 Oct 12 17:28:54 endless kernel: radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and cpu addr 0x00000000ba920de2 Oct 12 17:28:55 endless kernel: [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x850C)=0xCAFEDEAD) Oct 12 17:28:55 endless kernel: [drm:si_resume [radeon]] *ERROR* si startup failed on resume I also tried to disable radeon's runtime power management by passing "radeon.runpm=0" to boot command. It makes system working stable on this model. -- You are receiving this mail because: You are the assignee for the bug. [View Less]

1 2

[Bug 107545] radeon - ring 0 stalled - GPU lockup - SI
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=107545 Bug ID: 107545 Summary: radeon - ring 0 stalled - GPU lockup - SI 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: julien.isorce(a)gmail.com * Steps to reproduce: for i in {0..300}; do (… [View More]

1 20

← Newer
1
2
3
4
5
6
7
8
9
...
203
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel January 2019