Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: David Gow <davidgow@google.com>
Cc: Brendan Higgins <brendan.higgins@linux.dev>,
	Rae Moar <rmoar@google.com>,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: Error during --arch x86_64 kunit test run
Date: Wed, 12 Mar 2025 17:51:36 -0600	[thread overview]
Message-ID: <5a1e11fb-4213-45f6-a5ef-636de5e175d8@linuxfoundation.org> (raw)
In-Reply-To: <CABVgOSk+xztNcNJ5fQiRSGC3DKHS2H3kN1wHwAO4gCfG7cWY1Q@mail.gmail.com>

On 3/12/25 16:52, David Gow wrote:
> Hi Shuah,
> 
> On Thu, 13 Mar 2025 at 05:14, Shuah Khan <skhan@linuxfoundation.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

  reply	other threads:[~2025-03-12 23:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-12 21:14 Error during --arch x86_64 kunit test run Shuah Khan
2025-03-12 22:52 ` David Gow
2025-03-12 23:51   ` Shuah Khan [this message]
2025-03-13  2:21     ` David Gow
2025-03-13 20:19       ` Shuah Khan

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=5a1e11fb-4213-45f6-a5ef-636de5e175d8@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=brendan.higgins@linux.dev \
    --cc=davidgow@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=rmoar@google.com \
    /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