All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@kernel.org>
To: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Cc: Fabio Estevam <festevam@gmail.com>,
	Randy Dunlap <rdunlap@infradead.org>,
	Kees Cook <keescook@chromium.org>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	"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: Wed, 2 Feb 2022 08:46:00 +0100	[thread overview]
Message-ID: <CAK8P3a3ELrSC=KX6cr8UnP6kkJN0AXeAE4EG4oUY=Zz7gG_dgg@mail.gmail.com> (raw)
In-Reply-To: <d8981e2a-4f61-72bb-e5cc-bf4ded29c08a@synopsys.com>

On Wed, Feb 2, 2022 at 1:14 AM Thinh Nguyen <Thinh.Nguyen@synopsys.com> wrote:
> Fabio Estevam wrote:
> > On Tue, Feb 1, 2022 at 8:06 PM Randy Dunlap <rdunlap@infradead.org> wrote:
> >>
> >> 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?
>
> I did not enable it.
>
> >> Please provide the failing .config file.
> >
> > Does selecting CONFIG_FB=y help?
> >
>
> On the config that has the issue, this isn't set. After reverting the
> commit above, this was set. Maybe this is what's needed? I need to test it.

CONFIG_FB should not normally be needed for booting, so unless
you have a graphical application in your initramfs that requires the /dev/fb0
device to work, it is not supposed to make a difference.

Are there any other differences in your .config before and after the patch?
It's possible that you use some other driver that in turn depends on
CONFIG_FB. Does your machine have any graphical output device?
If yes, which driver do you use?

