Re: [lkp-robot] [locking/ww_mutex] 857811a371: INFO:task_blocked_for_more_than#seconds

From	Chris Wilson <chris@chris-wilson.co.uk>
Newsgroups	linux.kernel
Subject	Re: [lkp-robot] [locking/ww_mutex] 857811a371: INFO:task_blocked_for_more_than#seconds
Date	2017-03-08 13:20 +0100
Message-ID	<tiIJs-6r7-19@gated-at.bofh.it> (permalink)
References	<tiyqJ-7Bf-3@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Wed, Mar 08, 2017 at 09:08:54AM +0800, kernel test robot wrote:
> 
> FYI, we noticed the following commit:
> 
> commit: 857811a37129f5d2ba162d7be3986eff44724014 ("locking/ww_mutex: Adjust the lock number for stress test")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
> 
> in testcase: boot
> 
> on test machine: qemu-system-i386 -enable-kvm -m 320M
> 
> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):

Now the test is running, it takes too long. :)

wait_for_completion_interruptible() would stop the hung task check? That
leaves NMI watchdog to check if we hit a deadlock between the workers.

And add a timeout to the stress test.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Re: [lkp-robot] [locking/ww_mutex]  857811a371:  INFO:task_blocked_for_more_than#seconds Chris Wilson <chris@chris-wilson.co.uk> - 2017-03-08 13:20 +0100
  Re: [lkp-robot] [locking/ww_mutex]  857811a371:  INFO:task_blocked_for_more_than#seconds Fengguang Wu <fengguang.wu@intel.com> - 2017-03-08 16:30 +0100
  Re: [locking/ww_mutex] 857811a371 INFO: task swapper/0:1 blocked for  more than 120 seconds. Boqun Feng <boqun.feng@gmail.com> - 2017-03-10 10:50 +0100

csiph-web