public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Heiner Kallweit <hkallweit1@gmail.com>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	Luis Chamberlain <mcgrof@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: wait_for_initramfs warning from kernel_init_freeable()
Date: Thu, 29 Apr 2021 09:16:18 +0200	[thread overview]
Message-ID: <4d6aa2dd-92df-4f36-10ac-cd003a0229f7@gmail.com> (raw)
In-Reply-To: <c197724b-3d16-45bd-d71b-0a016196ca40@gmail.com>

On 29.04.2021 08:46, Heiner Kallweit wrote:
> Since 97f8172f9a98 ("init/initramfs.c: do unpacking asynchronously") I get
> the following warning early in the boot process from umh:
> "wait_for_initramfs() called before rootfs_initcalls"
> Some debugging lead me to the following call chain:
> 
> kernel_init_freeable()
> -> do_basic_setup()
>    -> driver_init()
>       -> platform_bus_init()
>          -> bus_register()
>             -> kset_register()
>                -> kobject_uvent()
> 

Sorry, this is the first umh call, but at this time UMH_DISABLED is still set.
The first umh call where UMH is enabled is the following:

kernel_init_freeable()
-> do_basic_setup()
   -> do_initcalls()
      -> do_one_initcall()
         -> wq_sysfs_init()         <- core_initcall()
            -> subsys_virtual_register()
               -> bus_register()

  reply	other threads:[~2021-04-29  7:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29  6:46 wait_for_initramfs warning from kernel_init_freeable() Heiner Kallweit
2021-04-29  7:16 ` Heiner Kallweit [this message]
2021-04-29  8:18   ` Rasmus Villemoes
2021-04-29  8:52     ` Heiner Kallweit

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=4d6aa2dd-92df-4f36-10ac-cd003a0229f7@gmail.com \
    --to=hkallweit1@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=mcgrof@kernel.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