From: Thorsten Leemhuis <regressions@leemhuis.info>
To: torvic9@mailbox.org, Linus Torvalds <torvalds@linux-foundation.org>
Cc: "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: Thu, 7 Jul 2022 10:22:19 +0200 [thread overview]
Message-ID: <40f45d61-2e3a-eef1-d31a-ca41f40cacfd@leemhuis.info> (raw)
In-Reply-To: <830109073.51279.1657180466311@office.mailbox.org>
On 07.07.22 09:54, torvic9@mailbox.org wrote:
>> Linus Torvalds <torvalds@linux-foundation.org> hat am 06.07.2022 18:59 GMT geschrieben:
>> 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.
>>
>
> I confirm that applying
> "drm/aperture: Run fbdev removal before internal helpers"
> on top of rc5 solves this issue, computer boots normally again.
> I suppose this commit will be cherry-picked for rc6.
Thx for confirming. Yes, that patch is in the drm-misc-fixes tree as
bf43e4521ff3 and thus will likely be merged with this weeks DRM merge.
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.
next prev parent reply other threads:[~2022-07-07 8:22 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
2022-07-07 7:54 ` torvic9
2022-07-07 8:22 ` Thorsten Leemhuis [this message]
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=40f45d61-2e3a-eef1-d31a-ca41f40cacfd@leemhuis.info \
--to=regressions@leemhuis.info \
--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=torvalds@linux-foundation.org \
--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.