public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Phillip Susi <phill@thesusis.net>
To: linux-kernel@vger.kernel.org
Cc: Niklas Neronin <niklas.neronin@linux.intel.com>,
	Mathias Nyman <mathias.nyman@linux.intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Suspend regression in v6.18-rc1
Date: Tue, 14 Oct 2025 21:22:53 -0400	[thread overview]
Message-ID: <871pn5j6vm.fsf@vps.thesusis.net> (raw)

I have a suspend regression in v6.18-rc1 that results in this in my
dmesg when I try to suspend:

[   36.739259] Freezing remaining freezable tasks
[   36.740378] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
[   36.740414] printk: Suspending console(s) (use no_console_suspend to debug)
[   36.783363] xhci_hcd 0000:51:00.0: Root hub is not suspended
[   36.783366] xhci_hcd 0000:51:00.0: PM: pci_pm_suspend(): hcd_pci_suspend [usbcore] returns -16
[   36.783378] xhci_hcd 0000:51:00.0: PM: dpm_run_callback(): pci_pm_suspend returns -16
[   36.783383] xhci_hcd 0000:51:00.0: PM: failed to suspend async: error
-16

I have bisected it to this commit:

commit 719de070f764e079cdcb4ddeeb5b19b3ddddf9c1 (HEAD)
Author: Niklas Neronin <niklas.neronin@linux.intel.com>
Date:   Thu Sep 18 00:07:22 2025 +0300

    usb: xhci-pci: add support for hosts with zero USB3 ports
    
    Add xhci support for PCI hosts that have zero USB3 ports.
    Avoid creating a shared Host Controller Driver (HCD) when there is only
    one root hub. Additionally, all references to 'xhci->shared_hcd' are now
    checked before use.
    
    Only xhci-pci.c requires modification to accommodate this change, as the
    xhci core already supports configurations with zero USB3 ports. This
    capability was introduced when xHCI Platform and MediaTek added support
    for zero USB3 ports.
    
    Closes: https://bugzilla.kernel.org/show_bug.cgi?id=220181
    Tested-by: Nick Nielsen <nick.kainielsen@free.fr>
    Tested-by: grm1 <grm1@mailbox.org>
    Signed-off-by: Niklas Neronin <niklas.neronin@linux.intel.com>
    Signed-off-by: Mathias Nyman <mathias.nyman@linux.intel.com>
    Link: https://lore.kernel.org/r/20250917210726.97100-4-mathias.nyman@linux.intel.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

It sounds like it may be related to these errors that I have had on this
system since I built it last year:

Oct 14 20:55:36 faldara kernel: hub 10-0:1.0: USB hub found
Oct 14 20:55:36 faldara kernel: hub 10-0:1.0: config failed, hub doesn't
have any ports! (err -19)

I believe this system has a usb hub with "zero ports" that this patch
was meant to fix, but up until now, has only resulted in this beign
dmesg error.  I no longer see this error after this commit.

This is an ASrock 650E Taichi Lite motherboard I built last year.

What additional information can I provide?

             reply	other threads:[~2025-10-15  1:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-15  1:22 Phillip Susi [this message]
2025-10-15  5:45 ` Suspend regression in v6.18-rc1 Neronin, Niklas
2025-10-15 20:36   ` Phillip Susi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871pn5j6vm.fsf@vps.thesusis.net \
    --to=phill@thesusis.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathias.nyman@linux.intel.com \
    --cc=niklas.neronin@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox