From: Nikolay Borisov <nborisov@suse.com>
To: kernel test robot <rong.a.chen@intel.com>, Qu Wenruo <wqu@suse.com>
Cc: David Sterba <dsterba@suse.com>,
Yoon Jungyeon <jungyeon@gatech.edu>,
Johannes Thumshirn <jthumshirn@suse.de>,
LKML <linux-kernel@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
lkp@01.org
Subject: Re: [btrfs] 70d28b0e4f: BUG:kernel_reboot-without-warning_in_early-boot_stage,last_printk:Probing_EDD(edd=off_to_disable)...ok
Date: Mon, 1 Apr 2019 16:28:12 +0300 [thread overview]
Message-ID: <f3cef716-a1e3-2e84-0133-9a9c3fad2a74@suse.com> (raw)
In-Reply-To: <20190401132427.GC9217@shao2-debian>
On 1.04.19 г. 16:24 ч., kernel test robot wrote:
> FYI, we noticed the following commit (built with gcc-7):
>
> commit: 70d28b0e4f8ed2d38571e7b1f9bec7f321a53102 ("btrfs: tree-checker: Verify dev item")
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
>
> in testcase: trinity
> with following parameters:
>
> runtime: 300s
>
> test-description: Trinity is a linux system call fuzz tester.
> test-url: http://codemonkey.org.uk/projects/trinity/
>
>
> on test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 2G
>
> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
>
>
> +--------------------------------------------------------------------------------------------------------+------------+------------+
> | | 36b9d2bc69 | 70d28b0e4f |
> +--------------------------------------------------------------------------------------------------------+------------+------------+
> | boot_successes | 14 | 0 |
> | boot_failures | 2 | 14 |
> | IP-Config:Auto-configuration_of_network_failed | 2 | |
> | BUG:kernel_reboot-without-warning_in_early-boot_stage,last_printk:Probing_EDD(edd=off_to_disable)...ok | 0 | 14 |
> +--------------------------------------------------------------------------------------------------------+------------+------------+
>
>
>
> early console in setup code
> Probing EDD (edd=off to disable)... ok
> BUG: kernel reboot-without-warning in early-boot stage, last printk: Probing EDD (edd=off to disable)... ok
> Linux version 5.0.0-rc8-00196-g70d28b0 #1
> Command line: ip=::::vm-snb-quantal-x86_64-1415::dhcp root=/dev/ram0 user=lkp job=/lkp/jobs/scheduled/vm-snb-quantal-x86_64-1415/trinity-300s-quantal-core-x86_64-2018-11-09.cgz-70d28b0-20190330-29362-1y6g0qb-2.yaml ARCH=x86_64 kconfig=x86_64-randconfig-s5-03231928 branch=linux-devel/devel-hourly-2019032317 commit=70d28b0e4f8ed2d38571e7b1f9bec7f321a53102 BOOT_IMAGE=/pkg/linux/x86_64-randconfig-s5-03231928/gcc-7/70d28b0e4f8ed2d38571e7b1f9bec7f321a53102/vmlinuz-5.0.0-rc8-00196-g70d28b0 max_uptime=1500 RESULT_ROOT=/result/trinity/300s/vm-snb-quantal-x86_64/quantal-core-x86_64-2018-11-09.cgz/x86_64-randconfig-s5-03231928/gcc-7/70d28b0e4f8ed2d38571e7b1f9bec7f321a53102/8 LKP_SERVER=inn debug apic=debug sysrq_always_enabled rcupdate.rcu_cpu_stall_timeout=100 net.ifnames=0 printk.devkmsg=on panic=-1 softlockup_panic=1 nmi_watchdog=panic oops=panic load_ramdisk=2 prompt_ramdisk=0 drbd.minor_count=8 systemd.log_level=err ignore_loglevel console=tty0 earlyprintk=ttyS0,115200 console=ttyS0,115200 vga=normal rw rcuperf.shutdown=0
>
Can this report be made useful by actually including output from serial
console? For example possible bug-ons or whatnot? dmesg.xz just contains
qemu's command line + some metadata about the test and :
"BUG: kernel reboot-without-warning in early-boot stage, last printk:
Probing EDD (edd=off to disable)... ok"
At least a stack trace would have been useful.
<snip>
next prev parent reply other threads:[~2019-04-01 13:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 13:24 kernel test robot
2019-04-01 13:28 ` Nikolay Borisov [this message]
2019-04-01 14:02 ` Chen, Rong A
2019-04-01 14:29 ` Qu Wenruo
2019-04-01 15:02 ` Chen, Rong A
2019-04-01 15:40 ` David Sterba
2019-04-02 3:14 ` [LKP] [btrfs] 70d28b0e4f: BUG:kernel_reboot-without-warning_in_early-boot_stage, last_printk:Probing_EDD(edd=off_to_disable)...ok Rong Chen
2019-04-02 3:30 ` Qu Wenruo
2019-04-02 4:55 ` Qu Wenruo
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=f3cef716-a1e3-2e84-0133-9a9c3fad2a74@suse.com \
--to=nborisov@suse.com \
--cc=dsterba@suse.com \
--cc=jthumshirn@suse.de \
--cc=jungyeon@gatech.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=rong.a.chen@intel.com \
--cc=sfr@canb.auug.org.au \
--cc=wqu@suse.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®