From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: linux-pm@vger.kernel.org, "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: kbuild-all@lists.01.org, linux-acpi@vger.kernel.org,
devel@acpica.org, kernel test robot <lkp@intel.com>,
x86@kernel.org
Subject: Re: [pm:acpi 1/2] ERROR: modpost: "wakeup_cpu0" [drivers/acpi/processor.ko] undefined!
Date: Tue, 06 Apr 2021 14:05:40 +0200 [thread overview]
Message-ID: <87pmz7d3e3.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <202104030252.XSSunJui-lkp@intel.com>
kernel test robot <lkp@intel.com> writes:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git acpi
> head: 91463ebff32d3e6fc71134784ae6aa91402bfe3d
> commit: 8cdddd182bd7befae6af49c5fd612893f55d6ccb [1/2] ACPI: processor: Fix CPU0 wakeup in acpi_idle_play_dead()
> config: x86_64-randconfig-r016-20210401 (attached as .config)
> compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
> reproduce (this is a W=1 build):
> # https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?id=8cdddd182bd7befae6af49c5fd612893f55d6ccb
> git remote add pm https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
> git fetch --no-tags pm acpi
> git checkout 8cdddd182bd7befae6af49c5fd612893f55d6ccb
> # save the attached .config to linux build tree
> make W=1 ARCH=x86_64
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>, old ones prefixed by <<):
>
>>> ERROR: modpost: "wakeup_cpu0" [drivers/acpi/processor.ko] undefined!
>>> ERROR: modpost: "start_cpu0" [drivers/acpi/processor.ko] undefined!
>
This happens when we have
CONFIG_ACPI_PROCESSOR=m
as wakeup_cpu0()/start_cpu0() are not exported, sorry about the breakage
:-( I'll be sending a patch to fix things up shortly.
--
Vitaly
WARNING: multiple messages have this Message-ID (diff)
From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: kbuild-all@lists.01.org
Subject: Re: [pm:acpi 1/2] ERROR: modpost: "wakeup_cpu0" [drivers/acpi/processor.ko] undefined!
Date: Tue, 06 Apr 2021 14:05:40 +0200 [thread overview]
Message-ID: <87pmz7d3e3.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <202104030252.XSSunJui-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1409 bytes --]
kernel test robot <lkp@intel.com> writes:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git acpi
> head: 91463ebff32d3e6fc71134784ae6aa91402bfe3d
> commit: 8cdddd182bd7befae6af49c5fd612893f55d6ccb [1/2] ACPI: processor: Fix CPU0 wakeup in acpi_idle_play_dead()
> config: x86_64-randconfig-r016-20210401 (attached as .config)
> compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
> reproduce (this is a W=1 build):
> # https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?id=8cdddd182bd7befae6af49c5fd612893f55d6ccb
> git remote add pm https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
> git fetch --no-tags pm acpi
> git checkout 8cdddd182bd7befae6af49c5fd612893f55d6ccb
> # save the attached .config to linux build tree
> make W=1 ARCH=x86_64
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>, old ones prefixed by <<):
>
>>> ERROR: modpost: "wakeup_cpu0" [drivers/acpi/processor.ko] undefined!
>>> ERROR: modpost: "start_cpu0" [drivers/acpi/processor.ko] undefined!
>
This happens when we have
CONFIG_ACPI_PROCESSOR=m
as wakeup_cpu0()/start_cpu0() are not exported, sorry about the breakage
:-( I'll be sending a patch to fix things up shortly.
--
Vitaly
next prev parent reply other threads:[~2021-04-06 12:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 18:45 [Devel] [pm:acpi 1/2] ERROR: modpost: "wakeup_cpu0" [drivers/acpi/processor.ko] undefined! kernel test robot
2021-04-02 18:45 ` kernel test robot
2021-04-02 18:45 ` kernel test robot
2021-04-06 12:05 ` Vitaly Kuznetsov [this message]
2021-04-06 12:05 ` Vitaly Kuznetsov
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=87pmz7d3e3.fsf@vitty.brq.redhat.com \
--to=vkuznets@redhat.com \
--cc=devel@acpica.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lkp@intel.com \
--cc=rjw@rjwysocki.net \
--cc=x86@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 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.