From: kernel test robot <oliver.sang@intel.com>
To: Zihuan Zhang <zhangzihuan@kylinos.cn>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-pm@vger.kernel.org>,
"rafael J . wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
zhenglifeng <zhenglifeng1@huawei.com>,
<linux-kernel@vger.kernel.org>,
Zihuan Zhang <zhangzihuan@kylinos.cn>, <oliver.sang@intel.com>
Subject: Re: [PATCH v1] cpufreq: Return current frequency when frequency table is unavailable
Date: Mon, 18 Aug 2025 14:54:49 +0800 [thread overview]
Message-ID: <202508180834.3b8fe9d6-lkp@intel.com> (raw)
In-Reply-To: <20250814085216.358207-1-zhangzihuan@kylinos.cn>
Hello,
kernel test robot noticed "xfstests.xfs.177.fail" on:
commit: 69f6747d99d0b1482fb38c36dfa26fe22654ff1f ("[PATCH v1] cpufreq: Return current frequency when frequency table is unavailable")
url: https://github.com/intel-lab-lkp/linux/commits/Zihuan-Zhang/cpufreq-Return-current-frequency-when-frequency-table-is-unavailable/20250814-165519
base: https://git.kernel.org/cgit/linux/kernel/git/rafael/linux-pm.git linux-next
patch link: https://lore.kernel.org/all/20250814085216.358207-1-zhangzihuan@kylinos.cn/
patch subject: [PATCH v1] cpufreq: Return current frequency when frequency table is unavailable
in testcase: xfstests
version: xfstests-x86_64-e1e4a0ea-1_20250714
with following parameters:
disk: 4HDD
fs: xfs
test: xfs-177
config: x86_64-rhel-9.4-func
compiler: gcc-12
test machine: 4 threads Intel(R) Xeon(R) CPU E3-1225 v5 @ 3.30GHz (Skylake) with 16G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202508180834.3b8fe9d6-lkp@intel.com
2025-08-16 15:56:36 export TEST_DIR=/fs/sda1
2025-08-16 15:56:36 export TEST_DEV=/dev/sda1
2025-08-16 15:56:36 export FSTYP=xfs
2025-08-16 15:56:36 export SCRATCH_MNT=/fs/scratch
2025-08-16 15:56:36 mkdir /fs/scratch -p
2025-08-16 15:56:36 export SCRATCH_DEV=/dev/sda4
2025-08-16 15:56:36 export SCRATCH_LOGDEV=/dev/sda2
2025-08-16 15:56:36 export SCRATCH_XFS_LIST_METADATA_FIELDS=u3.sfdir3.hdr.parent.i4
2025-08-16 15:56:36 export SCRATCH_XFS_LIST_FUZZ_VERBS=random
2025-08-16 15:56:36 echo xfs/177
2025-08-16 15:56:36 ./check xfs/177
FSTYP -- xfs (non-debug)
PLATFORM -- Linux/x86_64 lkp-skl-d06 6.17.0-rc1-00011-g69f6747d99d0 #1 SMP PREEMPT_DYNAMIC Sat Aug 16 23:40:03 CST 2025
MKFS_OPTIONS -- -f /dev/sda4
MOUNT_OPTIONS -- /dev/sda4 /fs/scratch
xfs/177 - output mismatch (see /lkp/benchmarks/xfstests/results//xfs/177.out.bad)
--- tests/xfs/177.out 2025-07-14 17:48:52.000000000 +0000
+++ /lkp/benchmarks/xfstests/results//xfs/177.out.bad 2025-08-16 15:57:27.495121515 +0000
@@ -2,11 +2,14 @@
new file count is in range
inodes after creating files is in range
Round 1
-inodes after bulkstat is in range
+inodes after bulkstat has value of 4
+inodes after bulkstat is NOT in range 1023 .. 1033
inodes after expire is in range
...
(Run 'diff -u /lkp/benchmarks/xfstests/tests/xfs/177.out /lkp/benchmarks/xfstests/results//xfs/177.out.bad' to see the entire diff)
HINT: You _MAY_ be missing kernel fix:
f38a032b165d xfs: fix I_DONTCACHE
Ran: xfs/177
Failures: xfs/177
Failed 1 of 1 tests
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20250818/202508180834.3b8fe9d6-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-08-18 6:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 8:52 Zihuan Zhang
2025-08-14 9:02 ` Viresh Kumar
2025-08-14 9:24 ` Zihuan Zhang
2025-08-14 9:31 ` Viresh Kumar
2025-08-14 9:57 ` Zihuan Zhang
2025-08-18 6:54 ` kernel test robot [this message]
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=202508180834.3b8fe9d6-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=rafael@kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=zhangzihuan@kylinos.cn \
--cc=zhenglifeng1@huawei.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
all inboxes | Powered by JetHome®