From: Randy Dunlap <rdunlap@infradead.org>
To: Gustavo Padovan <gus@collabora.com>,
Denys Fedoryshchenko <denys.f@collabora.com>
Cc: kernelci <kernelci@lists.linux.dev>,
kernelci-results <kernelci-results@groups.io>,
regressions <regressions@lists.linux.dev>,
linux-next <linux-next@vger.kernel.org>
Subject: Re: [REGRESSION] next/master: (build) undefined reference to `pm_hibernation_mode_is_suspend' in vmlinux...
Date: Mon, 29 Sep 2025 08:34:02 -0700 [thread overview]
Message-ID: <bccbcccb-a3db-4b34-962c-14e79cc8bece@infradead.org> (raw)
In-Reply-To: <19995464e11.7f75fad1483203.4516273948739211660@collabora.com>
Hi,
On 9/29/25 4:40 AM, Gustavo Padovan wrote:
> Hi Randy,
>
>
> ---- On Mon, 29 Sep 2025 01:15:24 -0300 Denys Fedoryshchenko <denys.f@collabora.com> wrote ---
>
> > Hi Randy,
> >
> > On Sun, 2025-09-28 at 18:13 -0700, Randy Dunlap wrote:
> > > Hi,
> > >
> > > On 9/26/25 9:59 AM, KernelCI bot wrote:
> > > >
> > > >
> > > >
> > > >
> > > > Hello,
> > > >
> > > > New build issue found on next/master:
> > > >
> > > > ---
> > > > undefined reference to `pm_hibernation_mode_is_suspend' in
> > > > vmlinux.unstripped (drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c)
> > > > [logspec:kbuild,kbuild.compiler.linker_error]
> > > > ---
> > > >
> > > > - dashboard:
> > > > https://d.kernelci.org/i/maestro:74f8fe195e9e78290f1dae54754bf5b8d4b2a893
> > > > - giturl:
> > > > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> > > > - commit HEAD: 262858079afde6d367ce3db183c74d8a43a0e83f
> > > > - tags: next-20250926
> > > >
> > > >
> > > > Log excerpt:
> > > > =====================================================
> > > > LD .tmp_vmlinux1
> > > > ld: drivers/gpu/drm/amd/amdgpu/amdgpu_drv.o: in function
> > > > `amdgpu_pmops_thaw':
> > > > /tmp/kci/linux/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c:2677:
> > > > undefined reference to `pm_hibernation_mode_is_suspend'
> > > >
> > > > =====================================================
> > > >
> > > >
> > > > # Builds where the incident occurred:
> > > >
> > > > ## cros://chromeos-6.6/x86_64/chromeos-amd-
> > > > stoneyridge.flavour.config+lab-setup+x86-
> > > > board+CONFIG_MODULE_COMPRESS=n+CONFIG_MODULE_COMPRESS_NONE=y on
> > > > (x86_64):
> > > > - compiler: gcc-12
> > > > - dashboard:
> > > > https://d.kernelci.org/build/maestro:68d6bd56aabea828fddae00b
> > > >
> > > > ## cros://chromeos-6.6/x86_64/chromeos-intel-
> > > > pineview.flavour.config+lab-setup+x86-
> > > > board+CONFIG_MODULE_COMPRESS=n+CONFIG_MODULE_COMPRESS_NONE=y on
> > > > (x86_64):
> > > > - compiler: gcc-12
> > > > - dashboard:
> > > > https://d.kernelci.org/build/maestro:68d6bd59aabea828fddae00e
> > > >
> > >
> > > Is there a URL for the .config file that causes the
> > > build error?
> > Yes,
> > https://files.kernelci.org/kbuild-gcc-12-x86-chromeos-intel-68d6bd59aabea828fddae00e/.config
>
> Out of curiosity, have you tried to find the config in our Dashboard? We added basic information in
> the email report and then the Dashboard link take you to our comprehensive report.
>
I did look at the Dashboard first but it seems that I overlooked the config file info.
>
> Any feedback here?
I would rather not use the Dashboard until I need to dig deeperinto the problem. IOW, I prefer to have the config file URL
in the email report.
Thanks.
--
~Randy
next prev parent reply other threads:[~2025-09-29 15:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 16:59 [REGRESSION] next/master: (build) undefined reference to `pm_hibernation_mode_is_suspend' in vmlinux KernelCI bot
2025-09-29 1:13 ` Randy Dunlap
2025-09-29 4:15 ` Denys Fedoryshchenko
2025-09-29 11:40 ` Gustavo Padovan
2025-09-29 15:34 ` Randy Dunlap [this message]
2025-09-29 21:59 ` Randy Dunlap
2025-10-06 12:22 ` Gustavo Padovan
2025-10-06 17:01 ` Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2025-09-26 16:59 KernelCI bot
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=bccbcccb-a3db-4b34-962c-14e79cc8bece@infradead.org \
--to=rdunlap@infradead.org \
--cc=denys.f@collabora.com \
--cc=gus@collabora.com \
--cc=kernelci-results@groups.io \
--cc=kernelci@lists.linux.dev \
--cc=linux-next@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/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