All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pim van Riezen <pi@openpanel.com>
To: xen-devel@lists.xensource.com
Subject: Re: pvops domu soft lockup under load (more logs)
Date: Mon, 12 Apr 2010 11:44:39 +0200	[thread overview]
Message-ID: <1C3B7CF5-5772-4D88-9EBF-F7F71BBA710D@openpanel.com> (raw)
In-Reply-To: <ADED75B1-732F-4FB0-8643-BDEDB29920F6@panelsix.com>


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 <domain> 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?

Pi

  reply	other threads:[~2010-04-12  9:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-09 13:22 pvops domu soft lockup under load Pim van Riezen
2010-04-09 16:50 ` pvops domu soft lockup under load (more logs) Pim van Riezen
2010-04-09 18:43   ` Jeremy Fitzhardinge
2010-04-10  7:12     ` Pim van Riezen
2010-04-12  9:44       ` Pim van Riezen [this message]
2010-04-14 17:48         ` Jeremy Fitzhardinge
2010-04-15 10:56           ` Pim van Riezen
2010-04-15 17:21             ` Jeremy Fitzhardinge
2010-04-16  7:37               ` Pim van Riezen
2010-04-16  7:55                 ` Pim van Riezen
2010-04-16 15:17                   ` Dan Magenheimer
2010-04-16 16:00                     ` Dan Magenheimer
2010-04-16 15:24                   ` Pim van Riezen
     [not found]                 ` <9D75997F-4855-41A0-B159-18B6A3BFC776@panelsix.com>
2010-04-16 13:25                   ` Pim van Riezen
2010-04-16 20:22                 ` Jeremy Fitzhardinge
2010-04-16 14:20               ` Pim van Riezen
2010-04-16 14:19           ` Pim van Riezen

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=1C3B7CF5-5772-4D88-9EBF-F7F71BBA710D@openpanel.com \
    --to=pi@openpanel.com \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.