All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Tor Vic <torvic9@mailbox.org>,
	"Limonciello, Mario" <Mario.Limonciello@amd.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"platform-driver-x86@vger.kernel.org" 
	<platform-driver-x86@vger.kernel.org>,
	Hans de Goede <hdegoede@redhat.com>,
	Jani Nikula <jani.nikula@intel.com>
Subject: Re: [Regression?] Linux 5.19-rc5 gets stuck on boot, not rc4
Date: Wed, 6 Jul 2022 11:59:03 -0700	[thread overview]
Message-ID: <CAHk-=whfSg1FNFJXv9QfXXnWFO71YufsoTs9S8sYzonfwjm4XA@mail.gmail.com> (raw)
In-Reply-To: <8ee1bc75-3ecd-9d87-b7cc-37ba15133026@leemhuis.info>

On Wed, Jul 6, 2022 at 11:21 AM Thorsten Leemhuis
<regressions@leemhuis.info> wrote:
>
> Wild guess, I'm not involved at all in any of the following, I just
> noticed it and thought it might be worth mentioning:
>
> I heard Fedora rawhide added this patch to solve a boot problem that
> sounded similar to yours:
> https://patchwork.freedesktop.org/patch/489982/

Yes, this looks likely, and matches that "starts in 5.19-rc5" since
the offending commit came in as

  ee7a69aa38d8 ("fbdev: Disable sysfb device registration when
removing conflicting FBs")

so that does look like a likely cause.

              Linus

  parent reply	other threads:[~2022-07-06 18:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-05 13:50 [Regression?] Linux 5.19-rc5 gets stuck on boot, not rc4 torvic9
2022-07-05 16:39 ` Linus Torvalds
2022-07-05 17:10   ` Limonciello, Mario
2022-07-06  8:42     ` torvic9
2022-07-06 18:21       ` Thorsten Leemhuis
2022-07-06 18:56         ` Tor Vic
2022-07-06 18:59         ` Linus Torvalds [this message]
2022-07-07  7:54           ` torvic9
2022-07-07  8:22             ` Thorsten Leemhuis
2022-07-06 11:50     ` torvic9
2022-07-07  8:20 ` Thorsten Leemhuis

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='CAHk-=whfSg1FNFJXv9QfXXnWFO71YufsoTs9S8sYzonfwjm4XA@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=Mario.Limonciello@amd.com \
    --cc=hdegoede@redhat.com \
    --cc=jani.nikula@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=regressions@leemhuis.info \
    --cc=torvic9@mailbox.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 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.