Re: renesas 1912:0014 failures

[Michal Pecio <michal.pecio@gmail.com>]

On Wed, 13 May 2026 00:34:02 +0200, Anders Thomson wrote:
> Here we go:
> [  469.798260] PM: suspend entry (deep)
> [  470.046476] Filesystems sync: 0.248 seconds
> [  470.048616] Freezing user space processes
> [  470.049453] Freezing user space processes completed (elapsed 0.000 seconds)
> [  470.049499] OOM killer disabled.
> [  470.049536] Freezing remaining freezable tasks
> [  470.050449] Freezing remaining freezable tasks completed (elapsed
> 0.000 seconds)
> [  470.050516] printk: Suspending console(s) (use no_console_suspend to debug)
> [  470.051839] xhci-pci-renesas 0000:03:00.0: Get port status 9-1
> read: 0x2a0, return 0x100
> [  470.051866] xhci-pci-renesas 0000:03:00.0: Get port status 9-2
> read: 0x2a0, return 0x100
> [  470.051876] xhci-pci-renesas 0000:03:00.0: Get port status 9-3
> read: 0x2a0, return 0x100
> [  470.051886] xhci-pci-renesas 0000:03:00.0: Get port status 9-4
> read: 0x2a0, return 0x100
> [  470.077248] xhci-pci-renesas 0000:03:00.0: Get port status 10-1
> read: 0x2a0, return 0x2a0
> [  470.077264] xhci-pci-renesas 0000:03:00.0: Get port status 10-2
> read: 0x2a0, return 0x2a0
> [  470.077276] xhci-pci-renesas 0000:03:00.0: Get port status 10-3
> read: 0x2a0, return 0x2a0
> [  470.077292] xhci-pci-renesas 0000:03:00.0: Get port status 10-4
> read: 0x2a0, return 0x2a0
> [  470.077501] sd 7:0:0:0: [sdf] Synchronizing SCSI cache
> [  470.077635] xhci-pci-renesas 0000:03:00.0: config port 10-1 wake
> bits, portsc: 0x2a0, write: 0x202a0
> [  470.077818] xhci-pci-renesas 0000:03:00.0: config port 10-2 wake
> bits, portsc: 0x2a0, write: 0x202a0
> [  470.077825] xhci-pci-renesas 0000:03:00.0: config port 10-3 wake
> bits, portsc: 0x2a0, write: 0x202a0
> [  470.077833] xhci-pci-renesas 0000:03:00.0: config port 10-4 wake
> bits, portsc: 0x2a0, write: 0x202a0
> [  470.077842] xhci-pci-renesas 0000:03:00.0: config port 9-1 wake
> bits, portsc: 0x2a0, write: 0x202a0
> [  470.077847] xhci-pci-renesas 0000:03:00.0: config port 9-2 wake
> bits, portsc: 0x2a0, write: 0x202a0
> [  470.077852] xhci-pci-renesas 0000:03:00.0: config port 9-3 wake
> bits, portsc: 0x2a0, write: 0x202a0
> [  470.077856] xhci-pci-renesas 0000:03:00.0: config port 9-4 wake
> bits, portsc: 0x2a0, write: 0x202a0
> [  470.077859] xhci-pci-renesas 0000:03:00.0: xhci_suspend: stopping
> usb9 port polling.
> [  470.078452] r8169 0000:02:00.0 enp2s0: Link is Down
> [  470.083228] xhci-pci-renesas 0000:03:00.0: Setting command ring
> address to 0x2476001

This looks like normal suspend, no indication that the chip failed
to halt or otherwise appeared nonresponsive.

> [  470.085447] sd 0:0:0:0: [sda] Synchronizing SCSI cache
> [  470.085685] ata1.00: Entering standby power mode
> [  470.089467] sd 3:0:0:0: [sdd] Synchronizing SCSI cache
> [  470.089471] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
> [  470.089498] sd 2:0:0:0: [sdc] Synchronizing SCSI cache
> [  470.089976] ata3.00: Entering standby power mode
> [  471.185801] ata4.00: Entering standby power mode
> [  471.923516] ACPI: PM: Preparing to enter system sleep state S3
> [  471.923767] ACPI: PM: Saving platform NVS memory
> [  471.924004] Disabling non-boot CPUs ...
> [  471.925486] smpboot: CPU 3 is now offline
> [  471.927750] smpboot: CPU 2 is now offline
> [  471.930012] smpboot: CPU 1 is now offline
> [  471.937302] ACPI: PM: Low-level resume complete
> [  471.937330] ACPI: PM: Restoring platform NVS memory
> [  471.937770] Enabling non-boot CPUs ...
> [  471.937814] smpboot: Booting Node 0 Processor 1 APIC 0x1
> [  471.948497] CPU1 is up
> [  471.948526] smpboot: Booting Node 0 Processor 2 APIC 0x2
> [  471.958206] CPU2 is up
> [  471.958233] smpboot: Booting Node 0 Processor 3 APIC 0x3
> [  471.967051] CPU3 is up
> [  471.970459] ACPI: PM: Waking up from system sleep state S3
> [  471.973104] usb usb2: root hub lost power or was reset
> [  471.973129] usb usb4: root hub lost power or was reset
> [  471.973229] usb usb5: root hub lost power or was reset
> [  471.973248] usb usb6: root hub lost power or was reset
> [  471.973325] usb usb7: root hub lost power or was reset
> [  471.973345] usb usb8: root hub lost power or was reset
> [  471.973735] hpet: Lost 1253 RTC interrupts
> [  471.973898] usb usb9: root hub lost power or was reset
> [  471.973901] usb usb10: root hub lost power or was reset
> [  471.973904] xhci-pci-renesas 0000:03:00.0: Stop HCD
> [  471.973906] xhci-pci-renesas 0000:03:00.0: // Halt the HC
> [  471.973917] xhci-pci-renesas 0000:03:00.0: // Reset the HC
> [  500.363392] hpet: Lost 1815 RTC interrupts
> [  500.363631] xhci-pci-renesas 0000:03:00.0: PCI post-resume error -110!
> [  500.363635] xhci-pci-renesas 0000:03:00.0: HC died; cleaning up
> [  500.363715] xhci-pci-renesas 0000:03:00.0: PM: dpm_run_callback():
> pci_pm_resume returns -110
> [  500.363725] xhci-pci-renesas 0000:03:00.0: PM: failed to resume
> async: error -110

I see you still have the quirk, but it doesn't matter, the chip is
stuck and doesn't work either way.

I don't know what causes this, looks like a low level problem - in HW
or possibly the PCI layer. Maybe Mathias will have other ideas, but
I'm not sure that USB subsystem can do anything about it.

Regards,
Michal