From: Randy Dunlap <rdunlap@infradead•org>
To: Alex Deucher <alexdeucher@gmail•com>,
"Sudip Mukherjee (Codethink)" <sudipm.mukherjee@gmail•com>
Cc: "Alex Deucher" <alexander.deucher@amd•com>,
"Christian König" <christian.koenig@amd•com>,
"Pan, Xinhui" <Xinhui.Pan@amd•com>,
"David Airlie" <airlied@linux•ie>,
"Daniel Vetter" <daniel@ffwll•ch>,
linux-next@vger•kernel.org, dri-devel@lists•freedesktop.org,
amd-gfx@lists•freedesktop.org, linux-kernel@vger•kernel.org
Subject: Re: build failure of next-20220817 for amdgpu
Date: Wed, 17 Aug 2022 19:09:26 -0700 [thread overview]
Message-ID: <5638aaf1-b808-bdc6-d84a-820f24facea6@infradead.org> (raw)
In-Reply-To: <CADnq5_Od9W1iuzYpsmODOB=Xem97ogeH_t0JrjWC-S8h0XM9fA@mail.gmail.com>
On 8/17/22 19:01, Alex Deucher wrote:
> On Wed, Aug 17, 2022 at 6:03 PM Sudip Mukherjee (Codethink)
> <sudipm.mukherjee@gmail•com> wrote:
>>
>> Hi All,
>>
>> Not sure if it has been reported, build of next-20220817 fails with the
>> error:
>>
>> ERROR: modpost: "cpu_smallcore_map" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] undefined!
>>
>> Trying to do a git bisect to find out the offending commit.
>>
>
> Thanks. I don't see that symbol in the driver at all. Not sure where
> it is coming from.
>
It's powerpc only.
Sudip, is it non-CONFIG_SMP by any chance?
>
>
>> I will be happy to test any patch or provide any extra log if needed.
>>
>>
>> --
>> Regards
>> Sudip
--
~Randy
next prev parent reply other threads:[~2022-08-18 2:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 22:02 build failure of next-20220817 for amdgpu Sudip Mukherjee (Codethink)
2022-08-18 2:01 ` Alex Deucher
2022-08-18 2:09 ` Randy Dunlap [this message]
2022-08-18 10:43 ` Sudip Mukherjee
2022-08-18 15:10 ` Randy Dunlap
2022-08-18 19:15 ` build failure of next-20220817 for amdgpu due to 7bc913085765 ("drm/amdkfd: Try to schedule bottom half on same core") Sudip Mukherjee
2022-08-18 19:34 ` Randy Dunlap
2022-08-19 18:04 ` Felix Kuehling
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=5638aaf1-b808-bdc6-d84a-820f24facea6@infradead.org \
--to=rdunlap@infradead$(echo .)org \
--cc=Xinhui.Pan@amd$(echo .)com \
--cc=airlied@linux$(echo .)ie \
--cc=alexander.deucher@amd$(echo .)com \
--cc=alexdeucher@gmail$(echo .)com \
--cc=amd-gfx@lists$(echo .)freedesktop.org \
--cc=christian.koenig@amd$(echo .)com \
--cc=daniel@ffwll$(echo .)ch \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sudipm.mukherjee@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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