[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5a1e11fb-4213-45f6-a5ef-636de5e175d8@linuxfoundation.org>
Date: Wed, 12 Mar 2025 17:51:36 -0600
From: Shuah Khan <skhan@...uxfoundation.org>
To: David Gow <davidgow@...gle.com>
Cc: Brendan Higgins <brendan.higgins@...ux.dev>, Rae Moar <rmoar@...gle.com>,
linux-kselftest@...r.kernel.org, linux-kernel@...r.kernel.org,
Shuah Khan <skhan@...uxfoundation.org>
Subject: Re: Error during --arch x86_64 kunit test run
On 3/12/25 16:52, David Gow wrote:
> Hi Shuah,
>
> On Thu, 13 Mar 2025 at 05:14, Shuah Khan <skhan@...uxfoundation.org> wrote:
>>
>> David, Brendan, Rae,
>>
>> I am seeing the following error when I run
>>
>> ./tools/testing/kunit/kunit.py run --arch x86_64
>>
>> ERROR:root:ld:arch/x86/realmode/rm/realmode.lds:236: undefined symbol `sev_es_trampoline_start' referenced in expression
>>
>> I isolated it to dependency on CONFIG_AMD_MEM_ENCRYPT
>>
>
> That's interesting. I recall seeing this issue briefly about a year
> ago on an internal branch, and we worked around it there by enabling
> CONFIG_AMD_MEM_ENCRYPT (which worked).
>
> But I've been totally unable to reproduce it this morning: are you
> seeing this on any particular branch / config / environment?
linux_next - I did allmodconfig build prior to running the tests.
That means I had to run make ARCH=x86_64 mrproper before running
./tools/testing/kunit/kunit.py run --arch x86_64
I tried something different checking out a fresh
linux_next repo and running ./tools/testing/kunit/kunit.py run --arch x86_64
No errors on
./tools/testing/kunit/kunit.py run --arch x86_64
I will try this again and let you know. Can you try this as well.
- Clean linux_next and run tests
- Run tests after buidling allmodconfig and mrproper
thanks,
-- Shuah
Powered by blists - more mailing lists