All of lore.kernel.org
 help / color / mirror / Atom feed
From: Péter Ujfalusi <peter.ujfalusi@linux.intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [linux-next:master 4766/5417] sound/soc/sof/core.c:135: undefined reference to `sof_client_fw_state_dispatcher'
Date: Mon, 14 Feb 2022 13:39:19 +0200	[thread overview]
Message-ID: <2427ac68-bc54-a129-35f2-96b61099bf06@linux.intel.com> (raw)
In-Reply-To: <69845e3e-6dac-fc9b-5914-78833b2cfa5a@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 3319 bytes --]



On 13/02/2022 00:42, Pierre-Louis Bossart wrote:
> 
> 
> On 2/12/22 15:00, kernel test robot wrote:
>> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>> head:   6d9bd4ad4ca08b1114e814c2c42383b8b13be631
>> commit: 3dc0d709177828a22dfc9d0072e3ac937ef90d06 [4766/5417] ASoC: SOF: Convert the generic probe support to SOF client
>> config: i386-randconfig-a003-20210930 (https://download.01.org/0day-ci/archive/20220213/202202130429.GEdTKNDQ-lkp(a)intel.com/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/next/linux-next.git/commit/?id=3dc0d709177828a22dfc9d0072e3ac937ef90d06
>>         git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>>         git fetch --no-tags linux-next master
>>         git checkout 3dc0d709177828a22dfc9d0072e3ac937ef90d06
>>         # save the config file to linux build tree
>>         mkdir build_dir
>>         make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
>>
>> 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 >>):
>>
>>    ld: sound/soc/sof/core.o: in function `sof_set_fw_state':
>>>> sound/soc/sof/core.c:135: undefined reference to `sof_client_fw_state_dispatcher'
>>    ld: sound/soc/sof/core.o: in function `sof_probe_continue':
>>>> sound/soc/sof/core.c:287: undefined reference to `sof_register_clients'
>>    ld: sound/soc/sof/core.o: in function `sof_set_fw_state':
>>>> sound/soc/sof/core.c:135: undefined reference to `sof_client_fw_state_dispatcher'
>>    ld: sound/soc/sof/core.o: in function `snd_sof_device_remove':
>>>> sound/soc/sof/core.c:427: undefined reference to `sof_unregister_clients'
>>    ld: sound/soc/sof/core.o: in function `sof_set_fw_state':
>>>> sound/soc/sof/core.c:135: undefined reference to `sof_client_fw_state_dispatcher'
>>    ld: sound/soc/sof/ipc.o: in function `snd_sof_ipc_msgs_rx':
>>>> sound/soc/sof/ipc.c:574: undefined reference to `sof_client_ipc_rx_dispatcher'
>>    ld: sound/soc/sof/pm.o: in function `sof_suspend':
>>>> sound/soc/sof/pm.c:227: undefined reference to `sof_suspend_clients'
>>>> ld: sound/soc/sof/pm.c:217: undefined reference to `sof_suspend_clients'
>>    ld: sound/soc/sof/pm.o: in function `sof_resume':
>>>> sound/soc/sof/pm.c:171: undefined reference to `sof_resume_clients'
>>
> 
> I can reproduce this with the attached config with networking disabled,
> otherwise I have a compilation issues.

I was also able to reproduce it.

> Not sure why we are only seeing this now, this code has been in the SOF
> tree for months.

It came out of randconfig, we might not been lucky enough to get this
combination...

> At any rate, it seems like a legit problem, where some configs result in
> the sof core configured as built-in but the clients configured as
> modules. We need to find a way to force the client to use the same
> configuration as the core.

Changing the SOC_SOF_CLIENT from tristate to bool worked, but I think
the fix via the Makefile is better:
https://lore.kernel.org/alsa-devel/20220214071330.22151-1-peter.ujfalusi(a)linux.intel.com/

-- 
Péter

WARNING: multiple messages have this Message-ID (diff)
From: "Péter Ujfalusi" <peter.ujfalusi@linux.intel.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	Mark Brown <broonie@kernel.org>,
	Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
	Kai Vehmanen <kai.vehmanen@linux.intel.com>
