From: Bjorn Helgaas <helgaas@kernel.org>
To: "Zeno R.R. Davatz" <zdavatz@gmail.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Takashi Iwai <tiwai@suse.de>, Jaroslav Kysela <perex@perex.cz>,
alsa-devel@alsa-project.org
Subject: Re: [Bug 216859] New: PCI bridge to bus boot hang at enumeration
Date: Thu, 12 Jan 2023 14:08:19 -0600 [thread overview]
Message-ID: <20230112200819.GA1785077@bhelgaas> (raw)
In-Reply-To: <20221228120248.GA508080@bhelgaas>
[+cc sound folks]
On Wed, Dec 28, 2022 at 06:02:48AM -0600, Bjorn Helgaas wrote:
> On Wed, Dec 28, 2022 at 08:37:52AM +0000, bugzilla-daemon@kernel.org wrote:
> > https://bugzilla.kernel.org/show_bug.cgi?id=216859
>
> > Summary: PCI bridge to bus boot hang at enumeration
> > Kernel Version: 6.1-rc1
> > ...
>
> > With Kernel 6.1-rc1 the enumeration process stopped working for me,
> > see attachments.
> >
> > The enumeration works fine with Kernel 6.0 and below.
> >
> > Same problem still exists with v6.1. and v6.2.-rc1
>
> Thank you very much for your report, Zeno!
>
> v6.0 works, v6.1-rc1 fails. Would you mind booting v6.1-rc1 with the
> "ignore_loglevel initcall_debug" kernel parameters and taking a photo
> when it hangs?
>
> How did you conclude that the hang is related to a PCI bridge? I see
> recent PCI messages in the photo, but it looks like the last message
> is from NFS, so I'm wondering if I'm missing some context. The v6.0
> dmesg shows several other ntfs, fuse, JFS, etc messages before more
> PCI-related things. Anyway, the "initcall_debug" might help us narrow
> it down a bit.
Thanks very much for the bisection (complete log at [1])!
The bisection claims the first bad commit is:
833477fce7a1 ("Merge tag 'sound-6.1-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound")
with parents:
7e6739b9336e ("Merge tag 'drm-next-2022-10-05' of git://anongit.freedesktop.org/drm/drm")
86a4d29e7554 ("Merge tag 'asoc-v6.1' of https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-linus")
Both 7e6739b9336e and 86a4d29e7554 tested "good" during the bisection.
There is a minor conflict when merging 86a4d29e7554 into the upstream,
but I can't imagine that being resolved incorrectly.
Would you mind turning off CONFIG_SOUND in your .config and testing
833477fce7a1 again? I'm a little skeptical that the hang would be
sound-related, but I guess it's a place to start.
Bjorn
[1] https://bugzilla.kernel.org/show_bug.cgi?id=216859#c35
next prev parent reply other threads:[~2023-01-12 20:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-216859-41252@https.bugzilla.kernel.org/>
2022-12-28 12:02 ` [Bug 216859] New: PCI bridge to bus boot hang at enumeration Bjorn Helgaas
2022-12-28 17:42 ` Zeno Davatz
2022-12-28 18:42 ` Bjorn Helgaas
2022-12-30 18:50 ` Bjorn Helgaas
2023-01-06 16:42 ` Zeno Davatz
2023-01-19 0:04 ` Bjorn Helgaas
2023-01-19 17:00 ` Bjorn Helgaas
2023-01-19 17:36 ` Zeno Davatz
2023-01-12 20:08 ` Bjorn Helgaas [this message]
2023-01-13 10:18 ` Zeno Davatz
2023-01-26 12:11 ` [REGRESSION] " Bjorn Helgaas
2023-02-01 22:30 ` Bjorn Helgaas
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=20230112200819.GA1785077@bhelgaas \
--to=helgaas@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
--cc=zdavatz@gmail.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;
as well as URLs for NNTP newsgroup(s).