From: kernel test robot <oliver.sang@intel.com>
To: Yury Norov <yury.norov@gmail.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>, <oliver.sang@intel.com>
Subject: [norov:bitmap_param] [bitmap] 0ee65b4b68: BUG:unable_to_handle_page_fault_for_address
Date: Fri, 31 Jul 2026 19:47:15 +0800 [thread overview]
Message-ID: <202607311010.9c97983e-lkp@intel.com> (raw)
Hello,
we didn't get too much useful information from dmesg, but seems the issue is
quite persistent with high rate and always clean on parent, so still report out
FYI.
=========================================================================================
tbox_group/testcase/rootfs/kconfig/compiler/sleep:
vm-snb/boot/quantal-i386-core-20190426.cgz/x86_64-randconfig-072-20260723/gcc-14/1
bf7e3686b708683e 0ee65b4b686fb78bda2320d6a70
---------------- ---------------------------
fail:runs %reproduction fail:runs
| | |
:496 50% 249:496 dmesg.BUG:unable_to_handle_page_fault_for_address
kernel test robot noticed "BUG:unable_to_handle_page_fault_for_address" on:
commit: 0ee65b4b686fb78bda2320d6a7002332c41d7537 ("bitmap: use unsigned long for bit indices and sizes")
https://github.com/norov/linux bitmap_param
in testcase: boot
config: x86_64-randconfig-072-20260723
compiler: gcc-14
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 32G
(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/202607311010.9c97983e-lkp@intel.com
[ 128.056595][ C0] BUG: unable to handle page fault for address: fffffffffffffff8
BUG: kernel hang in boot stage
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260731/202607311010.9c97983e-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-31 11:47 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=202607311010.9c97983e-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=yury.norov@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.