From: Peter Senna Tschudin <peter.senna@linux.intel.com>
To: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Cc: Lucas De Marchi <lucas.demarchi@intel.com>
Subject: [PATCH i-g-t] tests/intel/xe_module_load: Handling of snd_hda_intel
Date: Thu, 10 Oct 2024 11:42:02 +0200 [thread overview]
Message-ID: <ffa2bbcb-edb3-4610-aec8-bcd6a3b8f106@linux.intel.com> (raw)
The problem: Running the following test-list twice fails on the second run:
igt@xe_module_load@load
igt@xe_module_load@unload
The load test will modprobe snd_hda_intel, while the unload will not rmmod
snd_hda_intel. Then running the load test the second time will fail as
snd_hda_intel is loaded and marked as an "unwanted_drivers".
It used to be the case that snd_hda_intel could prevent module load and unload
and we needed to take care of it in older kernels. This is no longer the case
so remove snd_had_intel from unwanted_drivers for this test.
cc: Lucas De Marchi <lucas.demarchi@intel.com>
Signed-off-by: Peter Senna Tschudin <peter.senna@linux.intel.com>
---
tests/intel/xe_module_load.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/tests/intel/xe_module_load.c b/tests/intel/xe_module_load.c
index 30259fc26..83e37430f 100644
--- a/tests/intel/xe_module_load.c
+++ b/tests/intel/xe_module_load.c
@@ -94,7 +94,6 @@ static void load_and_check_xe(const char *opts)
static const char * const unwanted_drivers[] = {
"xe",
"i915",
- "snd_hda_intel",
NULL
};
--
2.34.1
next reply other threads:[~2024-10-10 9:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 9:42 Peter Senna Tschudin [this message]
2024-10-10 10:40 ` ✓ CI.xeBAT: success for tests/intel/xe_module_load: Handling of snd_hda_intel Patchwork
2024-10-10 10:55 ` ✓ Fi.CI.BAT: " Patchwork
2024-10-10 13:22 ` [PATCH i-g-t] " Lucas De Marchi
2024-10-11 0:06 ` ✗ CI.xeFULL: failure for " Patchwork
2024-10-11 5:17 ` Peter Senna Tschudin
2024-10-11 18:25 ` ✗ Fi.CI.IGT: " Patchwork
2024-10-14 5:22 ` Peter Senna Tschudin
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=ffa2bbcb-edb3-4610-aec8-bcd6a3b8f106@linux.intel.com \
--to=peter.senna@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=lucas.demarchi@intel.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