[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231011085421.h4qtizye4m3rjuov@vireshk-i7>
Date: Wed, 11 Oct 2023 14:24:21 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Thorsten Leemhuis <linux@...mhuis.info>
Cc: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
LKML <linux-kernel@...r.kernel.org>,
linux-arm-msm <linux-arm-msm@...r.kernel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: next: Build error on arm64: `modpost: "of_find_next_cache_node"
[drivers/cpufreq/qcom-cpufreq-nvmem.ko] undefined!`
On 11-10-23, 10:49, Thorsten Leemhuis wrote:
> Hi Dmitry, my linux-next builds for Fedora failed today with this error:
>
> > + /usr/bin/make -s 'HOSTCFLAGS=-O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection ' 'HOSTLDFLAGS=-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes ' ARCH=arm64 'KCFLAGS= ' WITH_GCOV=0 -j4 modules
> > drivers/net/ethernet/freescale/dpaa/dpaa_ethtool.c: In function 'dpaa_set_coalesce':
> > drivers/net/ethernet/freescale/dpaa/dpaa_ethtool.c:502:1: warning: the frame size of 4112 bytes is larger than 2048 bytes [-Wframe-larger-than=]
> > 502 | }
> > | ^
> > drivers/net/ethernet/freescale/dpaa/dpaa_eth.c: In function 'dpaa_fq_setup.constprop':
> > drivers/net/ethernet/freescale/dpaa/dpaa_eth.c:1000:1: warning: the frame size of 8224 bytes is larger than 2048 bytes [-Wframe-larger-than=]
> > 1000 | }
> > | ^
> > ERROR: modpost: "of_find_next_cache_node" [drivers/cpufreq/qcom-cpufreq-nvmem.ko] undefined!
>
> A quick search on lore found that the 0-day bot encountered a similar
> problem early July:
> https://lore.kernel.org/all/202307030626.PUPpfATh-lkp@intel.com/
>
> Back then it afaics was caused by "cpufreq: qcom-nvmem: create L2 cache
> device" which is new in todays next, which makes it a likely suspect for
> my problem. That's why I decided to write this mail. But note, I didn't
> verify if that patch really causes the trouble; hence if you think it
> might be something entirely different, let me know.
>
> Full build log:
> https://copr-be.cloud.fedoraproject.org/results/@kernel-vanilla/next/fedora-38-aarch64/06516038-next-next-all/builder-live.log.gz
>
> I don't have the config file at hand, but it should be the following one
> processed with "make olddefconfig"
> https://www.leemhuis.info/files/misc/kernel-aarch64-fedora.config
of_find_next_cache_node() needs to be exported for modules.
Dmitry, can you send a patch for that and mention that it needs to go
in via my tree ?
--
viresh
Powered by blists - more mailing lists