From: kernel test robot <oliver.sang@intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Christoph Hellwig <hch@lst.de>, <oliver.sang@intel.com>
Subject: [hch-xfs:xfs-zoned-zwp] [xfs] 6998648bf0: modprobe: ERROR: could not insert 'xfs'
Date: Wed, 28 Feb 2024 15:24:33 +0800 [thread overview]
Message-ID: <202402281423.1b82ee17-oliver.sang@intel.com> (raw)
Hello,
we noticed this is "this is early prototype code", so below report is just FYI
what we observed in our tests.
kernel test robot noticed "modprobe: ERROR: could not insert 'xfs'" on:
commit: 6998648bf0e3fce2d2d3e0f5e092dbd64712cf1c ("xfs: support zoned RT devices")
git://git.infradead.org/users/hch/xfs xfs-zoned-zwp
in testcase: xfstests
version: xfstests-x86_64-c46ca4d1-1_20240205
with following parameters:
disk: 4HDD
fs: xfs
test: generic-group-46
compiler: gcc-12
test machine: 8 threads Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz (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/202402281423.1b82ee17-oliver.sang@intel.com
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240228/202402281423.1b82ee17-oliver.sang@intel.com
[ 59.112427][ T1261] xfs: Unknown symbol bio_add_folio_nofail (err -2)
...
[ 63.929952][ T315] modprobe: ERROR: could not insert 'xfs': Unknown symbol in module, or unknown parameter (see dmesg)
[ 63.929971][ T315]
[ 63.943962][ T315] mount: /fs/sda1: unknown filesystem type 'xfs'.
[ 63.943977][ T315]
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-02-28 7:24 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=202402281423.1b82ee17-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=hch@lst.de \
--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).