linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Zeno Davatz <zdavatz@gmail.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Bruno Moreira-Guedes" <brunodout.dev@gmail.com>,
	"Krzysztof Wilczyński" <kw@linux.com>
Subject: Re: [Bug 216859] New: PCI bridge to bus boot hang at enumeration
Date: Wed, 18 Jan 2023 18:04:58 -0600	[thread overview]
Message-ID: <20230119000458.GA275446@bhelgaas> (raw)
In-Reply-To: <CAOkhzLW+1z58681zBV7LT=Lw=tcT9EgVPEbKx8YGsa+EJyxUSw@mail.gmail.com>

[+cc Krzysztof]

On Fri, Jan 06, 2023 at 05:42:33PM +0100, Zeno Davatz wrote:
> On Fri, Dec 30, 2022 at 7:50 PM Bjorn Helgaas <helgaas@kernel.org> wrote:
> > On Wed, Dec 28, 2022 at 12:42:34PM -0600, Bjorn Helgaas wrote:
> > > On Wed, Dec 28, 2022 at 06:42:38PM +0100, Zeno Davatz wrote:
> > > > On Wed, Dec 28, 2022 at 1:02 PM Bjorn Helgaas <helgaas@kernel.org> 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?
> > > >
> > > > I will try this after Januar 7th 2023.
> 
> I updated the issue:
> 
> https://bugzilla.kernel.org/show_bug.cgi?id=216859
> 
> I booted with the option: "ignore_loglevel initcall_debug"

Thanks!  There's so much pcie output in that picture that we can't see
any of the initcall logging.  Can you capture another movie, but use
kernel parameters like "ignore_loglevel initcall_debug boot_delay=100"
to slow things down?  The full-speed boot is too fast for the camera
to capture all the output.  You can do this on any convenient kernel
that hangs.

There might be more we can do with the bisection, too, but I don't
have any suggestions for that yet.  Maybe Krzysztof does.

Bjorn

  reply	other threads:[~2023-01-19  0:05 UTC|newest]

Thread overview: 14+ 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 [this message]
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
2023-02-01 23:27       ` Bjorn Helgaas
2023-02-13 20:47         ` 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=20230119000458.GA275446@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=brunodout.dev@gmail.com \
    --cc=kw@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --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).