linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: regressions@lists.linux.dev
Cc: linux-pci@vger.kernel.org
Subject: Re: [REGRESSION] [Bug 216859] New: PCI bridge to bus boot hang at enumeration
Date: Wed, 1 Feb 2023 17:27:50 -0600	[thread overview]
Message-ID: <20230201232750.GA1908996@bhelgaas> (raw)
In-Reply-To: <20230126121124.GA1258686@bhelgaas>

On Thu, Jan 26, 2023 at 06:11:24AM -0600, Bjorn Helgaas wrote:
> [+cc folks from 145eed48de27 and framebuffer folks, regression list]
> 
> On Thu, Jan 12, 2023 at 02:08:19PM -0600, Bjorn Helgaas wrote:
> > 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
> 
> This is a regression between v6.0 and v6.1-rc1.  Console output during
> boot freezes after nvidiafb deactivates the VGA console.
> 
> It was a lot of work for Zeno, but we finally isolated this console
> hang to 145eed48de27 ("fbdev: Remove conflicting devices on PCI bus").
> 
> The system actually does continue to boot and is accessible via ssh, 
> but the console appears hung, at least for output.  More details in
> the bugzilla starting at
> https://bugzilla.kernel.org/show_bug.cgi?id=216859#c47 .

#regzbot introduced: 145eed48de27
#regzbot dup: https://lore.kernel.org/all/D41A3A42-2412-4722-9090-01565058E525@gmail.com/

  parent reply	other threads:[~2023-02-01 23:27 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
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 [this message]
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=20230201232750.GA1908996@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    /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).