All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Filippe Duke <fduke@greennet.ua>
Cc: "regressions@lists.linux.dev" <regressions@lists.linux.dev>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"bhelgaas@google.com" <bhelgaas@google.com>,
	"superm1@kernel.org" <superm1@kernel.org>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"tiwai@suse.com" <tiwai@suse.com>
Subject: Re: [REGRESSION][BISECTED] HDA controller MMIO unreadable on Intel 5-series PCH (Ibex Peak) since v6.16
Date: Mon, 1 Jun 2026 09:34:03 +0200	[thread overview]
Message-ID: <ah016_TukXkcqnyQ@wunner.de> (raw)
In-Reply-To: <60c710e22fc987a3b444e5b687a9a64bb454f0f8.camel@greennet.ua>

On Sun, May 31, 2026 at 09:22:52PM +0000, Filippe Duke wrote:
> A working LTS kernel version tells completely different story.

Right:

 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset
[...]
-       Interrupts: pin B disabled, MSI(X) routed to IRQ 34
+       Interrupts: pin B disabled, MSI(X) routed to IRQ 28
[...]
-               Address: 0000000000000000  Data: 0000
+               Address: 00000000fee00000  Data: 0022

That's the only difference.  Seems plausible that it causes
communication failure with the HDA controller.

The offending commit causes current_state to be PCI_D0 instead of
PCI_UNKNOWN at boot time enumeration and this results in different
code paths being taken.

I note that current_state is queried in three places in
drivers/pci/msi/msi.c, so I'd start by instrumenting them with
printk()'s to see why the behavior is different.

E.g. __pci_write_msi_msg() bails out if current_state is not PCI_D0.
Perhaps it used to do that on a working kernel and now it doesn't.

Thanks,

Lukas

  reply	other threads:[~2026-06-01  7:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-29 18:26 [REGRESSION][BISECTED] HDA controller MMIO unreadable on Intel 5-series PCH (Ibex Peak) since v6.16 Filippe Duke
2026-05-31 13:21 ` Mario Limonciello
2026-05-31 19:49   ` Filippe Duke
2026-05-31 20:48     ` Lukas Wunner
2026-05-31 21:22       ` Filippe Duke
2026-06-01  7:34         ` Lukas Wunner [this message]
2026-06-16  8:12           ` Thorsten Leemhuis
2026-06-16  8:24             ` Filippe Duke

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=ah016_TukXkcqnyQ@wunner.de \
    --to=lukas@wunner.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=bhelgaas@google.com \
    --cc=fduke@greennet.ua \
    --cc=linux-pci@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=superm1@kernel.org \
    --cc=tiwai@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.