Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: "Mario Limonciello (AMD) (kernel.org)" <superm1@kernel.org>
Cc: "Adrià Vilanova Martínez" <me@avm99963.com>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	regressions@lists.linux.dev, linux-pci@vger.kernel.org,
	"Lukas Wunner" <lukas@wunner.de>
Subject: Re: [REGRESSION] Intel Wireless adapter is not detected until suspending to RAM and resuming
Date: Mon, 20 Oct 2025 18:25:10 -0500	[thread overview]
Message-ID: <20251020232510.GA1167305@bhelgaas> (raw)
In-Reply-To: <149b04c5-23d3-4fd8-9724-5b955b645fbb@kernel.org>

[+cc Lukas, beginning of thread with complete dmesg log:
https://lore.kernel.org/r/owewi3sswao4jt5qn3ntm533lvxe3jlovhjbdufq3uedbuztxt@76nft22vboxv]

On Mon, Oct 20, 2025 at 11:37:43AM -0500, Mario Limonciello (AMD) (kernel.org) wrote:
> On 10/20/2025 7:56 AM, Adrià Vilanova Martínez wrote:
> > On Sun, Oct 19, 2025 at 07:25:08PM -0500, Mario Limonciello wrote:
> > > Thanks, knowing that pcie_aspm=off helps I think we should compare output
> > > for:
> > > 
> > > # sudo lspci -vvnn
> > 
> > Sure, I'm attaching the outputs of this command for all the scenarios.
> > There are some differences, so it seems promising.
> 
> Surprisingly there is nothing different about ASPM though.  It's all PCI-PM
> differences.
> 
> Looking at your log again I noticed this from the bridge:
> 
> pcieport 0000:00:1c.0: pciehp: Slot(0): Card not present
> pcieport 0000:00:1c.0: pciehp: Slot(0): Card present
> pcieport 0000:00:1c.0: pciehp: Slot(0): Link Up
> ...
> pcieport 0000:00:1c.0: pciehp: Slot(0): No device found
> ...
> (suspend)
> ...
> pcieport 0000:00:1c.0: pciehp: Slot(0): Card present
> pcieport 0000:00:1c.0: pciehp: Slot(0): Link Up

This seems wrong.  The PCI core definitely enumerated the wifi device,
but it seems like there's some pciehp confusion about presence/link
up/etc, and we couldn't actually use it until after the
suspend/resume:

  [    0.113379] pci 0000:00:1c.0: [8086:9d10] type 01 class 0x060400 PCIe Root Port
  [    0.113403] pci 0000:00:1c.0: PCI bridge to [bus 01]
  [    0.113409] pci 0000:00:1c.0:   bridge window [mem 0x91000000-0x910fffff]
  [    0.115692] pci 0000:01:00.0: [8086:095a] type 00 class 0x028000 PCIe Endpoint
  [    0.115830] pci 0000:01:00.0: BAR 0 [mem 0x91000000-0x91001fff 64bit]
  [    0.196539] pcieport 0000:00:1c.0: pciehp: Slot #0 AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Interlock- NoCompl+ IbPresDis- LLActRep+
  [    0.196802] pcieport 0000:00:1c.0: pciehp: Slot(0): Card not present
  [    0.196925] pcieport 0000:00:1c.0: pciehp: Slot(0): Card present
  [    0.196927] pcieport 0000:00:1c.0: pciehp: Slot(0): Link Up
  [    1.400127] pcieport 0000:00:1c.0: pciehp: Slot(0): No device found
  [   50.295404] ACPI: PM: Preparing to enter system sleep state S3

  [   50.314754] ACPI: PM: Waking up from system sleep state S3
  [   50.328910] pcieport 0000:00:1c.0: pciehp: Slot(0): Card present
  [   50.328914] pcieport 0000:00:1c.0: pciehp: Slot(0): Link Up
  [   50.454011] pci 0000:01:00.0: [8086:095a] type 00 class 0x028000 PCIe Endpoint
  [   50.454135] pci 0000:01:00.0: BAR 0 [mem 0x91000000-0x91001fff 64bit]
  [   50.833621] iwlwifi 0000:01:00.0: Detected crf-id 0x0, cnv-id 0x0 wfpm id 0x0
  [   50.833632] iwlwifi 0000:01:00.0: PCI dev 095a/9e10, rev=0x210, rfid=0xd55555d5
  [   50.833636] iwlwifi 0000:01:00.0: Detected Intel(R) Dual Band Wireless-AC 7265

I don't have any good ideas.

Bjorn

  parent reply	other threads:[~2025-10-20 23:25 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-18 22:01 [REGRESSION] Intel Wireless adapter is not detected until suspending to RAM and resuming Adrià Vilanova Martínez
2025-10-19  5:12 ` Mario Limonciello
2025-10-19  9:35   ` Adrià Vilanova Martínez
2025-10-19 11:37     ` Adrià Vilanova Martínez
2025-10-19 18:22       ` Mario Limonciello
2025-10-19 23:08         ` Adrià Vilanova Martínez
2025-10-20  0:25           ` Mario Limonciello
2025-10-20 12:56             ` Adrià Vilanova Martínez
2025-10-20 16:37               ` Mario Limonciello (AMD) (kernel.org)
2025-10-20 17:38                 ` Mario Limonciello (AMD) (kernel.org)
2025-10-20 22:33                   ` Adrià Vilanova Martínez
2025-10-20 23:25                 ` Bjorn Helgaas [this message]
2025-10-21  7:37                   ` Lukas Wunner
2025-10-21  8:30                     ` Lukas Wunner
2025-10-21 13:35                     ` Adrià Vilanova Martínez
2025-10-22 15:30                       ` Lukas Wunner
2025-10-22 16:19                         ` Lukas Wunner
2025-10-27 16:36                           ` Adrià Vilanova Martínez
2025-10-28 14:30                             ` Adrià Vilanova Martínez
2025-10-27 15:49                         ` Adrià Vilanova Martínez

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=20251020232510.GA1167305@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=me@avm99963.com \
    --cc=regressions@lists.linux.dev \
    --cc=superm1@kernel.org \
    /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