From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: pvops domu soft lockup under load (more logs) Date: Thu, 15 Apr 2010 10:21:21 -0700 Message-ID: <4BC74B11.7080206@goop.org> References: <2F17645D-999B-435C-97EE-508D39B71035@panelsix.com> <4BBF7550.6070807@goop.org> <1C3B7CF5-5772-4D88-9EBF-F7F71BBA710D@openpanel.com> <4BC5FFF6.3090703@goop.org> <5D538568-D29B-40DB-BEE8-240429C97044@panelsix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5D538568-D29B-40DB-BEE8-240429C97044@panelsix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Pim van Riezen Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 04/15/2010 03:56 AM, Pim van Riezen wrote: > On Apr 14, 2010, at 19:48 , Jeremy Fitzhardinge wrote: > > >> Does it appear on the Xen console (visible with "xm dmesg")? You may >> need to do a sysrq '9' first to get it to output all messages. >> > Does that sysrq have to go to dom0 or to the domU? > To the locked-up domU. > I also got the tip from someone on xen-users to take a look at the clock source, and setting /sys/devices/system/clocksource/clocksource0/current_clocksource to 'jiffies' does seem to stop the lockups from happening. The fact that I've witnessed other kernel timekeeping going wonky on these guests, the fact that this helps does seem intuitively right, but I don't know if it gives you enough to work with. > I've seen similar lockups at a very low rate. The clocksource workaround just confuses me; the whole thing stumps me. The main piece of evidence I haven't managed to get yet is a complete process dump (sysrq-t) to see who's waiting on what. Also, could you try 2.6.32.11, which has some timer-related fixes in it, that may or may not help. J