From: kernel test robot <oliver.sang@intel.com>
To: John Ogness <john.ogness@linutronix.de>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
<linux-serial@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [linux-next:master] [serial] d353934702: BUG:kernel_reboot-without-warning_in_test_stage
Date: Thu, 6 Aug 2026 16:42:10 +0800 [thread overview]
Message-ID: <202608061008.48a1e76e-lkp@intel.com> (raw)
Hello,
similar to
https://lore.kernel.org/all/202602271552.c972ef9e-lkp@intel.com/
we still found we have kernel_reboot-without-warning_in_test_stage by this
change in our tests.
hard for us to understand the connection, and we cannot capture more useful
information from serail. just report FYI what we observed in our tests.
kernel test robot noticed "BUG:kernel_reboot-without-warning_in_test_stage" on:
commit: d3539347022ad4eeb9dbd29c50bfca17b9d8a146 ("serial: 8250: Switch to nbcon console, take 2")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
in testcase: boot
config: i386-randconfig-2006-20250825
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/202608061008.48a1e76e-lkp@intel.com
[ 65.107802][ T272] INFO: lkp CACHE_DIR is /tmp/cache
[ 65.107809][ T272]
BUG: kernel reboot-without-warning in test stage
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260806/202608061008.48a1e76e-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-08-06 8:42 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=202608061008.48a1e76e-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=john.ogness@linutronix.de \
--cc=linux-serial@vger.kernel.org \
--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