linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ye Xiaolong <xiaolong.ye@intel.com>
To: Jens Axboe <axboe@fb.com>, Tejun Heo <tj@kernel.org>,
	Fengguang Wu <fengguang.wu@intel.com>
Cc: lkp@01.org, Philip Li <philip.li@intel.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [LKP] [writeback] 8bc4ad9498: INFO: suspicious RCU usage. ]
Date: Thu, 8 Sep 2016 10:04:04 +0800	[thread overview]
Message-ID: <20160908020404.GA12960@yexl-desktop> (raw)
In-Reply-To: <20160908014313.fdebw6ig2m6edy46@wfg-t540p.sh.intel.com>

On 09/08, Fengguang Wu wrote:
>Hi Jens and Tejun,
>
>>The command line was in the original email:
>>
>>$ qemu-system-x86_64 -enable-kvm -cpu Westmere -m 512M
>>
>>And agree, in general it'd be nice if there was a link to the image as
>>well, so that folks can reproduce.
>
>Yes we have a reproduce script internally, however need to polish it
>up and make it general usable by kernel developers.
>
>CC Philip. It'd be helpful to give more priority to the "lkp qemu"
>reproduce command.
>
>For the warning here, it does not depend on any initrd, I just
>confirmed this simple script can reproduce the problem.

Yes, just confirmed that v4.8-rc5 doesn't have this warning, while kernel
for the updated commit (fa0e2cb1af765691fabd329f03cad563a0eebf18) on branch 
wb-buf-throttle could reproduce it.

Thanks,
Xiaolong
>
>-----------------------------------------------------------------------------
>#!/bin/bash
>
>kernel=$1
>
>kvm=(
>       qemu-system-x86_64
>       -enable-kvm
>       -cpu Westmere
>       -kernel $kernel
>       -m 1024
>       -smp 1
>       -device e1000,netdev=net0
>       -netdev user,id=net0
>       -boot order=nc
>       -no-reboot
>       -watchdog i6300esb
>       -watchdog-action debug
>       -rtc base=localtime
>       -nographic
>)
>
>
>append=(
>       ip=::::vm-kbuild-yocto-ia32-17::dhcp
>       root=/dev/ram0
>       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
>       systemd.log_level=err
>       ignore_loglevel
>       earlyprintk=ttyS0,115200
>       console=ttyS0,115200
>       console=tty0
>       vga=normal
>       rw
>)
>
>"${kvm[@]}" -append "${append[*]}"
>-----------------------------------------------------------------------------
>
>Thanks,
>Fengguang

  reply	other threads:[~2016-09-08  2:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-01 10:21 [writeback] 8bc4ad9498: INFO: suspicious RCU usage. ] kernel test robot
2016-09-01 20:13 ` Jens Axboe
2016-09-02 14:56   ` Tejun Heo
2016-09-02 15:36     ` Paul E. McKenney
2016-09-02 15:49       ` Jens Axboe
2016-09-02 17:00         ` Paul E. McKenney
2016-09-02 18:00           ` Tejun Heo
2016-09-07 16:41 ` Tejun Heo
2016-09-07 19:25   ` Jens Axboe
2016-09-08  1:43     ` [LKP] " Fengguang Wu
2016-09-08  2:04       ` Ye Xiaolong [this message]
2016-09-08 15:52         ` Jens Axboe
2016-09-09  0:46           ` Ye Xiaolong

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=20160908020404.GA12960@yexl-desktop \
    --to=xiaolong.ye@intel.com \
    --cc=axboe@fb.com \
    --cc=fengguang.wu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=philip.li@intel.com \
    --cc=tj@kernel.org \
    /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 NNTP newsgroup(s).