You may also want to make sure that you have 9d6366e743f3 ("drm:
fb_helper: improve CONFIG_FB dependency") in your kernel, which
fixes a minor problem with my original patch.

         Arnd

WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@kernel.org>
To: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Cc: Fabio Estevam <festevam@gmail.com>,
	Randy Dunlap <rdunlap@infradead.org>,
	 Kees Cook <keescook@chromium.org>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	 "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: Wed, 2 Feb 2022 08:46:00 +0100	[thread overview]
Message-ID: <CAK8P3a3ELrSC=KX6cr8UnP6kkJN0AXeAE4EG4oUY=Zz7gG_dgg@mail.gmail.com> (raw)
In-Reply-To: <d8981e2a-4f61-72bb-e5cc-bf4ded29c08a@synopsys.com>

On Wed, Feb 2, 2022 at 1:14 AM Thinh Nguyen <Thinh.Nguyen@synopsys.com> wrote:
> Fabio Estevam wrote:
> > On Tue, Feb 1, 2022 at 8:06 PM Randy Dunlap <rdunlap@infradead.org> wrote:
> >>
> >> 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?
>
> I did not enable it.
>
> >> Please provide the failing .config file.
> >
> > Does selecting CONFIG_FB=y help?
> >
>
> On the config that has the issue, this isn't set. After reverting the
> commit above, this was set. Maybe this is what's needed? I need to test it.

CONFIG_FB should not normally be needed for booting, so unless
you have a graphical application in your initramfs that requires the /dev/fb0
device to work, it is not supposed to make a difference.

Are there any other differences in your .config before and after the patch?
It's possible that you use some other driver that in turn depends on
CONFIG_FB. Does your machine have any graphical output device?
If yes, which driver do you use?

You may also want to make sure that you have 9d6366e743f3 ("drm:
fb_helper: improve CONFIG_FB dependency") in your kernel, which
fixes a minor problem with my original patch.

         Arnd

_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek

WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@kernel.org>
To: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Cc: Fabio Estevam <festevam@gmail.com>,
	Randy Dunlap <rdunlap@infradead.org>,
	 Kees Cook <keescook@chromium.org>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	 "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: Wed, 2 Feb 2022 08:46:00 +0100	[thread overview]
Message-ID: <CAK8P3a3ELrSC=KX6cr8UnP6kkJN0AXeAE4EG4oUY=Zz7gG_dgg@mail.gmail.com> (raw)
In-Reply-To: <d8981e2a-4f61-72bb-e5cc-bf4ded29c08a@synopsys.com>

On Wed, Feb 2, 2022 at 1:14 AM Thinh Nguyen <Thinh.Nguyen@synopsys.com> wrote:
> Fabio Estevam wrote:
> > On Tue, Feb 1, 2022 at 8:06 PM Randy Dunlap <rdunlap@infradead.org> wrote:
> >>
> >> 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?
>
> I did not enable it.
>
> >> Please provide the failing .config file.
> >
> > Does selecting CONFIG_FB=y help?
> >
>
> On the config that has the issue, this isn't set. After reverting the
> commit above, this was set. Maybe this is what's needed? I need to test it.

CONFIG_FB should not normally be needed for booting, so unless
you have a graphical application in your initramfs that requires the /dev/fb0
device to work, it is not supposed to make a difference.

Are there any other differences in your .config before and after the patch?
It's possible that you use some other driver that in turn depends on
CONFIG_FB. Does your machine have any graphical output device?
If yes, which driver do you use?

You may also want to make sure that you have 9d6366e743f3 ("drm:
fb_helper: improve CONFIG_FB dependency") in your kernel, which
fixes a minor problem with my original patch.

         Arnd

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@kernel.org>
To: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Cc: Kees Cook <keescook@chromium.org>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Randy Dunlap <rdunlap@infradead.org>,
	"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: Wed, 2 Feb 2022 08:46:00 +0100	[thread overview]
Message-ID: <CAK8P3a3ELrSC=KX6cr8UnP6kkJN0AXeAE4EG4oUY=Zz7gG_dgg@mail.gmail.com> (raw)
In-Reply-To: <d8981e2a-4f61-72bb-e5cc-bf4ded29c08a@synopsys.com>

On Wed, Feb 2, 2022 at 1:14 AM Thinh Nguyen <Thinh.Nguyen@synopsys.com> wrote:
> Fabio Estevam wrote:
> > On Tue, Feb 1, 2022 at 8:06 PM Randy Dunlap <rdunlap@infradead.org> wrote:
> >>
> >> 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?
>
> I did not enable it.
>
> >> Please provide the failing .config file.
> >
> > Does selecting CONFIG_FB=y help?
> >
>
> On the config that has the issue, this isn't set. After reverting the
> commit above, this was set. Maybe this is what's needed? I need to test it.

CONFIG_FB should not normally be needed for booting, so unless
you have a graphical application in your initramfs that requires the /dev/fb0
device to work, it is not supposed to make a difference.

Are there any other differences in your .config before and after the patch?
It's possible that you use some other driver that in turn depends on
CONFIG_FB. Does your machine have any graphical output device?
If yes, which driver do you use?

You may also want to make sure that you have 9d6366e743f3 ("drm:
fb_helper: improve CONFIG_FB dependency") in your kernel, which
fixes a minor problem with my original patch.

         Arnd

  reply	other threads:[~2022-02-02  7:46 UTC|newest]

Thread overview: 63+ 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:01 ` Thinh Nguyen
2022-02-01 23:01 ` Thinh Nguyen
2022-02-01 23:01 ` Thinh Nguyen
2022-02-01 23:06 ` Randy Dunlap
2022-02-01 23:06   ` Randy Dunlap
2022-02-01 23:06   ` Randy Dunlap
2022-02-01 23:06   ` Randy Dunlap
2022-02-01 23:59   ` Fabio Estevam
2022-02-01 23:59     ` Fabio Estevam
2022-02-01 23:59     ` Fabio Estevam
2022-02-01 23:59     ` Fabio Estevam
2022-02-02  0:14     ` Thinh Nguyen
2022-02-02  0:14       ` Thinh Nguyen
2022-02-02  0:14       ` Thinh Nguyen
2022-02-02  0:14       ` Thinh Nguyen
2022-02-02  7:46       ` Arnd Bergmann [this message]
2022-02-02  7:46         ` Arnd Bergmann
2022-02-02  7:46         ` Arnd Bergmann
2022-02-02  7:46         ` Arnd Bergmann
2022-02-02 23:55         ` Thinh Nguyen
2022-02-02 23:55           ` Thinh Nguyen
2022-02-02 23:55           ` Thinh Nguyen
2022-02-03  3:15           ` Randy Dunlap
2022-02-03  3:15             ` Randy Dunlap
2022-02-03  3:15             ` Randy Dunlap
2022-02-03  3:15             ` Randy Dunlap
2022-02-03  4:23             ` Thinh Nguyen
2022-02-03  4:23               ` Thinh Nguyen
2022-02-03  4:23               ` Thinh Nguyen
2022-02-03  4:23               ` Thinh Nguyen
2022-02-03  7:18           ` Arnd Bergmann
2022-02-03  7:18             ` Arnd Bergmann
2022-02-03  7:18             ` Arnd Bergmann
2022-02-03  7:18             ` Arnd Bergmann
2022-02-04  3:21             ` Thinh Nguyen
2022-02-04  3:21               ` Thinh Nguyen
2022-02-04  3:21               ` Thinh Nguyen
2022-02-04  3:21               ` Thinh Nguyen
2022-02-04  4:02               ` Randy Dunlap
2022-02-04  4:02                 ` Randy Dunlap
2022-02-04  4:02                 ` Randy Dunlap
2022-02-04  4:02                 ` Randy Dunlap
2022-02-08 20:10                 ` Thinh Nguyen
2022-02-08 20:10                   ` Thinh Nguyen
2022-02-08 20:10                   ` Thinh Nguyen
2022-02-08 20:10                   ` Thinh Nguyen
2022-02-08 20:45                   ` Randy Dunlap
2022-02-08 20:45                     ` Randy Dunlap
2022-02-08 20:45                     ` Randy Dunlap
2022-02-08 20:45                     ` Randy Dunlap
2022-02-08 22:42                     ` Thinh Nguyen
2022-02-08 22:42                       ` Thinh Nguyen
2022-02-08 22:42                       ` Thinh Nguyen
2022-02-08 22:42                       ` Thinh Nguyen
2022-02-09  7:06                       ` Arnd Bergmann
2022-02-09  7:06                         ` Arnd Bergmann
2022-02-09  7:06                         ` Arnd Bergmann
2022-02-09  7:06                         ` Arnd Bergmann
2022-02-15  2:52                         ` Thinh Nguyen
2022-02-15  2:52                           ` Thinh Nguyen
2022-02-15  2:52                           ` Thinh Nguyen
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='CAK8P3a3ELrSC=KX6cr8UnP6kkJN0AXeAE4EG4oUY=Zz7gG_dgg@mail.gmail.com' \
    --to=arnd@kernel.org \
    --cc=Bing.Yuan@synopsys.com \
    --cc=John.Youn@synopsys.com \
    --cc=Thinh.Nguyen@synopsys.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=festevam@gmail.com \
    --cc=keescook@chromium.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=rdunlap@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 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.