From: kernel test robot <oliver.sang@intel.com>
To: Yunsheng Lin <linyunsheng@huawei.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>, <oliver.sang@intel.com>
Subject: [linyunsheng:page_frag_v3_0113] 5e887f0037: errno 12 (Cannot allocate memory)
Date: Wed, 7 Feb 2024 14:57:26 +0800 [thread overview]
Message-ID: <202402071438.a5c1b77a-oliver.sang@intel.com> (raw)
Hello,
we reported
"[linyunsheng:page_frag_v3_0113] 5e887f0037: stress-ng.sync-file.ops_per_sec -6.8% regression"
in
https://lore.kernel.org/all/202401312212.f0f4517c-oliver.sang@intel.com/
now we also notice other issues. below FYI.
kernel test robot noticed "errno 12 (Cannot allocate memory)" on:
commit: 5e887f00379ac36883e4ef0ef418b2401686ebc9 ("pcp alloc opt")
https://github.com/gestionlin/linux.git page_frag_v3_0113
in testcase: filebench
version: filebench-x86_64-22620e6-1_20221010
with following parameters:
disk: 1HDD
fs: btrfs
fs2: nfsv4
test: createfiles.f
cpufreq_governor: performance
compiler: gcc-12
test machine: 128 threads 2 sockets Intel(R) Xeon(R) Platinum 8358 CPU @ 2.60GHz (Ice Lake) with 128G 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/202402071438.a5c1b77a-oliver.sang@intel.com
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240207/202402071438.a5c1b77a-oliver.sang@intel.com
(we didn't observe below output on parent commit)
[ 41.525004][ T1410] Job for nfs-server.service canceled.
[ 41.525007][ T1410]
....
[ 42.280398][ T1408] Feb 05 08:22:46 lkp-icl-2sp6 rpc.nfsd[3939]: error starting threads: errno 12 (Cannot allocate memory)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-02-07 6:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202402071438.a5c1b77a-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=linyunsheng@huawei.com \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).