From: Randy Dunlap <rdunlap@infradead.org>
To: Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
Kees Cook <keescook@chromium.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Arnd Bergmann <arnd@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
John Youn <John.Youn@synopsys.com>,
Bing Yuan <Bing.Yuan@synopsys.com>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: Kconfig CONFIG_FB dependency regression
Date: Tue, 1 Feb 2022 15:06:04 -0800 [thread overview]
Message-ID: <9bab4777-3034-b789-fdf6-ca8d7e6a8c35@infradead.org> (raw)
In-Reply-To: <6fc4a81f-1a13-bff9-7b2e-d5bec382cb42@synopsys.com>
On 2/1/22 15:01, Thinh Nguyen wrote:
> Hi,
>
> One of our test setups is unable to boot (stuck at initramfs). Git
> bisection points to the commit below:
>
> f611b1e7624c ("drm: Avoid circular dependencies for CONFIG_FB")
>
> Reverting this patch resolves the issue. This issue persists in mainline
> also. Unfortunately there isn't any meaningful log. Hopefully someone
> can give some insight as to what could be the issue and revert/fix this
> issue.
Hi,
Did you enable DRM_FBDEV_EMULATION?
Please provide the failing .config file.
--
~Randy
next prev parent reply other threads:[~2022-02-01 23:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 23:01 Kconfig CONFIG_FB dependency regression Thinh Nguyen
2022-02-01 23:06 ` Randy Dunlap [this message]
2022-02-01 23:59 ` Fabio Estevam
2022-02-02 0:14 ` Thinh Nguyen
2022-02-02 7:46 ` Arnd Bergmann
2022-02-02 23:55 ` Thinh Nguyen
2022-02-03 3:15 ` Randy Dunlap
2022-02-03 4:23 ` Thinh Nguyen
2022-02-03 7:18 ` Arnd Bergmann
2022-02-04 3:21 ` Thinh Nguyen
2022-02-04 4:02 ` Randy Dunlap
2022-02-08 20:10 ` Thinh Nguyen
2022-02-08 20:45 ` Randy Dunlap
2022-02-08 22:42 ` Thinh Nguyen
2022-02-09 7:06 ` Arnd Bergmann
2022-02-15 2:52 ` Thinh Nguyen
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=9bab4777-3034-b789-fdf6-ca8d7e6a8c35@infradead.org \
--to=rdunlap@infradead.org \
--cc=Bing.Yuan@synopsys.com \
--cc=John.Youn@synopsys.com \
--cc=Thinh.Nguyen@synopsys.com \
--cc=arnd@kernel.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.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 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).