From: Boqun Feng <boqun.feng@gmail.com>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Ingo Molnar <mingo@kernel.org>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
chris@chris-wilson.co.uk, linux-kernel@vger.kernel.org,
LKP <lkp@01.org>
Subject: Re: [locking/ww_mutex] 857811a371 INFO: task swapper/0:1 blocked for more than 120 seconds.
Date: Fri, 10 Mar 2017 17:45:41 +0800 [thread overview]
Message-ID: <20170310094541.4ou4t3iuauqqxjvt@tardis> (raw)
In-Reply-To: <20170310030746.43zyebko27f62ehd@tardis>
[-- Attachment #1: Type: text/plain, Size: 1941 bytes --]
On Fri, Mar 10, 2017 at 11:07:46AM +0800, Boqun Feng wrote:
> On Fri, Mar 10, 2017 at 10:56:49AM +0800, Fengguang Wu wrote:
> > Hi Boqun,
> >
>
> Hello Fengguang,
>
> > FYI here is another bisect result. I report it once again since the
> > attached reproduce-* may be more handy for debug. :)
> >
>
> That's very helpful! lkp is a bit difficult for me to set up ;-)
>
Hmm... hit this when run the reproduce script:
early console in setup code
KVM internal error. Suberror: 3
extra data[0]: 80000306
extra data[1]: 31
RAX=0000000000000000 RBX=ffffffff800c0038 RCX=1ffffffff0d8c301 RDX=dffffc0000000000
RSI=0000000000000001 RDI=ffffffff86c61e78 RBP=ffffffff800c0028 RSP=ffffffff800c0000
R8 =0000000000000001 R9 =0000000000000001 R10=ffffffff85e07bd0 R11=ffffffff85e079d7
R12=0000000000000006 R13=0000000000000003 R14=00000000000199a0 R15=0000000000000001
RIP=ffffffff84a84715 RFL=00010046 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0000 0000000000000000 ffffffff 00000000
CS =0010 0000000000000000 ffffffff 00a09b00 DPL=0 CS64 [-RA]
SS =0000 0000000000000000 ffffffff 00000000
DS =0000 0000000000000000 ffffffff 00000000
FS =0000 0000000000000000 ffffffff 00000000
GS =0000 ffffffff8737a000 ffffffff 00000000
LDT=0000 0000000000000000 ffffffff 00000000
TR =0020 0000000000000000 00000fff 00808b00 DPL=0 TSS64-busy
GDT= ffffffff8738c000 0000007f
IDT= ffffffff877ad000 00000fff
CR0=80050033 CR2=ffff880000014200 CR3=0000000007567000 CR4=000000a0
DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000
DR6=00000000ffff0ff0 DR7=0000000000000400
EFER=0000000000000d01
Code=00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 88 47 a8 84 ff <ff> ff ff 07 67 72 81 ff ff ff ff d0 7a b6 86 ff ff ff ff 79 84 4e 81 ff ff ff ff 8b 25 d2
Using reproduce script for some other kernel is fine. Any idea?
My host is ArchLinux with kernel 4.9.11-1-ARCH.
Regards,
Boqun
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-03-10 9:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 1:08 [lkp-robot] [locking/ww_mutex] 857811a371: INFO:task_blocked_for_more_than#seconds kernel test robot
2017-03-08 12:13 ` Chris Wilson
2017-03-08 14:46 ` Fengguang Wu
2017-03-10 2:56 ` [locking/ww_mutex] 857811a371 INFO: task swapper/0:1 blocked for more than 120 seconds Fengguang Wu
2017-03-10 3:07 ` Boqun Feng
2017-03-10 9:45 ` Boqun Feng [this message]
2017-03-10 10:57 ` [PATCH] locking/ww-mutex: Limit stress test to 2s Chris Wilson
2017-03-30 8:33 ` [tip:locking/core] locking/ww-mutex: Limit stress test to 2 seconds tip-bot for Chris Wilson
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=20170310094541.4ou4t3iuauqqxjvt@tardis \
--to=boqun.feng@gmail.com \
--cc=chris@chris-wilson.co.uk \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®