Subject: Re: [linux-next:master 4766/5417] sound/soc/sof/core.c:135: undefined reference to `sof_client_fw_state_dispatcher'
Date: Mon, 14 Feb 2022 13:39:19 +0200	[thread overview]
Message-ID: <2427ac68-bc54-a129-35f2-96b61099bf06@linux.intel.com> (raw)
In-Reply-To: <69845e3e-6dac-fc9b-5914-78833b2cfa5a@linux.intel.com>



On 13/02/2022 00:42, Pierre-Louis Bossart wrote:
> 
> 
> On 2/12/22 15:00, kernel test robot wrote:
>> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>> head:   6d9bd4ad4ca08b1114e814c2c42383b8b13be631
>> commit: 3dc0d709177828a22dfc9d0072e3ac937ef90d06 [4766/5417] ASoC: SOF: Convert the generic probe support to SOF client
>> config: i386-randconfig-a003-20210930 (https://download.01.org/0day-ci/archive/20220213/202202130429.GEdTKNDQ-lkp@intel.com/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/next/linux-next.git/commit/?id=3dc0d709177828a22dfc9d0072e3ac937ef90d06
>>         git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>>         git fetch --no-tags linux-next master
>>         git checkout 3dc0d709177828a22dfc9d0072e3ac937ef90d06
>>         # save the config file to linux build tree
>>         mkdir build_dir
>>         make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
>>
>> 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 >>):
>>
>>    ld: sound/soc/sof/core.o: in function `sof_set_fw_state':
>>>> sound/soc/sof/core.c:135: undefined reference to `sof_client_fw_state_dispatcher'
>>    ld: sound/soc/sof/core.o: in function `sof_probe_continue':
>>>> sound/soc/sof/core.c:287: undefined reference to `sof_register_clients'
>>    ld: sound/soc/sof/core.o: in function `sof_set_fw_state':
>>>> sound/soc/sof/core.c:135: undefined reference to `sof_client_fw_state_dispatcher'
>>    ld: sound/soc/sof/core.o: in function `snd_sof_device_remove':
>>>> sound/soc/sof/core.c:427: undefined reference to `sof_unregister_clients'
>>    ld: sound/soc/sof/core.o: in function `sof_set_fw_state':
>>>> sound/soc/sof/core.c:135: undefined reference to `sof_client_fw_state_dispatcher'
>>    ld: sound/soc/sof/ipc.o: in function `snd_sof_ipc_msgs_rx':
>>>> sound/soc/sof/ipc.c:574: undefined reference to `sof_client_ipc_rx_dispatcher'
>>    ld: sound/soc/sof/pm.o: in function `sof_suspend':
>>>> sound/soc/sof/pm.c:227: undefined reference to `sof_suspend_clients'
>>>> ld: sound/soc/sof/pm.c:217: undefined reference to `sof_suspend_clients'
>>    ld: sound/soc/sof/pm.o: in function `sof_resume':
>>>> sound/soc/sof/pm.c:171: undefined reference to `sof_resume_clients'
>>
> 
> I can reproduce this with the attached config with networking disabled,
> otherwise I have a compilation issues.

I was also able to reproduce it.

> Not sure why we are only seeing this now, this code has been in the SOF
> tree for months.

It came out of randconfig, we might not been lucky enough to get this
combination...

> At any rate, it seems like a legit problem, where some configs result in
> the sof core configured as built-in but the clients configured as
> modules. We need to find a way to force the client to use the same
> configuration as the core.

Changing the SOC_SOF_CLIENT from tristate to bool worked, but I think
the fix via the Makefile is better:
https://lore.kernel.org/alsa-devel/20220214071330.22151-1-peter.ujfalusi@linux.intel.com/

-- 
Péter


  reply	other threads:[~2022-02-14 11:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-12 21:00 [linux-next:master 4766/5417] sound/soc/sof/core.c:135: undefined reference to `sof_client_fw_state_dispatcher' kernel test robot
2022-02-12 21:00 ` kernel test robot
2022-02-12 22:42 ` Pierre-Louis Bossart
2022-02-12 22:42   ` Pierre-Louis Bossart
2022-02-14 11:39   ` Péter Ujfalusi [this message]
2022-02-14 11:39     ` Péter Ujfalusi

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=2427ac68-bc54-a129-35f2-96b61099bf06@linux.intel.com \
    --to=peter.ujfalusi@linux.intel.com \
    --cc=kbuild-all@lists.01.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.