From: Petr Vorel <pvorel@suse.cz>
To: "Kubaj, Piotr" <piotr.kubaj@intel.com>
Cc: "Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
"Ossowski, Tomasz" <tomasz.ossowski@intel.com>,
"Dubel, Helena Anna" <helena.anna.dubel@intel.com>,
"Niestepski, Daniel" <daniel.niestepski@intel.com>,
"ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v2] thermal: add new test group
Date: Thu, 22 Jan 2026 00:06:39 +0100 [thread overview]
Message-ID: <20260121230639.GA10001@pevik> (raw)
In-Reply-To: <4dd67d8bf040715bf5a6456bb4270f08dba3986b.camel@intel.com>
Hi Piotr,
> > I tried to run test under root:
> > # ./thermal_interrupt_events
> > tst_test.c:1856: TINFO: Overall timeout per run is 0h 03m 30s
> > thermal_interrupt_events.c:168: TBROK: Failed to close FILE
> > '/sys/class/thermal/thermal_zone1/trip_point_1_temp': EINVAL (22)
> > But later it worked:
> > tst_test.c:2028: TINFO: LTP version: 20250930-134-g02805b05a1
> > tst_test.c:2031: TINFO: Tested kernel: 6.17.12+deb14-amd64 #1 SMP
> > PREEMPT_DYNAMIC Debian 6.17.12-1 (2025-12-14) x86_64
> > tst_kconfig.c:88: TINFO: Parsing kernel config '/boot/config-
> > 6.17.12+deb14-amd64'
> > tst_test.c:1856: TINFO: Overall timeout per run is 0h 03m 30s
> > thermal_interrupt_events.c:181: TPASS: x86 package thermal interrupt
> > triggered
> > I wonder what was wrong.
> Can you check if the test fails again the 1st time after a reboot? If
> I'm correct, it might be a reproduction of the bug due to be fixed in
> https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/patch/?id=39b1bd1613b8f73994f654988ad75a72b633f5e2
Yes, it's really affected only 1st run after reboot. Thanks for pointing out
the fix.
In that case once fix is merged to Linus' tree (so that the git commit hash will
not change) we should add it to the test [1]:
struct tst_test test = {
...
.tags = (const struct tst_tag[]) {
{"linux-git", "39b1bd1613b8f"},
{}
This info will be printed on the test failure. And also the fix will be in our
doc [2].
(The fix is not yet in the next tree, because thermal-fixes branch is not
configured for linux-next git, although other linux-pm git branches are
configured [3]).
Kind regards,
Petr
[1] https://github.com/linux-test-project/ltp/blob/master/doc/old/C-Test-API.asciidoc#140-test-tags
[2] https://linux-test-project.readthedocs.io/en/latest/users/test_catalog.html
[3] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/Next/Trees?h=next-20260121
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-01-21 23:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 14:46 [LTP] [PATCH v2] thermal: add new test group Piotr Kubaj
2026-01-20 19:38 ` Petr Vorel
2026-01-21 11:55 ` Kubaj, Piotr
2026-01-21 23:06 ` Petr Vorel [this message]
2026-01-22 14:27 ` Petr Vorel
2026-01-23 12:37 ` Kubaj, Piotr
2026-01-23 19:48 ` Petr Vorel
-- strict thread matches above, loose matches on Subject: below --
2025-11-14 18:01 Piotr Kubaj
2025-11-18 18:18 ` Cyril Hrubis
2025-11-19 9:35 ` Cyril Hrubis
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=20260121230639.GA10001@pevik \
--to=pvorel@suse.cz \
--cc=daniel.niestepski@intel.com \
--cc=helena.anna.dubel@intel.com \
--cc=ltp@lists.linux.it \
--cc=piotr.kubaj@intel.com \
--cc=rafael.j.wysocki@intel.com \
--cc=tomasz.ossowski@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