* renesas 1912:0014 failures
@ 2026-05-06 12:58 Anders Thomson
2026-05-12 10:27 ` Michal Pecio
0 siblings, 1 reply; 10+ messages in thread
From: Anders Thomson @ 2026-05-06 12:58 UTC (permalink / raw)
To: linux-usb; +Cc: Mathias Nyman
Hi,
I've received a Renesas pcie usb3 card which fails to suspend (to ram)
correctly.
Regular boots appear to be working fine, but upon resuming from
suspend, I get this log:
[ 461.824899] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
[ 461.824902] rcu: 3-...0: (3 ticks this GP)
idle=0884/1/0x4000000000000000 softirq=2388/2389 fqs=5249
[ 461.824907] rcu: (detected by 1, t=21002 jiffies, g=5201, q=24 ncpus=4)
[ 461.824910] Sending NMI from CPU 1 to CPUs 3:
[ 461.824917] NMI backtrace for cpu 3
[ 461.824922] CPU: 3 UID: 0 PID: 513 Comm: kworker/u18:6 Tainted: G S
7.0.3 #2 PREEMPT(full)
[ 461.824926] Tainted: [S]=CPU_OUT_OF_SPEC
[ 461.824927] Hardware name: HP-Pavilion FJ422AA-UUW
a6551.sc/Benicia, BIOS 5.32 10/23/2008
[ 461.824929] Workqueue: async async_run_entry_fn
[ 461.824936] RIP: 0010:xhci_resume+0x3fe/0x5a0
[ 461.824941] Code: 04 f6 c4 08 74 5a 41 bd 7b 6f 98 00 eb 21 49 83
ed 01 0f 84 a0 01 00 00 bf c7 10 00 00 e8 1a fa 3e 00 f3 90 48 8b 04
24 8b 00 <f6> c4 08 74 31 83 f8 ff 75 da b8 ed ff ff ff 48 8b 0b 89 c2
48 c7
[ 461.824943] RSP: 0000:ffff9ed3003ebd68 EFLAGS: 00000082
[ 461.824945] RAX: 0000000000000801 RBX: ffff9112c241a250 RCX: ffff9ed30043e024
[ 461.824947] RDX: 0000000000000987 RSI: 0000000000000003 RDI: 0000000bf69fa402
[ 461.824948] RBP: ffff9112c241a000 R08: 0000000000000960 R09: 0000000000000003
[ 461.824950] R10: 0000000000000003 R11: ffffffff95258f20 R12: 0000000000000000
[ 461.824951] R13: 0000000000268925 R14: ffff9112c241a290 R15: 0000000000000000
[ 461.824952] FS: 0000000000000000(0000) GS:ffff9113e6604000(0000)
knlGS:0000000000000000
[ 461.824954] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 461.824956] CR2: 0000000000000000 CR3: 000000000faeb000 CR4: 00000000000006f0
[ 461.824957] Call Trace:
[ 461.824960] <TASK>
[ 461.824963] resume_common+0x89/0xd0
[ 461.824968] ? __pfx_pci_pm_resume+0x10/0x10
[ 461.824973] dpm_run_callback+0x3d/0x160
[ 461.824977] ? dpm_wait_for_superior+0xf7/0x150
[ 461.824981] device_resume+0x158/0x250
[ 461.824984] async_resume+0x14/0x20
[ 461.824987] async_run_entry_fn+0x21/0xa0
[ 461.824991] process_one_work+0x163/0x370
[ 461.824994] worker_thread+0x18f/0x300
[ 461.824997] ? __pfx_worker_thread+0x10/0x10
[ 461.824999] kthread+0xda/0x110
[ 461.825003] ? __pfx_kthread+0x10/0x10
[ 461.825006] ret_from_fork+0x1af/0x2b0
[ 461.825009] ? __pfx_kthread+0x10/0x10
[ 461.825012] ret_from_fork_asm+0x1a/0x30
[ 461.825017] </TASK>
[ 462.302911] rcu: INFO: rcu_preempt detected expedited stalls on
CPUs/tasks: { 3-...D } 21425 jiffies s: 365 root: 0x8/.
[ 462.302917] rcu: blocking rcu_node structures (internal RCU debug):
[ 462.302919] Sending NMI from CPU 1 to CPUs 3:
[ 462.302922] NMI backtrace for cpu 3
[ 462.302925] CPU: 3 UID: 0 PID: 513 Comm: kworker/u18:6 Tainted: G S
7.0.3 #2 PREEMPT(full)
[ 462.302928] Tainted: [S]=CPU_OUT_OF_SPEC
[ 462.302929] Hardware name: HP-Pavilion FJ422AA-UUW
a6551.sc/Benicia, BIOS 5.32 10/23/2008
[ 462.302930] Workqueue: async async_run_entry_fn
[ 462.302933] RIP: 0010:xhci_resume+0x3fe/0x5a0
[ 462.302936] Code: 04 f6 c4 08 74 5a 41 bd 7b 6f 98 00 eb 21 49 83
ed 01 0f 84 a0 01 00 00 bf c7 10 00 00 e8 1a fa 3e 00 f3 90 48 8b 04
24 8b 00 <f6> c4 08 74 31 83 f8 ff 75 da b8 ed ff ff ff 48 8b 0b 89 c2
48 c7
[ 462.302938] RSP: 0000:ffff9ed3003ebd68 EFLAGS: 00000082
[ 462.302940] RAX: 0000000000000801 RBX: ffff9112c241a250 RCX: ffff9ed30043e024
[ 462.302941] RDX: 0000000000000987 RSI: 0000000000000003 RDI: 0000000c3b0074cb
[ 462.302943] RBP: ffff9112c241a000 R08: 0000000000000960 R09: 0000000000000003
[ 462.302944] R10: 0000000000000003 R11: ffffffff95258f20 R12: 0000000000000000
[ 462.302945] R13: 000000000023f18b R14: ffff9112c241a290 R15: 0000000000000000
[ 462.302947] FS: 0000000000000000(0000) GS:ffff9113e6604000(0000)
knlGS:0000000000000000
[ 462.302949] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 462.302950] CR2: 0000000000000000 CR3: 000000000faeb000 CR4: 00000000000006f0
[ 462.302951] Call Trace:
[ 462.302952] <TASK>
[ 462.302953] resume_common+0x89/0xd0
[ 462.302957] ? __pfx_pci_pm_resume+0x10/0x10
[ 462.302961] dpm_run_callback+0x3d/0x160
[ 462.302964] ? dpm_wait_for_superior+0xf7/0x150
[ 462.302967] device_resume+0x158/0x250
[ 462.302970] async_resume+0x14/0x20
[ 462.302974] async_run_entry_fn+0x21/0xa0
[ 462.302977] process_one_work+0x163/0x370
[ 462.302980] worker_thread+0x18f/0x300
[ 462.302983] ? __pfx_worker_thread+0x10/0x10
[ 462.302985] kthread+0xda/0x110
[ 462.302988] ? __pfx_kthread+0x10/0x10
[ 462.302991] ret_from_fork+0x1af/0x2b0
[ 462.302993] ? __pfx_kthread+0x10/0x10
[ 462.302997] ret_from_fork_asm+0x1a/0x30
[ 462.303001] </TASK>
[ 468.932307] xhci-pci-renesas 0000:03:00.0: Controller not ready at
resume -110
[ 468.932332] clocksource: Long readout interval, skipping watchdog
check: cs_nsec: 26925372067 wd_nsec: 26925364392
[ 468.932394] xhci-pci-renesas 0000:03:00.0: PCI post-resume error -110!
[ 468.932401] xhci-pci-renesas 0000:03:00.0: HC died; cleaning up
[ 468.932429] xhci-pci-renesas 0000:03:00.0: PM: dpm_run_callback():
pci_pm_resume returns -110
[ 468.932434] xhci-pci-renesas 0000:03:00.0: PM: failed to resume
async: error -110
This is on vanilla 7.0.3. If I add the firmware (renesas_usb_fw.mem,
sha256=177560c224c73...) it fails to load on boot and I get a massive
stall in bootup:
[ 0.374764] pci 0000:00:1c.1: enabling device (0106 -> 0107)
[ 6.295099] pci 0000:03:00.0: xHCI HW not ready after 5 sec (HC
bug?) status = 0x801
[ 6.295198] pci 0000:03:00.0: quirk_usb_early_handoff+0x0/0x700
took 5781678 usecs
followed by:
[ 8.238859] sr 5:0:0:0: Attached scsi generic sg4 type 5
[ 66.649786] xhci-pci-renesas 0000:03:00.0: failed to load firmware
renesas_usb_fw.mem, fallback to ROM
[ 66.649936] xhci-pci-renesas 0000:03:00.0: xHCI Host Controller
[ 66.650039] xhci-pci-renesas 0000:03:00.0: new USB bus registered,
assigned bus number 9
[ 95.065505] xhci-pci-renesas 0000:03:00.0: can't setup: -110
[ 95.065555] xhci-pci-renesas 0000:03:00.0: USB bus 9 deregistered
[ 95.065680] xhci-pci-renesas 0000:03:00.0: init 0000:03:00.0 fail, -110
[ 95.065739] xhci-pci-renesas 0000:03:00.0: probe with driver
xhci-pci-renesas failed with error -110
After which the usb root devices are not present (according to lsusb).
Any idea how this can be fixed? I also tried the
https://github.com/markusj/upd72020x-load.git loader, but that didn't
change the situation.
Thanks in advance.
Anders
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: renesas 1912:0014 failures
2026-05-06 12:58 renesas 1912:0014 failures Anders Thomson
@ 2026-05-12 10:27 ` Michal Pecio
2026-05-12 14:40 ` Anders Thomson
0 siblings, 1 reply; 10+ messages in thread
From: Michal Pecio @ 2026-05-12 10:27 UTC (permalink / raw)
To: Anders Thomson; +Cc: linux-usb, Mathias Nyman
On Wed, 6 May 2026 14:58:44 +0200, Anders Thomson wrote:
> Hi,
>
> I've received a Renesas pcie usb3 card which fails to suspend (to ram)
> correctly.
>
> Regular boots appear to be working fine, but upon resuming from
> suspend, I get this log:
>
> [ 461.824899] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
> [ 461.824902] rcu: 3-...0: (3 ticks this GP)
> idle=0884/1/0x4000000000000000 softirq=2388/2389 fqs=5249
> [ 461.824907] rcu: (detected by 1, t=21002 jiffies, g=5201, q=24 ncpus=4)
> [ 461.824910] Sending NMI from CPU 1 to CPUs 3:
> [ 461.824917] NMI backtrace for cpu 3
> [ 461.824922] CPU: 3 UID: 0 PID: 513 Comm: kworker/u18:6 Tainted: G S
> 7.0.3 #2 PREEMPT(full)
> [ 461.824926] Tainted: [S]=CPU_OUT_OF_SPEC
> [ 461.824927] Hardware name: HP-Pavilion FJ422AA-UUW
> a6551.sc/Benicia, BIOS 5.32 10/23/2008
> [ 461.824929] Workqueue: async async_run_entry_fn
> [ 461.824936] RIP: 0010:xhci_resume+0x3fe/0x5a0
> [ 461.824941] Code: 04 f6 c4 08 74 5a 41 bd 7b 6f 98 00 eb 21 49 83
> ed 01 0f 84 a0 01 00 00 bf c7 10 00 00 e8 1a fa 3e 00 f3 90 48 8b 04
> 24 8b 00 <f6> c4 08 74 31 83 f8 ff 75 da b8 ed ff ff ff 48 8b 0b 89 c2
> 48 c7
> [ 461.824943] RSP: 0000:ffff9ed3003ebd68 EFLAGS: 00000082
> [ 461.824945] RAX: 0000000000000801 RBX: ffff9112c241a250 RCX: ffff9ed30043e024
> [ 461.824947] RDX: 0000000000000987 RSI: 0000000000000003 RDI: 0000000bf69fa402
> [ 461.824948] RBP: ffff9112c241a000 R08: 0000000000000960 R09: 0000000000000003
> [ 461.824950] R10: 0000000000000003 R11: ffffffff95258f20 R12: 0000000000000000
> [ 461.824951] R13: 0000000000268925 R14: ffff9112c241a290 R15: 0000000000000000
> [ 461.824952] FS: 0000000000000000(0000) GS:ffff9113e6604000(0000)
> knlGS:0000000000000000
> [ 461.824954] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ 461.824956] CR2: 0000000000000000 CR3: 000000000faeb000 CR4: 00000000000006f0
> [ 461.824957] Call Trace:
> [ 461.824960] <TASK>
> [ 461.824963] resume_common+0x89/0xd0
> [ 461.824968] ? __pfx_pci_pm_resume+0x10/0x10
> [ 461.824973] dpm_run_callback+0x3d/0x160
> [ 461.824977] ? dpm_wait_for_superior+0xf7/0x150
> [ 461.824981] device_resume+0x158/0x250
> [ 461.824984] async_resume+0x14/0x20
> [ 461.824987] async_run_entry_fn+0x21/0xa0
> [ 461.824991] process_one_work+0x163/0x370
> [ 461.824994] worker_thread+0x18f/0x300
> [ 461.824997] ? __pfx_worker_thread+0x10/0x10
> [ 461.824999] kthread+0xda/0x110
> [ 461.825003] ? __pfx_kthread+0x10/0x10
> [ 461.825006] ret_from_fork+0x1af/0x2b0
> [ 461.825009] ? __pfx_kthread+0x10/0x10
> [ 461.825012] ret_from_fork_asm+0x1a/0x30
> [ 461.825017] </TASK>
> [ 462.302911] rcu: INFO: rcu_preempt detected expedited stalls on
> CPUs/tasks: { 3-...D } 21425 jiffies s: 365 root: 0x8/.
> [ 462.302917] rcu: blocking rcu_node structures (internal RCU debug):
> [ 462.302919] Sending NMI from CPU 1 to CPUs 3:
> [ 462.302922] NMI backtrace for cpu 3
> [ 462.302925] CPU: 3 UID: 0 PID: 513 Comm: kworker/u18:6 Tainted: G S
> 7.0.3 #2 PREEMPT(full)
> [ 462.302928] Tainted: [S]=CPU_OUT_OF_SPEC
> [ 462.302929] Hardware name: HP-Pavilion FJ422AA-UUW
> a6551.sc/Benicia, BIOS 5.32 10/23/2008
> [ 462.302930] Workqueue: async async_run_entry_fn
> [ 462.302933] RIP: 0010:xhci_resume+0x3fe/0x5a0
> [ 462.302936] Code: 04 f6 c4 08 74 5a 41 bd 7b 6f 98 00 eb 21 49 83
> ed 01 0f 84 a0 01 00 00 bf c7 10 00 00 e8 1a fa 3e 00 f3 90 48 8b 04
> 24 8b 00 <f6> c4 08 74 31 83 f8 ff 75 da b8 ed ff ff ff 48 8b 0b 89 c2
> 48 c7
> [ 462.302938] RSP: 0000:ffff9ed3003ebd68 EFLAGS: 00000082
> [ 462.302940] RAX: 0000000000000801 RBX: ffff9112c241a250 RCX: ffff9ed30043e024
> [ 462.302941] RDX: 0000000000000987 RSI: 0000000000000003 RDI: 0000000c3b0074cb
> [ 462.302943] RBP: ffff9112c241a000 R08: 0000000000000960 R09: 0000000000000003
> [ 462.302944] R10: 0000000000000003 R11: ffffffff95258f20 R12: 0000000000000000
> [ 462.302945] R13: 000000000023f18b R14: ffff9112c241a290 R15: 0000000000000000
> [ 462.302947] FS: 0000000000000000(0000) GS:ffff9113e6604000(0000)
> knlGS:0000000000000000
> [ 462.302949] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ 462.302950] CR2: 0000000000000000 CR3: 000000000faeb000 CR4: 00000000000006f0
> [ 462.302951] Call Trace:
> [ 462.302952] <TASK>
> [ 462.302953] resume_common+0x89/0xd0
> [ 462.302957] ? __pfx_pci_pm_resume+0x10/0x10
> [ 462.302961] dpm_run_callback+0x3d/0x160
> [ 462.302964] ? dpm_wait_for_superior+0xf7/0x150
> [ 462.302967] device_resume+0x158/0x250
> [ 462.302970] async_resume+0x14/0x20
> [ 462.302974] async_run_entry_fn+0x21/0xa0
> [ 462.302977] process_one_work+0x163/0x370
> [ 462.302980] worker_thread+0x18f/0x300
> [ 462.302983] ? __pfx_worker_thread+0x10/0x10
> [ 462.302985] kthread+0xda/0x110
> [ 462.302988] ? __pfx_kthread+0x10/0x10
> [ 462.302991] ret_from_fork+0x1af/0x2b0
> [ 462.302993] ? __pfx_kthread+0x10/0x10
> [ 462.302997] ret_from_fork_asm+0x1a/0x30
> [ 462.303001] </TASK>
> [ 468.932307] xhci-pci-renesas 0000:03:00.0: Controller not ready at
> resume -110
> [ 468.932332] clocksource: Long readout interval, skipping watchdog
> check: cs_nsec: 26925372067 wd_nsec: 26925364392
> [ 468.932394] xhci-pci-renesas 0000:03:00.0: PCI post-resume error -110!
> [ 468.932401] xhci-pci-renesas 0000:03:00.0: HC died; cleaning up
> [ 468.932429] xhci-pci-renesas 0000:03:00.0: PM: dpm_run_callback():
> pci_pm_resume returns -110
> [ 468.932434] xhci-pci-renesas 0000:03:00.0: PM: failed to resume
> async: error -110
That's waiting 10 seconds with IRQs disabled for USBSTS.CNR to clear.
Sadly, a70bcbc322837 doesn't explain why such long timeout was used.
That being said, this bit should clear, so something is wrong.
Similar 0015 controllers have the RESET_ON_RESUME quirk applied. Sadly
again, the reason isn't documented in all detail we could wish for.
The quirk would apparently try a reset without looking at CNR (which is
frankly a spec violation) and only then test CNR.
Wonder if xhci_hcd.quirks=0x80 boot parameter would make a difference?
> This is on vanilla 7.0.3. If I add the firmware (renesas_usb_fw.mem,
> sha256=177560c224c73...) it fails to load on boot and I get a massive
> stall in bootup:
>
> [ 0.374764] pci 0000:00:1c.1: enabling device (0106 -> 0107)
> [ 6.295099] pci 0000:03:00.0: xHCI HW not ready after 5 sec (HC
> bug?) status = 0x801
> [ 6.295198] pci 0000:03:00.0: quirk_usb_early_handoff+0x0/0x700
> took 5781678 usecs
That's early boot, presence of FW files shouldn't have any effect.
Perhaps it happens *after* failing to load FW or loading wrong one,
then rebooting without power cycle or something like that?
Regards,
Michal
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: renesas 1912:0014 failures
2026-05-12 10:27 ` Michal Pecio
@ 2026-05-12 14:40 ` Anders Thomson
2026-05-12 17:02 ` Michal Pecio
0 siblings, 1 reply; 10+ messages in thread
From: Anders Thomson @ 2026-05-12 14:40 UTC (permalink / raw)
To: Michal Pecio; +Cc: linux-usb, Mathias Nyman
Adding that quirk to the boot cmdline, caused this on resume:
[ 1357.247864] usb usb10: root hub lost power or was reset
[ 1385.611310] xhci-pci-renesas 0000:03:00.0: PCI post-resume error -110!
[ 1385.611438] xhci-pci-renesas 0000:03:00.0: HC died; cleaning up
[ 1385.611491] xhci-pci-renesas 0000:03:00.0: PM: dpm_run_callback():
pci_pm_resume returns -110
[ 1385.611506] xhci-pci-renesas 0000:03:00.0: PM: failed to resume
async: error -110
and the attached disk is not recognized (obviously).
No stack traces, though.
Anders
On Tue, May 12, 2026 at 12:27 PM Michal Pecio <michal.pecio@gmail.com> wrote:
>
> On Wed, 6 May 2026 14:58:44 +0200, Anders Thomson wrote:
> > Hi,
> >
> > I've received a Renesas pcie usb3 card which fails to suspend (to ram)
> > correctly.
> >
> > Regular boots appear to be working fine, but upon resuming from
> > suspend, I get this log:
> >
> > [ 461.824899] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
> > [ 461.824902] rcu: 3-...0: (3 ticks this GP)
> > idle=0884/1/0x4000000000000000 softirq=2388/2389 fqs=5249
> > [ 461.824907] rcu: (detected by 1, t=21002 jiffies, g=5201, q=24 ncpus=4)
> > [ 461.824910] Sending NMI from CPU 1 to CPUs 3:
> > [ 461.824917] NMI backtrace for cpu 3
> > [ 461.824922] CPU: 3 UID: 0 PID: 513 Comm: kworker/u18:6 Tainted: G S
> > 7.0.3 #2 PREEMPT(full)
> > [ 461.824926] Tainted: [S]=CPU_OUT_OF_SPEC
> > [ 461.824927] Hardware name: HP-Pavilion FJ422AA-UUW
> > a6551.sc/Benicia, BIOS 5.32 10/23/2008
> > [ 461.824929] Workqueue: async async_run_entry_fn
> > [ 461.824936] RIP: 0010:xhci_resume+0x3fe/0x5a0
> > [ 461.824941] Code: 04 f6 c4 08 74 5a 41 bd 7b 6f 98 00 eb 21 49 83
> > ed 01 0f 84 a0 01 00 00 bf c7 10 00 00 e8 1a fa 3e 00 f3 90 48 8b 04
> > 24 8b 00 <f6> c4 08 74 31 83 f8 ff 75 da b8 ed ff ff ff 48 8b 0b 89 c2
> > 48 c7
> > [ 461.824943] RSP: 0000:ffff9ed3003ebd68 EFLAGS: 00000082
> > [ 461.824945] RAX: 0000000000000801 RBX: ffff9112c241a250 RCX: ffff9ed30043e024
> > [ 461.824947] RDX: 0000000000000987 RSI: 0000000000000003 RDI: 0000000bf69fa402
> > [ 461.824948] RBP: ffff9112c241a000 R08: 0000000000000960 R09: 0000000000000003
> > [ 461.824950] R10: 0000000000000003 R11: ffffffff95258f20 R12: 0000000000000000
> > [ 461.824951] R13: 0000000000268925 R14: ffff9112c241a290 R15: 0000000000000000
> > [ 461.824952] FS: 0000000000000000(0000) GS:ffff9113e6604000(0000)
> > knlGS:0000000000000000
> > [ 461.824954] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> > [ 461.824956] CR2: 0000000000000000 CR3: 000000000faeb000 CR4: 00000000000006f0
> > [ 461.824957] Call Trace:
> > [ 461.824960] <TASK>
> > [ 461.824963] resume_common+0x89/0xd0
> > [ 461.824968] ? __pfx_pci_pm_resume+0x10/0x10
> > [ 461.824973] dpm_run_callback+0x3d/0x160
> > [ 461.824977] ? dpm_wait_for_superior+0xf7/0x150
> > [ 461.824981] device_resume+0x158/0x250
> > [ 461.824984] async_resume+0x14/0x20
> > [ 461.824987] async_run_entry_fn+0x21/0xa0
> > [ 461.824991] process_one_work+0x163/0x370
> > [ 461.824994] worker_thread+0x18f/0x300
> > [ 461.824997] ? __pfx_worker_thread+0x10/0x10
> > [ 461.824999] kthread+0xda/0x110
> > [ 461.825003] ? __pfx_kthread+0x10/0x10
> > [ 461.825006] ret_from_fork+0x1af/0x2b0
> > [ 461.825009] ? __pfx_kthread+0x10/0x10
> > [ 461.825012] ret_from_fork_asm+0x1a/0x30
> > [ 461.825017] </TASK>
> > [ 462.302911] rcu: INFO: rcu_preempt detected expedited stalls on
> > CPUs/tasks: { 3-...D } 21425 jiffies s: 365 root: 0x8/.
> > [ 462.302917] rcu: blocking rcu_node structures (internal RCU debug):
> > [ 462.302919] Sending NMI from CPU 1 to CPUs 3:
> > [ 462.302922] NMI backtrace for cpu 3
> > [ 462.302925] CPU: 3 UID: 0 PID: 513 Comm: kworker/u18:6 Tainted: G S
> > 7.0.3 #2 PREEMPT(full)
> > [ 462.302928] Tainted: [S]=CPU_OUT_OF_SPEC
> > [ 462.302929] Hardware name: HP-Pavilion FJ422AA-UUW
> > a6551.sc/Benicia, BIOS 5.32 10/23/2008
> > [ 462.302930] Workqueue: async async_run_entry_fn
> > [ 462.302933] RIP: 0010:xhci_resume+0x3fe/0x5a0
> > [ 462.302936] Code: 04 f6 c4 08 74 5a 41 bd 7b 6f 98 00 eb 21 49 83
> > ed 01 0f 84 a0 01 00 00 bf c7 10 00 00 e8 1a fa 3e 00 f3 90 48 8b 04
> > 24 8b 00 <f6> c4 08 74 31 83 f8 ff 75 da b8 ed ff ff ff 48 8b 0b 89 c2
> > 48 c7
> > [ 462.302938] RSP: 0000:ffff9ed3003ebd68 EFLAGS: 00000082
> > [ 462.302940] RAX: 0000000000000801 RBX: ffff9112c241a250 RCX: ffff9ed30043e024
> > [ 462.302941] RDX: 0000000000000987 RSI: 0000000000000003 RDI: 0000000c3b0074cb
> > [ 462.302943] RBP: ffff9112c241a000 R08: 0000000000000960 R09: 0000000000000003
> > [ 462.302944] R10: 0000000000000003 R11: ffffffff95258f20 R12: 0000000000000000
> > [ 462.302945] R13: 000000000023f18b R14: ffff9112c241a290 R15: 0000000000000000
> > [ 462.302947] FS: 0000000000000000(0000) GS:ffff9113e6604000(0000)
> > knlGS:0000000000000000
> > [ 462.302949] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> > [ 462.302950] CR2: 0000000000000000 CR3: 000000000faeb000 CR4: 00000000000006f0
> > [ 462.302951] Call Trace:
> > [ 462.302952] <TASK>
> > [ 462.302953] resume_common+0x89/0xd0
> > [ 462.302957] ? __pfx_pci_pm_resume+0x10/0x10
> > [ 462.302961] dpm_run_callback+0x3d/0x160
> > [ 462.302964] ? dpm_wait_for_superior+0xf7/0x150
> > [ 462.302967] device_resume+0x158/0x250
> > [ 462.302970] async_resume+0x14/0x20
> > [ 462.302974] async_run_entry_fn+0x21/0xa0
> > [ 462.302977] process_one_work+0x163/0x370
> > [ 462.302980] worker_thread+0x18f/0x300
> > [ 462.302983] ? __pfx_worker_thread+0x10/0x10
> > [ 462.302985] kthread+0xda/0x110
> > [ 462.302988] ? __pfx_kthread+0x10/0x10
> > [ 462.302991] ret_from_fork+0x1af/0x2b0
> > [ 462.302993] ? __pfx_kthread+0x10/0x10
> > [ 462.302997] ret_from_fork_asm+0x1a/0x30
> > [ 462.303001] </TASK>
> > [ 468.932307] xhci-pci-renesas 0000:03:00.0: Controller not ready at
> > resume -110
> > [ 468.932332] clocksource: Long readout interval, skipping watchdog
> > check: cs_nsec: 26925372067 wd_nsec: 26925364392
> > [ 468.932394] xhci-pci-renesas 0000:03:00.0: PCI post-resume error -110!
> > [ 468.932401] xhci-pci-renesas 0000:03:00.0: HC died; cleaning up
> > [ 468.932429] xhci-pci-renesas 0000:03:00.0: PM: dpm_run_callback():
> > pci_pm_resume returns -110
> > [ 468.932434] xhci-pci-renesas 0000:03:00.0: PM: failed to resume
> > async: error -110
>
> That's waiting 10 seconds with IRQs disabled for USBSTS.CNR to clear.
> Sadly, a70bcbc322837 doesn't explain why such long timeout was used.
>
> That being said, this bit should clear, so something is wrong.
>
> Similar 0015 controllers have the RESET_ON_RESUME quirk applied. Sadly
> again, the reason isn't documented in all detail we could wish for.
> The quirk would apparently try a reset without looking at CNR (which is
> frankly a spec violation) and only then test CNR.
>
> Wonder if xhci_hcd.quirks=0x80 boot parameter would make a difference?
>
> > This is on vanilla 7.0.3. If I add the firmware (renesas_usb_fw.mem,
> > sha256=177560c224c73...) it fails to load on boot and I get a massive
> > stall in bootup:
> >
> > [ 0.374764] pci 0000:00:1c.1: enabling device (0106 -> 0107)
> > [ 6.295099] pci 0000:03:00.0: xHCI HW not ready after 5 sec (HC
> > bug?) status = 0x801
> > [ 6.295198] pci 0000:03:00.0: quirk_usb_early_handoff+0x0/0x700
> > took 5781678 usecs
>
> That's early boot, presence of FW files shouldn't have any effect.
> Perhaps it happens *after* failing to load FW or loading wrong one,
> then rebooting without power cycle or something like that?
>
> Regards,
> Michal
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: renesas 1912:0014 failures
2026-05-12 14:40 ` Anders Thomson
@ 2026-05-12 17:02 ` Michal Pecio
2026-05-12 22:34 ` Anders Thomson
0 siblings, 1 reply; 10+ messages in thread
From: Michal Pecio @ 2026-05-12 17:02 UTC (permalink / raw)
To: Anders Thomson; +Cc: linux-usb, Mathias Nyman
On Tue, 12 May 2026 16:40:30 +0200, Anders Thomson wrote:
> Adding that quirk to the boot cmdline, caused this on resume:
>
> [ 1357.247864] usb usb10: root hub lost power or was reset
> [ 1385.611310] xhci-pci-renesas 0000:03:00.0: PCI post-resume error -110!
> [ 1385.611438] xhci-pci-renesas 0000:03:00.0: HC died; cleaning up
> [ 1385.611491] xhci-pci-renesas 0000:03:00.0: PM: dpm_run_callback():
> pci_pm_resume returns -110
> [ 1385.611506] xhci-pci-renesas 0000:03:00.0: PM: failed to resume
> async: error -110
Looks like the quirk worked, but the chip is still stuck for good.
Sounds like it happens every time?
Does it happen without any connected devices?
Any chance that something goes weird already during suspend?
Maybe try to collect suspend/resume log with extra debug info:
echo 'module xhci_hcd +p' >/proc/dynamic_debug/control
dmesg -W |tee log.txt
# suspend and resume
echo 'module xhci_hcd -p' >/proc/dynamic_debug/control # disable
# stop dmesg, send log.txt
It's odd, I have a uPD720202 (the 2 port variant) and it never had
similar problems. But my card doesn't use the standby supply and
hence it fully power cycles the chip during S3 sleep, so it may be
apples to oranges if your card keeps aux power applied.
Regards,
Michal
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: renesas 1912:0014 failures
2026-05-12 17:02 ` Michal Pecio
@ 2026-05-12 22:34 ` Anders Thomson
2026-05-18 6:46 ` Michal Pecio
0 siblings, 1 reply; 10+ messages in thread
From: Anders Thomson @ 2026-05-12 22:34 UTC (permalink / raw)
To: Michal Pecio; +Cc: linux-usb, Mathias Nyman
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
[ 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
[ 500.421723] r8169 0000:02:00.0 enp2s0: Link is Down
[ 500.445507] OOM killer enabled.
[ 500.445548] Restarting tasks: Starting
[ 500.448081] Restarting tasks: Done
[ 500.448138] random: crng reseeded on system resumption
[ 500.448920] PM: suspend exit
[ 500.463568] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 500.463645] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 500.463708] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 500.464152] ata5: SATA link down (SStatus 0 SControl 300)
[ 500.464654] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 500.464885] ata6.00: configured for UDMA/33
[ 500.465423] sd 0:0:0:0: [sda] Starting disk
[ 500.466188] ata1.00: configured for UDMA/133
[ 500.484215] sd 2:0:0:0: [sdc] Starting disk
[ 500.486246] ata3.00: configured for UDMA/133
[ 500.667575] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 500.681515] sd 1:0:0:0: [sdb] Starting disk
[ 500.687837] ata2.00: configured for UDMA/133
[ 502.569318] sd 3:0:0:0: [sdd] Starting disk
[ 502.572754] ata4.00: configured for UDMA/133
[ 502.879209] r8169 0000:02:00.0 enp2s0: Link is Up - 1Gbps/Full -
flow control rx/tx
No devices attached to any port.
BR
Anders
On Tue, May 12, 2026 at 7:02 PM Michal Pecio <michal.pecio@gmail.com> wrote:
>
> On Tue, 12 May 2026 16:40:30 +0200, Anders Thomson wrote:
> > Adding that quirk to the boot cmdline, caused this on resume:
> >
> > [ 1357.247864] usb usb10: root hub lost power or was reset
> > [ 1385.611310] xhci-pci-renesas 0000:03:00.0: PCI post-resume error -110!
> > [ 1385.611438] xhci-pci-renesas 0000:03:00.0: HC died; cleaning up
> > [ 1385.611491] xhci-pci-renesas 0000:03:00.0: PM: dpm_run_callback():
> > pci_pm_resume returns -110
> > [ 1385.611506] xhci-pci-renesas 0000:03:00.0: PM: failed to resume
> > async: error -110
>
> Looks like the quirk worked, but the chip is still stuck for good.
>
> Sounds like it happens every time?
> Does it happen without any connected devices?
>
> Any chance that something goes weird already during suspend?
> Maybe try to collect suspend/resume log with extra debug info:
>
> echo 'module xhci_hcd +p' >/proc/dynamic_debug/control
> dmesg -W |tee log.txt
> # suspend and resume
> echo 'module xhci_hcd -p' >/proc/dynamic_debug/control # disable
> # stop dmesg, send log.txt
>
> It's odd, I have a uPD720202 (the 2 port variant) and it never had
> similar problems. But my card doesn't use the standby supply and
> hence it fully power cycles the chip during S3 sleep, so it may be
> apples to oranges if your card keeps aux power applied.
>
> Regards,
> Michal
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: renesas 1912:0014 failures
2026-05-12 22:34 ` Anders Thomson
@ 2026-05-18 6:46 ` Michal Pecio
2026-05-18 8:41 ` Anders Thomson
0 siblings, 1 reply; 10+ messages in thread
From: Michal Pecio @ 2026-05-18 6:46 UTC (permalink / raw)
To: Anders Thomson; +Cc: linux-usb, Mathias Nyman
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: renesas 1912:0014 failures
2026-05-18 6:46 ` Michal Pecio
@ 2026-05-18 8:41 ` Anders Thomson
2026-05-18 12:36 ` Anders Thomson
0 siblings, 1 reply; 10+ messages in thread
From: Anders Thomson @ 2026-05-18 8:41 UTC (permalink / raw)
To: Michal Pecio; +Cc: linux-usb, Mathias Nyman
On Mon, May 18, 2026 at 8:46 AM Michal Pecio <michal.pecio@gmail.com> wrote:
>
> 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.
The machine hangs on boot with the quirk. Without quirk i get:
[ 2.293602] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 2.303526] sr 5:0:0:0: Attached scsi CD-ROM sr0
[ 2.303603] sr 5:0:0:0: Attached scsi generic sg4 type 5
[ 28.493779] xhci-pci-renesas 0000:03:00.0: xHCI Host Controller
[ 28.493891] xhci-pci-renesas 0000:03:00.0: new USB bus registered,
assigned bus number 9
[ 28.499338] xhci-pci-renesas 0000:03:00.0: hcc params 0x014051cf
hci version 0x100 quirks 0x0000000100000090
Those 28.xxx renesas lines never show up with the quirk applied. The
machine works (waiting 10 minutes I get a logs from other kernel
threads), but the boot process is stopped. By the looks of it, no usb
probing completes.
> 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.
It is a pcie 1x card, with no external (molex) power supply, if that helps.
Regards
Anders
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: renesas 1912:0014 failures
2026-05-18 8:41 ` Anders Thomson
@ 2026-05-18 12:36 ` Anders Thomson
2026-05-23 16:32 ` Michal Pecio
0 siblings, 1 reply; 10+ messages in thread
From: Anders Thomson @ 2026-05-18 12:36 UTC (permalink / raw)
To: Michal Pecio; +Cc: linux-usb, Mathias Nyman
On Mon, May 18, 2026 at 10:41 AM Anders Thomson <andtho888@gmail.com> wrote:
>
> > I see you still have the quirk, but it doesn't matter, the chip is
> > stuck and doesn't work either way.
>
> The machine hangs on boot with the quirk. Without quirk i get:
> [ 2.293602] cdrom: Uniform CD-ROM driver Revision: 3.20
> [ 2.303526] sr 5:0:0:0: Attached scsi CD-ROM sr0
> [ 2.303603] sr 5:0:0:0: Attached scsi generic sg4 type 5
> [ 28.493779] xhci-pci-renesas 0000:03:00.0: xHCI Host Controller
> [ 28.493891] xhci-pci-renesas 0000:03:00.0: new USB bus registered,
> assigned bus number 9
> [ 28.499338] xhci-pci-renesas 0000:03:00.0: hcc params 0x014051cf
> hci version 0x100 quirks 0x0000000100000090
>
> Those 28.xxx renesas lines never show up with the quirk applied. The
> machine works (waiting 10 minutes I get a logs from other kernel
> threads), but the boot process is stopped. By the looks of it, no usb
> probing completes.
>
Some advances, perhaps. I _did_ get (twice) the boot to succeed with
the quirk (still with the 26 sec pause) . Both times was after a full
power cycle (PSU on/off). After a regular I/O Button press during, the
boot stalls. I'll run this a few times more to verify.
After successful boot with quirk, 1st suspend/resume without
peripherals attached, yielded:
[ 1057.321336] CPU3 is up
[ 1057.324889] ACPI: PM: Waking up from system sleep state S3
[ 1057.327299] usb usb2: root hub lost power or was reset
[ 1057.327321] usb usb4: root hub lost power or was reset
[ 1057.327387] usb usb5: root hub lost power or was reset
[ 1057.327406] usb usb6: root hub lost power or was reset
[ 1057.327455] usb usb7: root hub lost power or was reset
[ 1057.327484] usb usb8: root hub lost power or was reset
[ 1057.327587] usb usb9: root hub lost power or was reset
[ 1057.327589] usb usb10: root hub lost power or was reset
[ 1057.327592] xhci-pci-renesas 0000:03:00.0: Stop HCD
[ 1057.327599] xhci-pci-renesas 0000:03:00.0: // Halt the HC
[ 1057.327613] xhci-pci-renesas 0000:03:00.0: // Reset the HC
[ 1057.332908] xhci-pci-renesas 0000:03:00.0: Wait for controller to
be ready for doorbell rings
[ 1057.332958] xhci-pci-renesas 0000:03:00.0: // Disabling event ring interrupts
[ 1057.332967] xhci-pci-renesas 0000:03:00.0: cleaning up memory
[ 1057.332984] xhci-pci-renesas 0000:03:00.0: Freed interrupters
[ 1057.332986] xhci-pci-renesas 0000:03:00.0: Freed command ring
[ 1057.332992] xhci-pci-renesas 0000:03:00.0: Freed segment pool
[ 1057.332993] xhci-pci-renesas 0000:03:00.0: Freed device context pool
[ 1057.332995] xhci-pci-renesas 0000:03:00.0: Freed small stream array pool
[ 1057.332997] xhci-pci-renesas 0000:03:00.0: Freed xhci port bw array pool
[ 1057.332999] xhci-pci-renesas 0000:03:00.0: Freed medium stream array pool
[ 1057.333129] xhci-pci-renesas 0000:03:00.0: xhci_stop completed - status = 1
[ 1057.333131] xhci-pci-renesas 0000:03:00.0: Initialize the xhci_hcd
[ 1057.333133] xhci-pci-renesas 0000:03:00.0: Starting xhci_init
[ 1057.333137] xhci-pci-renesas 0000:03:00.0: HCD page size set to 4K
[ 1057.333141] xhci-pci-renesas 0000:03:00.0: Device context base
array address = 0x0x0000000002275000 (DMA), 0000000027fc954c (virt)
[ 1057.333148] xhci-pci-renesas 0000:03:00.0: Allocated command ring
at 000000002ad20c16
[ 1057.333150] xhci-pci-renesas 0000:03:00.0: First segment DMA is
0x0x0000000002279000
[ 1057.333152] xhci-pci-renesas 0000:03:00.0: Allocating primary event ring
[ 1057.333159] xhci-pci-renesas 0000:03:00.0: Allocating 4 scratchpad buffers
[ 1057.333194] xhci-pci-renesas 0000:03:00.0: Ext Cap
00000000f9dfb55c, port offset = 1, count = 4, revision = 0x3
[ 1057.333204] xhci-pci-renesas 0000:03:00.0: Ext Cap
00000000a5235153, port offset = 5, count = 4, revision = 0x2
[ 1057.333206] xhci-pci-renesas 0000:03:00.0: Found 4 USB 2.0 ports
and 4 USB 3.0 ports.
[ 1057.333209] xhci-pci-renesas 0000:03:00.0: xHC can handle at most
32 device slots
[ 1057.333217] xhci-pci-renesas 0000:03:00.0: Setting Max device slots
reg = 0x20
[ 1057.333232] xhci-pci-renesas 0000:03:00.0: Setting command ring
address to 0x2279001
[ 1057.333237] xhci-pci-renesas 0000:03:00.0: Doorbell array is
located at offset 0x800 from cap regs base addr
[ 1057.333247] xhci-pci-renesas 0000:03:00.0: // Write event ring
dequeue pointer, preserving EHB bit
[ 1057.333249] xhci-pci-renesas 0000:03:00.0: Finished xhci_init
[ 1057.333251] xhci-pci-renesas 0000:03:00.0: Start the primary HCD
[ 1057.333253] xhci-pci-renesas 0000:03:00.0: xhci_run
[ 1057.333263] xhci-pci-renesas 0000:03:00.0: ERST deq = 64'h2278000
[ 1057.333267] xhci-pci-renesas 0000:03:00.0: Finished xhci_run for main hcd
[ 1057.333415] xhci-pci-renesas 0000:03:00.0: Start the secondary HCD
[ 1057.333417] xhci-pci-renesas 0000:03:00.0: Enable interrupts
[ 1057.333426] xhci-pci-renesas 0000:03:00.0: Enable primary interrupter
[ 1057.333435] xhci-pci-renesas 0000:03:00.0: // Turn on HC, cmd = 0x5.
[ 1057.336587] xhci-pci-renesas 0000:03:00.0: xhci_resume: starting
usb9 port polling.
[ 1057.336611] xhci-pci-renesas 0000:03:00.0: xhci_hub_status_data:
stopping usb9 port polling
[ 1057.336644] xhci-pci-renesas 0000:03:00.0: set port power 9-1 ON,
portsc: 0x2a0
[ 1057.336654] xhci-pci-renesas 0000:03:00.0: set port power 10-1 ON,
portsc: 0x2a0
[ 1057.336675] xhci-pci-renesas 0000:03:00.0: set port power 10-2 ON,
portsc: 0x2a0
[ 1057.336683] xhci-pci-renesas 0000:03:00.0: set port power 9-2 ON,
portsc: 0x2a0
[ 1057.336698] xhci-pci-renesas 0000:03:00.0: set port power 10-3 ON,
portsc: 0x2a0
[ 1057.336707] xhci-pci-renesas 0000:03:00.0: set port power 9-3 ON,
portsc: 0x2a0
[ 1057.336722] xhci-pci-renesas 0000:03:00.0: set port power 10-4 ON,
portsc: 0x2a0
[ 1057.336731] xhci-pci-renesas 0000:03:00.0: set port power 9-4 ON,
portsc: 0x2a0
[ 1057.357444] xhci-pci-renesas 0000:03:00.0: Get port status 9-1
read: 0x2a0, return 0x100
[ 1057.357460] xhci-pci-renesas 0000:03:00.0: Get port status 9-2
read: 0x2a0, return 0x100
[ 1057.357473] xhci-pci-renesas 0000:03:00.0: Get port status 9-3
read: 0x2a0, return 0x100
[ 1057.357485] xhci-pci-renesas 0000:03:00.0: Get port status 9-4
read: 0x2a0, return 0x100
[ 1057.389904] r8169 0000:02:00.0 enp2s0: Link is Down
[ 1057.443447] xhci-pci-renesas 0000:03:00.0: Get port status 10-1
read: 0x2a0, return 0x2a0
[ 1057.443465] xhci-pci-renesas 0000:03:00.0: Get port status 10-2
read: 0x2a0, return 0x2a0
[ 1057.443478] xhci-pci-renesas 0000:03:00.0: Get port status 10-3
read: 0x2a0, return 0x2a0
[ 1057.443491] xhci-pci-renesas 0000:03:00.0: Get port status 10-4
read: 0x2a0, return 0x2a0
[ 1057.445180] OOM killer enabled.
[ 1057.445221] Restarting tasks: Starting
[ 1057.445387] xhci-pci-renesas 0000:03:00.0: set port remote wake
mask, actual port 10-1 status = 0xe0002a0
[ 1057.445422] xhci-pci-renesas 0000:03:00.0: xhci_hub_status_data:
stopping usb9 port polling
[ 1057.445498] Restarting tasks: Done
[ 1057.445597] random: crng reseeded on system resumption
[ 1057.445844] xhci-pci-renesas 0000:03:00.0: set port remote wake
mask, actual port 10-2 status = 0xe0002a0
[ 1057.445920] xhci-pci-renesas 0000:03:00.0: set port remote wake
mask, actual port 10-3 status = 0xe0002a0
[ 1057.445939] xhci-pci-renesas 0000:03:00.0: set port remote wake
mask, actual port 10-4 status = 0xe0002a0
[ 1057.449379] PM: suspend exit
[ 1057.472455] xhci-pci-renesas 0000:03:00.0: Get port status 10-1
read: 0x2a0, return 0x2a0
[ 1057.472485] xhci-pci-renesas 0000:03:00.0: Get port status 10-2
read: 0x2a0, return 0x2a0
[ 1057.472496] xhci-pci-renesas 0000:03:00.0: Get port status 10-3
read: 0x2a0, return 0x2a0
[ 1057.472505] xhci-pci-renesas 0000:03:00.0: Get port status 10-4
read: 0x2a0, return 0x2a0
[ 1057.648805] ata2: SATA link down (SStatus 0 SControl 300)
[ 1057.675671] xhci-pci-renesas 0000:03:00.0: set port remote wake
mask, actual port 10-1 status = 0xe0002a0
[ 1057.675702] xhci-pci-renesas 0000:03:00.0: set port remote wake
mask, actual port 10-2 status = 0xe0002a0
[ 1057.675727] xhci-pci-renesas 0000:03:00.0: set port remote wake
mask, actual port 10-3 status = 0xe0002a0
[ 1057.675750] xhci-pci-renesas 0000:03:00.0: set port remote wake
mask, actual port 10-4 status = 0xe0002a0
[ 1057.702449] xhci-pci-renesas 0000:03:00.0: Get port status 10-1
read: 0x2a0, return 0x2a0
[ 1057.702473] xhci-pci-renesas 0000:03:00.0: Get port status 10-2
read: 0x2a0, return 0x2a0
[ 1057.702489] xhci-pci-renesas 0000:03:00.0: Get port status 10-3
read: 0x2a0, return 0x2a0
[ 1057.702505] xhci-pci-renesas 0000:03:00.0: Get port status 10-4
read: 0x2a0, return 0x2a0
[ 1057.907650] xhci-pci-renesas 0000:03:00.0: set port remote wake
mask, actual port 10-1 status = 0xe0002a0
[ 1057.907685] xhci-pci-renesas 0000:03:00.0: set port remote wake
mask, actual port 10-2 status = 0xe0002a0
[ 1057.907710] xhci-pci-renesas 0000:03:00.0: set port remote wake
mask, actual port 10-3 status = 0xe0002a0
[ 1057.907734] xhci-pci-renesas 0000:03:00.0: set port remote wake
mask, actual port 10-4 status = 0xe0002a0
[ 1057.907788] xhci-pci-renesas 0000:03:00.0: xhci_hub_status_data:
stopping usb10 port polling
[ 1057.963448] xhci-pci-renesas 0000:03:00.0: xhci_hub_status_data:
stopping usb10 port polling
After the second suspend/resume, we got this:
[ 1695.841292] PM: suspend entry (deep)
[ 1696.015699] Filesystems sync: 0.174 seconds
[ 1696.016530] Freezing user space processes
[ 1696.017206] Freezing user space processes completed (elapsed 0.000 seconds)
[ 1696.017251] OOM killer disabled.
[ 1696.017289] Freezing remaining freezable tasks
[ 1696.018205] Freezing remaining freezable tasks completed (elapsed
0.000 seconds)
[ 1696.018275] printk: Suspending console(s) (use no_console_suspend to debug)
[ 1696.023467] xhci-pci-renesas 0000:03:00.0: Get port status 9-1
read: 0x2a0, return 0x100
[ 1696.023494] xhci-pci-renesas 0000:03:00.0: Get port status 9-2
read: 0x2a0, return 0x100
[ 1696.023505] xhci-pci-renesas 0000:03:00.0: Get port status 9-3
read: 0x2a0, return 0x100
[ 1696.023515] xhci-pci-renesas 0000:03:00.0: Get port status 9-4
read: 0x2a0, return 0x100
[ 1696.047191] xhci-pci-renesas 0000:03:00.0: Get port status 10-1
read: 0x2a0, return 0x2a0
[ 1696.047209] xhci-pci-renesas 0000:03:00.0: Get port status 10-2
read: 0x2a0, return 0x2a0
[ 1696.047224] xhci-pci-renesas 0000:03:00.0: Get port status 10-3
read: 0x2a0, return 0x2a0
[ 1696.047237] xhci-pci-renesas 0000:03:00.0: Get port status 10-4
read: 0x2a0, return 0x2a0
[ 1696.048846] sd 7:0:0:0: [sdf] Synchronizing SCSI cache
[ 1696.048995] xhci-pci-renesas 0000:03:00.0: config port 10-1 wake
bits, portsc: 0x2a0, write: 0x202a0
[ 1696.049179] xhci-pci-renesas 0000:03:00.0: config port 10-2 wake
bits, portsc: 0x2a0, write: 0x202a0
[ 1696.049188] xhci-pci-renesas 0000:03:00.0: config port 10-3 wake
bits, portsc: 0x2a0, write: 0x202a0
[ 1696.049195] xhci-pci-renesas 0000:03:00.0: config port 10-4 wake
bits, portsc: 0x2a0, write: 0x202a0
[ 1696.049302] xhci-pci-renesas 0000:03:00.0: config port 9-1 wake
bits, portsc: 0x2a0, write: 0x202a0
[ 1696.049308] xhci-pci-renesas 0000:03:00.0: config port 9-2 wake
bits, portsc: 0x2a0, write: 0x202a0
[ 1696.049314] xhci-pci-renesas 0000:03:00.0: config port 9-3 wake
bits, portsc: 0x2a0, write: 0x202a0
[ 1696.049321] xhci-pci-renesas 0000:03:00.0: config port 9-4 wake
bits, portsc: 0x2a0, write: 0x202a0
[ 1696.049323] xhci-pci-renesas 0000:03:00.0: xhci_suspend: stopping
usb9 port polling.
[ 1696.049433] r8169 0000:02:00.0 enp2s0: Link is Down
[ 1696.059820] xhci-pci-renesas 0000:03:00.0: Setting command ring
address to 0x2279001
[ 1696.062191] sd 3:0:0:0: [sdd] Synchronizing SCSI cache
[ 1696.063214] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 1696.063248] sd 2:0:0:0: [sdc] Synchronizing SCSI cache
[ 1696.063457] ata1.00: Entering standby power mode
[ 1696.063722] ata3.00: Entering standby power mode
[ 1696.066204] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
[ 1696.441672] ata4.00: Entering standby power mode
[ 1697.174324] ACPI: PM: Preparing to enter system sleep state S3
[ 1697.174519] ACPI: PM: Saving platform NVS memory
[ 1697.174753] Disabling non-boot CPUs ...
[ 1697.176350] smpboot: CPU 3 is now offline
[ 1697.178481] smpboot: CPU 2 is now offline
[ 1697.180591] smpboot: CPU 1 is now offline
[ 1697.187535] ACPI: PM: Low-level resume complete
[ 1697.187562] ACPI: PM: Restoring platform NVS memory
[ 1697.188011] Enabling non-boot CPUs ...
[ 1697.188054] smpboot: Booting Node 0 Processor 1 APIC 0x1
[ 1697.198800] CPU1 is up
[ 1697.198829] smpboot: Booting Node 0 Processor 2 APIC 0x2
[ 1697.208029] CPU2 is up
[ 1697.208052] smpboot: Booting Node 0 Processor 3 APIC 0x3
[ 1697.217860] CPU3 is up
[ 1697.221248] ACPI: PM: Waking up from system sleep state S3
[ 1697.223806] usb usb2: root hub lost power or was reset
[ 1697.223828] usb usb4: root hub lost power or was reset
[ 1697.223894] usb usb5: root hub lost power or was reset
[ 1697.223914] usb usb6: root hub lost power or was reset
[ 1697.223952] usb usb7: root hub lost power or was reset
[ 1697.223979] usb usb8: root hub lost power or was reset
[ 1697.224069] usb usb9: root hub lost power or was reset
[ 1697.224070] usb usb10: root hub lost power or was reset
[ 1697.224073] xhci-pci-renesas 0000:03:00.0: Stop HCD
[ 1697.224075] xhci-pci-renesas 0000:03:00.0: // Halt the HC
[ 1697.224087] xhci-pci-renesas 0000:03:00.0: // Reset the HC
[ 1697.548223] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 1697.548260] ata5: SATA link down (SStatus 0 SControl 300)
[ 1697.549400] ata2: SATA link down (SStatus 0 SControl 300)
[ 1698.095163] ata6.00: configured for UDMA/33
[ 1702.593051] ata4: link is slow to respond, please be patient (ready=0)
[ 1703.059049] ata3: link is slow to respond, please be patient (ready=0)
[ 1703.112051] ata1: link is slow to respond, please be patient (ready=0)
[ 1703.523047] ata2: link is slow to respond, please be patient (ready=0)
[ 1705.544059] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1705.550387] sd 2:0:0:0: [sdc] Starting disk
[ 1705.552417] ata3.00: configured for UDMA/133
[ 1705.652075] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1705.652799] sd 0:0:0:0: [sda] Starting disk
[ 1705.653552] ata1.00: configured for UDMA/133
[ 1706.373048] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1708.237896] sd 3:0:0:0: [sdd] Starting disk
[ 1708.241270] ata4.00: configured for UDMA/133
[ 1710.319031] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1710.332338] ata2.00: configured for UDMA/133
[ 1718.229968] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
[ 1718.229971] rcu: 1-...0: (1 GPs behind)
idle=171c/1/0x4000000000000000 softirq=3787/3788 fqs=5036
[ 1718.229975] rcu: (detected by 3, t=21002 jiffies, g=7661, q=20 ncpus=4)
[ 1718.229979] Sending NMI from CPU 3 to CPUs 1:
[ 1718.229984] NMI backtrace for cpu 1
[ 1718.229988] CPU: 1 UID: 0 PID: 801 Comm: kworker/u17:2 Tainted: G S
7.0.3 #6 PREEMPT(full)
[ 1718.229992] Tainted: [S]=CPU_OUT_OF_SPEC
[ 1718.229993] Hardware name: HP-Pavilion FJ422AA-UUW
a6551.sc/Benicia, BIOS 5.32 10/23/2008
[ 1718.229995] Workqueue: async async_run_entry_fn
[ 1718.230003] RIP: 0010:delay_tsc+0x2e/0xa0
[ 1718.230007] Code: ff 05 56 b7 50 01 65 44 8b 0d 52 b7 50 01 0f ae
e8 0f 31 48 c1 e2 20 48 89 d7 48 09 c7 eb 21 65 ff 0d 36 b7 50 01 74
57 f3 90 <65> ff 05 2b b7 50 01 65 8b 35 28 b7 50 01 41 39 f1 75 28 41
89 f1
[ 1718.230010] RSP: 0000:ffff9dd300c97d10 EFLAGS: 00000083
[ 1718.230012] RAX: 0000000bf64c6add RBX: 0000000094c8677a RCX: 0000000000000002
[ 1718.230014] RDX: 0000000000000321 RSI: 0000000000000001 RDI: 0000000bf64c67bc
[ 1718.230015] RBP: 0000000000989680 R08: 0000000000000960 R09: 0000000000000001
[ 1718.230016] R10: 00000000ffffe000 R11: 0000000000000000 R12: 0000000000000000
[ 1718.230018] R13: 0000000000000002 R14: ffff9dd300316020 R15: 0000000000000001
[ 1718.230019] FS: 0000000000000000(0000) GS:ffff98c1466c5000(0000)
knlGS:0000000000000000
[ 1718.230021] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 1718.230022] CR2: 0000000000000000 CR3: 0000000005dc8000 CR4: 00000000000026f0
[ 1718.230024] Call Trace:
[ 1718.230027] <TASK>
[ 1718.230028] xhci_handshake+0x6e/0xc0
[ 1718.230034] xhci_reset+0x65/0x110
[ 1718.230036] xhci_resume+0x146/0x710
[ 1718.230039] resume_common+0x8b/0x110
[ 1718.230043] ? __pfx_pci_pm_resume+0x10/0x10
[ 1718.230046] dpm_run_callback+0x4b/0x170
[ 1718.230050] device_resume+0x158/0x250
[ 1718.230052] async_resume+0x14/0x20
[ 1718.230054] async_run_entry_fn+0x29/0x130
[ 1718.230058] process_one_work+0x163/0x370
[ 1718.230062] worker_thread+0x18f/0x300
[ 1718.230065] ? __pfx_worker_thread+0x10/0x10
[ 1718.230068] kthread+0xda/0x110
[ 1718.230072] ? __pfx_kthread+0x10/0x10
[ 1718.230075] ret_from_fork+0x1af/0x2b0
[ 1718.230078] ? __pfx_kthread+0x10/0x10
[ 1718.230081] ret_from_fork_asm+0x1a/0x30
[ 1718.230086] </TASK>
[ 1718.758984] rcu: INFO: rcu_preempt detected expedited stalls on
CPUs/tasks: { 1-...D } 21306 jiffies s: 489 root: 0x2/.
[ 1718.758991] rcu: blocking rcu_node structures (internal RCU debug):
[ 1718.758993] Sending NMI from CPU 0 to CPUs 1:
[ 1718.758997] NMI backtrace for cpu 1
[ 1718.758999] CPU: 1 UID: 0 PID: 801 Comm: kworker/u17:2 Tainted: G S
7.0.3 #6 PREEMPT(full)
[ 1718.759002] Tainted: [S]=CPU_OUT_OF_SPEC
[ 1718.759003] Hardware name: HP-Pavilion FJ422AA-UUW
a6551.sc/Benicia, BIOS 5.32 10/23/2008
[ 1718.759004] Workqueue: async async_run_entry_fn
[ 1718.759007] RIP: 0010:xhci_handshake+0x51/0xc0
[ 1718.759010] Code: fa 8b 07 89 f1 49 89 fe 41 89 f5 21 c1 41 39 cc
75 22 eb 3c f3 90 48 81 eb e9 03 00 00 48 89 da 48 c1 ea 3f 44 21 fa
41 8b 06 <44> 89 e9 21 c1 44 39 e1 74 1c 83 f8 ff 74 2d 84 d2 75 3d bf
c7 10
[ 1718.759012] RSP: 0000:ffff9dd300c97d18 EFLAGS: 00000046
[ 1718.759014] RAX: 0000000000000002 RBX: 00000000898430c3 RCX: 0000000000000002
[ 1718.759015] RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000c41f90e71
[ 1718.759016] RBP: 0000000000989680 R08: 0000000000000960 R09: 0000000000000001
[ 1718.759018] R10: 00000000ffffe000 R11: 0000000000000000 R12: 0000000000000000
[ 1718.759019] R13: 0000000000000002 R14: ffff9dd300316020 R15: 0000000000000001
[ 1718.759020] FS: 0000000000000000(0000) GS:ffff98c1466c5000(0000)
knlGS:0000000000000000
[ 1718.759022] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 1718.759024] CR2: 0000000000000000 CR3: 0000000005dc8000 CR4: 00000000000026f0
[ 1718.759025] Call Trace:
[ 1718.759026] <TASK>
[ 1718.759027] xhci_reset+0x65/0x110
[ 1718.759029] xhci_resume+0x146/0x710
[ 1718.759032] resume_common+0x8b/0x110
[ 1718.759035] ? __pfx_pci_pm_resume+0x10/0x10
[ 1718.759037] dpm_run_callback+0x4b/0x170
[ 1718.759040] device_resume+0x158/0x250
[ 1718.759042] async_resume+0x14/0x20
[ 1718.759044] async_run_entry_fn+0x29/0x130
[ 1718.759048] process_one_work+0x163/0x370
[ 1718.759050] worker_thread+0x18f/0x300
[ 1718.759053] ? __pfx_worker_thread+0x10/0x10
[ 1718.759056] kthread+0xda/0x110
[ 1718.759059] ? __pfx_kthread+0x10/0x10
[ 1718.759062] ret_from_fork+0x1af/0x2b0
[ 1718.759065] ? __pfx_kthread+0x10/0x10
[ 1718.759068] ret_from_fork_asm+0x1a/0x30
[ 1718.759072] </TASK>
[ 1725.214850] clocksource: Long readout interval, skipping watchdog
check: cs_nsec: 27695782517 wd_nsec: 27695786524
[ 1725.214860] xhci-pci-renesas 0000:03:00.0: PCI post-resume error -110!
[ 1725.214863] xhci-pci-renesas 0000:03:00.0: HC died; cleaning up
[ 1725.214875] xhci-pci-renesas 0000:03:00.0: PM: dpm_run_callback():
pci_pm_resume returns -110
[ 1725.214879] xhci-pci-renesas 0000:03:00.0: PM: failed to resume
async: error -110
[ 1725.217115] r8169 0000:02:00.0 enp2s0: Link is Down
[ 1725.240097] sd 1:0:0:0: [sdb] Starting disk
[ 1725.253882] OOM killer enabled.
[ 1725.253932] Restarting tasks: Starting
[ 1725.254172] Restarting tasks: Done
[ 1725.254251] random: crng reseeded on system resumption
[ 1725.254860] PM: suspend exit
[ 1727.460670] r8169 0000:02:00.0 enp2s0: Link is Up - 1Gbps/Full -
flow control rx/tx
[ 2004.214804] kworker/u17:31 (678) used greatest stack depth: 12248 bytes left
I hope that sheds some light on things.
Br,
Anders
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: renesas 1912:0014 failures
2026-05-18 12:36 ` Anders Thomson
@ 2026-05-23 16:32 ` Michal Pecio
2026-05-26 19:12 ` Anders Thomson
0 siblings, 1 reply; 10+ messages in thread
From: Michal Pecio @ 2026-05-23 16:32 UTC (permalink / raw)
To: Anders Thomson; +Cc: linux-usb, Mathias Nyman
On Mon, 18 May 2026 14:36:18 +0200, Anders Thomson wrote:
> On Mon, May 18, 2026 at 10:41 AM Anders Thomson <andtho888@gmail.com> wrote:
> >
>
> > > I see you still have the quirk, but it doesn't matter, the chip is
> > > stuck and doesn't work either way.
> >
> > The machine hangs on boot with the quirk. Without quirk i get:
> > [ 2.293602] cdrom: Uniform CD-ROM driver Revision: 3.20
> > [ 2.303526] sr 5:0:0:0: Attached scsi CD-ROM sr0
> > [ 2.303603] sr 5:0:0:0: Attached scsi generic sg4 type 5
> > [ 28.493779] xhci-pci-renesas 0000:03:00.0: xHCI Host Controller
> > [ 28.493891] xhci-pci-renesas 0000:03:00.0: new USB bus registered,
> > assigned bus number 9
> > [ 28.499338] xhci-pci-renesas 0000:03:00.0: hcc params 0x014051cf
> > hci version 0x100 quirks 0x0000000100000090
> >
> > Those 28.xxx renesas lines never show up with the quirk applied.
> > The machine works (waiting 10 minutes I get a logs from other kernel
> > threads), but the boot process is stopped. By the looks of it, no
> > usb probing completes.
> >
> Some advances, perhaps. I _did_ get (twice) the boot to succeed with
> the quirk (still with the 26 sec pause) . Both times was after a full
> power cycle (PSU on/off). After a regular I/O Button press during, the
> boot stalls. I'll run this a few times more to verify.
xhci_hcd.quirks=0x80 should have no effect on anything besides
suspend/resume. If you see differences in boot behavior, it probably
is an effect of suspend/resume cycles performed or attempted during
the previous boot. It seems that the chip gets into some bad state
which requires a power cycle to fix. BTW, do you mean just turning off
the computer, or disconnecting the PSU to remove standby power?
FYI, the quirk performs full xHCI reset during resume and prevents
selectively suspending the chip when all its USB devices are suspended
but the system is running (not going to sleep). It doesn't prevent
suspending when no USB devices are connected at all. And either way,
runtime PM may be turned off, see if this is 'on' or 'auto':
cat /sys/bus/pci/devices/0000:03:00.0/power/control
> After successful boot with quirk, 1st suspend/resume without
> peripherals attached, yielded:
> [...]
>
> After the second suspend/resume, we got this:
> [...]
> [ 1697.224087] xhci-pci-renesas 0000:03:00.0: // Reset the HC
> [...]
> [ 1725.214860] xhci-pci-renesas 0000:03:00.0: PCI post-resume error -110!
> [ 1725.214863] xhci-pci-renesas 0000:03:00.0: HC died; cleaning up
> [ 1725.214875] xhci-pci-renesas 0000:03:00.0: PM: dpm_run_callback():
> pci_pm_resume returns -110
> [ 1725.214879] xhci-pci-renesas 0000:03:00.0: PM: failed to resume
I have no idea why it works the first time but not the second.
Not what happens if the same is done without the quirk?
Maybe try s2idle ("freeze") instead of S3 sleep? But that doesn't
provide the same power saving on older HW.
Regards,
Michal
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: renesas 1912:0014 failures
2026-05-23 16:32 ` Michal Pecio
@ 2026-05-26 19:12 ` Anders Thomson
0 siblings, 0 replies; 10+ messages in thread
From: Anders Thomson @ 2026-05-26 19:12 UTC (permalink / raw)
To: Michal Pecio; +Cc: linux-usb, Mathias Nyman
> > Some advances, perhaps. I _did_ get (twice) the boot to succeed with
> > the quirk (still with the 26 sec pause) . Both times was after a full
> > power cycle (PSU on/off). After a regular I/O Button press during, the
> > boot stalls. I'll run this a few times more to verify.
>
> xhci_hcd.quirks=0x80 should have no effect on anything besides
> suspend/resume. If you see differences in boot behavior, it probably
> is an effect of suspend/resume cycles performed or attempted during
> the previous boot. It seems that the chip gets into some bad state
> which requires a power cycle to fix. BTW, do you mean just turning off
> the computer, or disconnecting the PSU to remove standby power?
>
Ok. That can be the case. I did power cycle with the (240V presumably)
power button on the back of the case.
To be sure, I now disconnected the power cord for 6 hours, and it
subsequently booted nicely with the quirk.
[ 0.000000] Command line: root=/dev/sda2
init=/usr/lib/systemd/systemd mitigations=off xhci_hcd.quirks=0x80
<snip>
[ 87.156173] EXT4-fs (dm-7): mounted filesystem
67bc6f66-1a28-49d3-b834-3a49777f62e6 r/w with ordered data mode. Quota
mode: none.
[ 87.173234] systemd-tmpfile (363) used greatest stack depth: 12272 bytes left
Booted with no device attached. I now attach an old iPod
[ 88.029820] EXT4-fs (dm-1): mounted filesystem
43370d08-08a3-44a6-9809-7de71d91213a r/w with ordered data mode. Quota
mode: none.
[ 106.553175] EXT4-fs (dm-6): unmounting filesystem
aacac1ab-8727-4008-94ed-3997aa0c5cf2.
[ 107.627798] EXT4-fs (dm-7): unmounting filesystem
67bc6f66-1a28-49d3-b834-3a49777f62e6.
[ 161.704296] usb 9-4: new high-speed USB device number 2 using
xhci-pci-renesas
[ 161.835336] usb 9-4: New USB device found, idVendor=05ac,
idProduct=1265, bcdDevice= 0.01
[ 161.835411] usb 9-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 161.835461] usb 9-4: Product: iPod
[ 161.835506] usb 9-4: Manufacturer: Apple Inc.
[ 161.835553] usb 9-4: SerialNumber: 000A27001EAE1B01
[ 161.854035] usb-storage 9-4:1.0: USB Mass Storage device detected
[ 161.854251] scsi host8: usb-storage 9-4:1.0
[ 162.907030] scsi 8:0:0:0: Direct-Access Apple iPod
1.70 PQ: 0 ANSI: 0
[ 162.907750] sd 8:0:0:0: Attached scsi generic sg10 type 0
[ 162.909876] sd 8:0:0:0: [sdj] Spinning up disk...
[ 167.320187] .ready
[ 167.322136] sd 8:0:0:0: [sdj] 3901376 4096-byte logical blocks:
(16.0 GB/14.9 GiB)
[ 167.322606] sd 8:0:0:0: [sdj] Write Protect is off
[ 167.322662] sd 8:0:0:0: [sdj] Mode Sense: 68 00 00 08
[ 167.322967] sd 8:0:0:0: [sdj] Write cache: disabled, read cache:
enabled, doesn't support DPO or FUA
[ 167.341714] sdj: sdj1
[ 167.341905] sd 8:0:0:0: [sdj] Attached SCSI removable disk
[ 1488.464220] EXT4-fs (dm-1): unmounting filesystem
43370d08-08a3-44a6-9809-7de71d91213a.
[ 1713.180844] PM: suspend entry (deep)
[ 1713.273499] Filesystems sync: 0.092 seconds
[ 1713.276483] Freezing user space processes
[ 1713.299802] Freezing user space processes completed (elapsed 0.023 seconds)
[ 1713.299847] OOM killer disabled.
[ 1713.299893] Freezing remaining freezable tasks
[ 1713.300891] Freezing remaining freezable tasks completed (elapsed
0.000 seconds)
[ 1713.300957] printk: Suspending console(s) (use no_console_suspend to debug)
[ 1713.328404] r8169 0000:02:00.0 enp2s0: Link is Down
[ 1713.328917] sd 7:0:0:0: [sdf] Synchronizing SCSI cache
[ 1713.333896] sd 2:0:0:0: [sdc] Synchronizing SCSI cache
[ 1713.333911] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
[ 1713.333913] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 1713.334139] ata1.00: Entering standby power mode
[ 1713.334373] ata3.00: Entering standby power mode
[ 1713.343045] sd 3:0:0:0: [sdd] Synchronizing SCSI cache
[ 1713.541048] ata4.00: Entering standby power mode
[ 1714.273447] ACPI: PM: Preparing to enter system sleep state S3
[ 1714.273740] ACPI: PM: Saving platform NVS memory
[ 1714.273978] Disabling non-boot CPUs ...
[ 1714.275460] smpboot: CPU 3 is now offline
[ 1714.278005] smpboot: CPU 2 is now offline
[ 1714.278085] kworker/u18:4 (76) used greatest stack depth: 11856 bytes left
[ 1714.280461] smpboot: CPU 1 is now offline
[ 1714.287892] ACPI: PM: Low-level resume complete
[ 1714.287921] ACPI: PM: Restoring platform NVS memory
[ 1714.288372] Enabling non-boot CPUs ...
[ 1714.288413] smpboot: Booting Node 0 Processor 1 APIC 0x1
[ 1714.299130] CPU1 is up
[ 1714.299159] smpboot: Booting Node 0 Processor 2 APIC 0x2
[ 1714.308608] CPU2 is up
[ 1714.308642] smpboot: Booting Node 0 Processor 3 APIC 0x3
[ 1714.317495] CPU3 is up
[ 1714.320878] ACPI: PM: Waking up from system sleep state S3
[ 1714.326900] hpet: Lost 5479 RTC interrupts
[ 1714.327867] usb usb1: root hub lost power or was reset
[ 1714.327926] usb usb4: root hub lost power or was reset
[ 1714.328019] usb usb5: root hub lost power or was reset
[ 1714.328071] usb usb6: root hub lost power or was reset
[ 1714.328122] usb usb7: root hub lost power or was reset
[ 1714.328172] usb usb8: root hub lost power or was reset
[ 1714.328305] usb usb9: root hub lost power or was reset
[ 1714.328307] usb usb10: root hub lost power or was reset
[ 1714.717925] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 1714.718977] ata5: SATA link down (SStatus 0 SControl 300)
[ 1714.767957] ata6.00: configured for UDMA/33
[ 1719.766758] ata4: link is slow to respond, please be patient (ready=0)
[ 1719.768733] ata1: link is slow to respond, please be patient (ready=0)
[ 1722.777758] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1722.778469] sd 0:0:0:0: [sda] Starting disk
[ 1722.780092] ata1.00: configured for UDMA/133
[ 1723.235745] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1725.103942] sd 3:0:0:0: [sdd] Starting disk
[ 1725.107308] ata4.00: configured for UDMA/133
[ 1735.329691] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
[ 1735.329695] rcu: 3-...0: (1 GPs behind)
idle=ce4c/1/0x4000000000000000 softirq=63254/63255 fqs=5249
[ 1735.329701] rcu: (detected by 0, t=21002 jiffies, g=47065, q=31 ncpus=4)
[ 1735.329705] Sending NMI from CPU 0 to CPUs 3:
[ 1735.329711] NMI backtrace for cpu 3
[ 1735.329716] CPU: 3 UID: 0 PID: 1075 Comm: kworker/u18:0 Tainted: G
S 7.0.3 #6 PREEMPT(full)
[ 1735.329720] Tainted: [S]=CPU_OUT_OF_SPEC
[ 1735.329721] Hardware name: HP-Pavilion FJ422AA-UUW
a6551.sc/Benicia, BIOS 5.32 10/23/2008
[ 1735.329723] Workqueue: async async_run_entry_fn
[ 1735.329730] RIP: 0010:xhci_handshake+0x51/0xc0
[ 1735.329735] Code: fa 8b 07 89 f1 49 89 fe 41 89 f5 21 c1 41 39 cc
75 22 eb 3c f3 90 48 81 eb e9 03 00 00 48 89 da 48 c1 ea 3f 44 21 fa
41 8b 06 <44> 89 e9 21 c1 44 39 e1 74 1c 83 f8 ff 74 2d 84 d2 75 3d bf
c7 10
[ 1735.329737] RSP: 0000:ffff9fef00c3bd18 EFLAGS: 00000046
[ 1735.329739] RAX: 0000000000000002 RBX: 0000000093f583f3 RCX: 0000000000000002
[ 1735.329741] RDX: 0000000000000000 RSI: 0000000000000003 RDI: 0000000bf6319f3f
[ 1735.329742] RBP: 0000000000989680 R08: 0000000000000960 R09: 0000000000000003
[ 1735.329744] R10: 00000000ffffe000 R11: 0000000000000000 R12: 0000000000000000
[ 1735.329745] R13: 0000000000000002 R14: ffff9fef0043a020 R15: 0000000000000001
[ 1735.329746] FS: 0000000000000000(0000) GS:ffff968d5d1c5000(0000)
knlGS:0000000000000000
[ 1735.329748] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 1735.329750] CR2: 0000000000000000 CR3: 000000007f644000 CR4: 00000000000026f0
[ 1735.329751] Call Trace:
[ 1735.329754] <TASK>
[ 1735.329756] xhci_reset+0x65/0x110
[ 1735.329759] xhci_resume+0x146/0x710
[ 1735.329762] resume_common+0x8b/0x110
[ 1735.329766] ? __pfx_pci_pm_resume+0x10/0x10
[ 1735.329769] dpm_run_callback+0x4b/0x170
[ 1735.329772] device_resume+0x158/0x250
[ 1735.329775] async_resume+0x14/0x20
[ 1735.329777] async_run_entry_fn+0x29/0x130
[ 1735.329781] process_one_work+0x163/0x370
[ 1735.329785] worker_thread+0x18f/0x300
[ 1735.329788] ? __pfx_worker_thread+0x10/0x10
[ 1735.329790] kthread+0xda/0x110
[ 1735.329794] ? __pfx_kthread+0x10/0x10
[ 1735.329797] ret_from_fork+0x1af/0x2b0
[ 1735.329801] ? __pfx_kthread+0x10/0x10
[ 1735.329804] ret_from_fork_asm+0x1a/0x30
[ 1735.329809] </TASK>
[ 1735.769691] rcu: INFO: rcu_preempt detected expedited stalls on
CPUs/tasks: { 3-...D } 21383 jiffies s: 401 root: 0x8/.
[ 1735.769699] rcu: blocking rcu_node structures (internal RCU debug):
[ 1735.769700] Sending NMI from CPU 1 to CPUs 3:
[ 1735.769704] NMI backtrace for cpu 3
[ 1735.769706] CPU: 3 UID: 0 PID: 1075 Comm: kworker/u18:0 Tainted: G
S 7.0.3 #6 PREEMPT(full)
[ 1735.769709] Tainted: [S]=CPU_OUT_OF_SPEC
[ 1735.769710] Hardware name: HP-Pavilion FJ422AA-UUW
a6551.sc/Benicia, BIOS 5.32 10/23/2008
[ 1735.769711] Workqueue: async async_run_entry_fn
[ 1735.769715] RIP: 0010:xhci_handshake+0x51/0xc0
[ 1735.769717] Code: fa 8b 07 89 f1 49 89 fe 41 89 f5 21 c1 41 39 cc
75 22 eb 3c f3 90 48 81 eb e9 03 00 00 48 89 da 48 c1 ea 3f 44 21 fa
41 8b 06 <44> 89 e9 21 c1 44 39 e1 74 1c 83 f8 ff 74 2d 84 d2 75 3d bf
c7 10
[ 1735.769719] RSP: 0000:ffff9fef00c3bd18 EFLAGS: 00000046
[ 1735.769721] RAX: 0000000000000002 RBX: 000000008a928e70 RCX: 0000000000000002
[ 1735.769722] RDX: 0000000000000000 RSI: 0000000000000003 RDI: 0000000c352263c9
[ 1735.769724] RBP: 0000000000989680 R08: 0000000000000960 R09: 0000000000000003
[ 1735.769725] R10: 00000000ffffe000 R11: 0000000000000000 R12: 0000000000000000
[ 1735.769726] R13: 0000000000000002 R14: ffff9fef0043a020 R15: 0000000000000001
[ 1735.769728] FS: 0000000000000000(0000) GS:ffff968d5d1c5000(0000)
knlGS:0000000000000000
[ 1735.769729] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 1735.769731] CR2: 0000000000000000 CR3: 000000007f644000 CR4: 00000000000026f0
[ 1735.769732] Call Trace:
[ 1735.769733] <TASK>
[ 1735.769734] xhci_reset+0x65/0x110
[ 1735.769737] xhci_resume+0x146/0x710
[ 1735.769739] resume_common+0x8b/0x110
[ 1735.769742] ? __pfx_pci_pm_resume+0x10/0x10
[ 1735.769744] dpm_run_callback+0x4b/0x170
[ 1735.769747] device_resume+0x158/0x250
[ 1735.769749] async_resume+0x14/0x20
[ 1735.769752] async_run_entry_fn+0x29/0x130
[ 1735.769755] process_one_work+0x163/0x370
[ 1735.769758] worker_thread+0x18f/0x300
[ 1735.769761] ? __pfx_worker_thread+0x10/0x10
[ 1735.769763] kthread+0xda/0x110
[ 1735.769766] ? __pfx_kthread+0x10/0x10
[ 1735.769770] ret_from_fork+0x1af/0x2b0
[ 1735.769772] ? __pfx_kthread+0x10/0x10
[ 1735.769775] ret_from_fork_asm+0x1a/0x30
[ 1735.769779] </TASK>
[ 1742.263962] clocksource: Long readout interval, skipping watchdog
check: cs_nsec: 26631211515 wd_nsec: 26631203940
[ 1742.264015] xhci-pci-renesas 0000:03:00.0: PCI post-resume error -110!
[ 1742.264018] xhci-pci-renesas 0000:03:00.0: HC died; cleaning up
[ 1742.264059] xhci-pci-renesas 0000:03:00.0: PM: dpm_run_callback():
pci_pm_resume returns -110
[ 1742.264064] xhci-pci-renesas 0000:03:00.0: PM: failed to resume
async: error -110
[ 1742.266288] r8169 0000:02:00.0 enp2s0: Link is Down
[ 1742.303296] OOM killer enabled.
[ 1742.303337] Restarting tasks: Starting
[ 1742.303541] usb 9-4: USB disconnect, device number 2
[ 1742.303813] Restarting tasks: Done
[ 1742.303874] random: crng reseeded on system resumption
[ 1742.304744] PM: suspend exit
[ 1742.574174] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> FYI, the quirk performs full xHCI reset during resume and prevents
> selectively suspending the chip when all its USB devices are suspended
> but the system is running (not going to sleep). It doesn't prevent
> suspending when no USB devices are connected at all. And either way,
> runtime PM may be turned off, see if this is 'on' or 'auto':
>
> cat /sys/bus/pci/devices/0000:03:00.0/power/control
>
# cat /sys/bus/pci/devices/0000:03:00.0/power/control
on
> I have no idea why it works the first time but not the second.
> Not what happens if the same is done without the quirk?
> Maybe try s2idle ("freeze") instead of S3 sleep? But that doesn't
> provide the same power saving on older HW.
>
I''l give that a go.
Thanks!
Anders
> Regards,
> Michal
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2026-05-26 19:12 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-05-06 12:58 renesas 1912:0014 failures Anders Thomson
2026-05-12 10:27 ` Michal Pecio
2026-05-12 14:40 ` Anders Thomson
2026-05-12 17:02 ` Michal Pecio
2026-05-12 22:34 ` Anders Thomson
2026-05-18 6:46 ` Michal Pecio
2026-05-18 8:41 ` Anders Thomson
2026-05-18 12:36 ` Anders Thomson
2026-05-23 16:32 ` Michal Pecio
2026-05-26 19:12 ` Anders Thomson
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox