From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: pvops domu soft lockup under load (more logs) Date: Wed, 14 Apr 2010 10:48:38 -0700 Message-ID: <4BC5FFF6.3090703@goop.org> References: <2F17645D-999B-435C-97EE-508D39B71035@panelsix.com> <4BBF7550.6070807@goop.org> <1C3B7CF5-5772-4D88-9EBF-F7F71BBA710D@openpanel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1C3B7CF5-5772-4D88-9EBF-F7F71BBA710D@openpanel.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/12/2010 02:44 AM, Pim van Riezen wrote: > On Apr 10, 2010, at 9:12 , Pim van Riezen wrote: > > >>> When you're getting lockups, could you capture the output of sysrq-t (xm >>> sysrq t, or "Ctrl-O t" on the domain's console)? >>> >> This one is going to be a bit tough. I only get the error after the fact. The domain has multiple vcpu's, so it's usually not apparent that it's hanging, all depending on which process gets stuck. I'll keep poking at it and if I manage to catch it in the act I'll follow up with a sysrq-t. >> > xm sysrq $vps t doesn't seem to add anything to the console. Am I doing it wrong? > 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. J