From: Zeno Davatz <zdavatz@gmail.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Bug 216859] New: PCI bridge to bus boot hang at enumeration
Date: Wed, 28 Dec 2022 18:42:38 +0100 [thread overview]
Message-ID: <CAOkhzLXr_+oydSFVm+LdwzCU+qZ_A=m4dcV+r=Uf-OjQnNdJqA@mail.gmail.com> (raw)
In-Reply-To: <20221228120248.GA508080@bhelgaas>
Dear Bjorn
On Wed, Dec 28, 2022 at 1:02 PM Bjorn Helgaas <helgaas@kernel.org> wrote:
>
> [+cc linux-pci, linux-kernel]
>
> 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?
I will try this after Januar 7th 2023.
> 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.
I did not really conclude that. I just saw "PCI" as one of the last
messages being outputted before the boot process stopped.
Best
Zeno
next prev parent reply other threads:[~2022-12-28 17:42 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 [this message]
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
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='CAOkhzLXr_+oydSFVm+LdwzCU+qZ_A=m4dcV+r=Uf-OjQnNdJqA@mail.gmail.com' \
--to=zdavatz@gmail.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.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;
as well as URLs for NNTP newsgroup(s).