mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.de>
To: "Chen, Rong A" <rong.a.chen@intel.com>,
	Nikolay Borisov <nborisov@suse.com>
Cc: lkp@01.org, Stephen Rothwell <sfr@canb.auug.org.au>,
	Yoon Jungyeon <jungyeon@gatech.edu>,
	David Sterba <DSterba@suse.com>,
	Johannes Thumshirn <jthumshirn@suse.de>,
	LKML <linux-kernel@vger.kernel.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 22:29:18 +0800	[thread overview]
Message-ID: <5b82b026-bdd7-f781-e661-f1afdc9cb97b@suse.de> (raw)
In-Reply-To: <7a6c000e-c523-382a-d13c-790809260e4e@intel.com>



On 2019/4/1 下午10:02,  Chen, Rong A  wrote:
> 
> On 4/1/2019 9:28 PM, Nikolay Borisov wrote:
>>
>> 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>
> 
> 
> Hi,
> 
> We usually use the tool ("bin/lkp qemu -k <bzImage> job-script") to
> reproduce it.  It seems no stack trace in the result:

So there is no regression at that commit right?

Just some false alert?

Thanks,
Qu

> 
> $ lkp qemu -k vmlinuz-5.0.0-rc8-00196-g70d28b0 job-script
> ...
> Formatting '/tmp/vdisk-nfs/disk-vm-snb-quantal-x86_64-1415-0', fmt=qcow2
> size=274877906944 cluster_size=65536 lazy_refcounts=off refcount_bits=16
> Formatting '/tmp/vdisk-nfs/disk-vm-snb-quantal-x86_64-1415-1', fmt=qcow2
> size=274877906944 cluster_size=65536 lazy_refcounts=off refcount_bits=16
> exec command: qemu-system-x86_64 -enable-kvm -fsdev
> local,id=test_dev,path=/home/nfs/.lkp//result/trinity/300s/vm-snb-quantal-x86_64/quantal-core-x86_64-2018-11-09.cgz/x86_64-randconfig-s5-03231928/gcc-7/70d28b0e4f8ed2d38571e7b1f9bec7f321a53102/2,security_model=none
> -device virtio-9p-pci,fsdev=test_dev,mount_tag=9p/virtfs_mount -kernel
> vmlinuz-5.0.0-rc8-00196-g70d28b0 -append 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_LOCAL_RUN=1 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 ip=dhcp
> result_service=9p/virtfs_mount -initrd /home/nfs/.lkp/cache/final_initrd
> -smp 2 -m 2048M -no-reboot -watchdog i6300esb -rtc base=localtime
> -device e1000,netdev=net0 -netdev user,id=net0 -display none -monitor
> null -serial stdio -drive
> file=/tmp/vdisk-nfs/disk-vm-snb-quantal-x86_64-1415-0,media=disk,if=virtio
> -drive
> file=/tmp/vdisk-nfs/disk-vm-snb-quantal-x86_64-1415-1,media=disk,if=virtio
> early console in setup code
> Probing EDD (edd=off to disable)... ok
> 
> Best Regards,
> Rong Chen
> 
> 

  reply	other threads:[~2019-04-01 14:29 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
2019-04-01 14:02   ` Chen, Rong A
2019-04-01 14:29     ` Qu Wenruo [this message]
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=5b82b026-bdd7-f781-e661-f1afdc9cb97b@suse.de \
    --to=wqu@suse.de \
    --cc=DSterba@suse.com \
    --cc=jthumshirn@suse.de \
    --cc=jungyeon@gatech.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=nborisov@suse.com \
    --cc=rong.a.chen@intel.com \
    --cc=sfr@canb.auug.org.au \
    /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®