From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Bert Karwatzki <spasswolf@web.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: commit c2fe0480cd77 leads to hang on boot
Date: Fri, 30 Aug 2024 07:22:22 +0200 [thread overview]
Message-ID: <717c608b-6280-45fd-bb88-eeb862a893e3@t-8ch.de> (raw)
In-Reply-To: <20240829230438.3226-1-spasswolf@web.de>
Hi Bert,
thanks for the report.
On 2024-08-30 01:04:37+0000, Bert Karwatzki wrote:
> To look into the issue I applied the following patch to next-20240829:
>
> diff --git a/drivers/video/fbdev/efifb.c b/drivers/video/fbdev/efifb.c
> index 20517448487e..ba2b0d4b1bd3 100644
> --- a/drivers/video/fbdev/efifb.c
> +++ b/drivers/video/fbdev/efifb.c
> @@ -573,6 +573,8 @@ static int efifb_probe(struct platform_device *dev)
> pr_err("efifb: cannot acquire aperture\n");
> goto err_fb_dealloc_cmap;
> }
> + printk(KERN_INFO "%s: not calling devm_register_framebuffer\n", __func__);
> + goto err_fb_dealloc_cmap;
> err = devm_register_framebuffer(&dev->dev, info);
> if (err < 0) {
> pr_err("efifb: cannot register framebuffer\n");
>
> Now booting works again so the problem seems to be in devm_register_framebuffer().
What happens if you replace devm_register_framebuffer() with a plain
register_framebuffer() again?
Thomas
next prev parent reply other threads:[~2024-08-30 5:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 23:04 Bert Karwatzki
2024-08-30 5:22 ` Thomas Weißschuh [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-30 12:34 Bert Karwatzki
2024-08-30 12:37 ` Bert Karwatzki
2024-08-29 22:41 Bert Karwatzki
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=717c608b-6280-45fd-bb88-eeb862a893e3@t-8ch.de \
--to=linux@weissschuh.net \
--cc=linux-kernel@vger.kernel.org \
--cc=spasswolf@web.de \
/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
all inboxes | Powered by JetHome®