Path: csiph.com!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From: Richard Cochran <richardcochran@gmail.com>
Newsgroups: linux.kernel
Subject: Re: [patch 4 14/22] timer: Switch to a non cascading wheel
Date: Tue, 16 Aug 2016 11:00:01 +0200
Message-ID: <s6Io1-R5-15@gated-at.bofh.it>
References: <rR8Pv-419-7@gated-at.bofh.it> <rR8Pw-419-35@gated-at.bofh.it> <s505H-5ym-29@gated-at.bofh.it> <s5oUq-4QH-19@gated-at.bofh.it> <s5q9Q-5PW-9@gated-at.bofh.it>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: robomod@news.nic.it
Approved: robomod@news.nic.it
Lines: 21
Organization: linux.* mail to news gateway
Xref: csiph.com linux.kernel:1463558

On Fri, Aug 12, 2016 at 12:14:11PM -0700, Paul E. McKenney wrote:
> FWIW, I do appear to be seeing more lost wakeups on current mainline
> than on v4.7, but not enough of a difference to get a reliable bisction
> in reasonable time.

We are seeing reproducible hangs* when running Steven's
stress-cpu-hotplug under kvm.  This hang goes back to v4.7 at least.
I couldn't reproduce this with bare metal.  Thomas thought it was a
virtualization issue, not related to the hotplug rework.  He is away
until next week.  Maybe he knows more to say...

To reproduce, run 

   while [ 1 ]; do ./stress-cpu-hotplug ; done

and wait about 20 minutes (or longer).

Thanks,
Richard

* INFO: task cpuhp/7:49 blocked for more than 120 seconds