All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pim van Riezen <pi+lists@panelsix.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: pvops domu soft lockup under load (more logs)
Date: Thu, 15 Apr 2010 12:56:59 +0200	[thread overview]
Message-ID: <5D538568-D29B-40DB-BEE8-240429C97044@panelsix.com> (raw)
In-Reply-To: <4BC5FFF6.3090703@goop.org>


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?

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.

Cheers,
Pim

  reply	other threads:[~2010-04-15 10:56 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
2010-04-14 17:48         ` Jeremy Fitzhardinge
2010-04-15 10:56           ` Pim van Riezen [this message]
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=5D538568-D29B-40DB-BEE8-240429C97044@panelsix.com \
    --to=pi+lists@panelsix.com \
    --cc=jeremy@goop.org \
    --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.