mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ferenc Wagner <wferi@niif.hu>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: linux-kernel@vger.kernel.org, Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: doubled idle count
Date: Sun, 21 Sep 2008 14:05:59 +0200	[thread overview]
Message-ID: <87hc89g0uw.fsf@tac.ki.iif.hu> (raw)
In-Reply-To: Ferenc Wagner's message of "Fri, 19 Sep 2008 18:53:35 +0200"

Ferenc Wagner <wferi@niif.hu> writes:

> Jeremy Fitzhardinge <jeremy@goop.org> writes:
> --text follows this line--
>> Ferenc Wagner wrote:
>>
>>> After upgrading a Xen virtual machine to Debian's 2.6.26-4 kernel, I
>>> noticed that the idle counter doubled its pace on one of the machines:
>>> [...]
>>> One out of three machines show this effect, with the exact same kernel
>>> and Xen versions (3.2.0, dom0 is Debian's stock Etch 2.6.18 kernel).
>>> They aren't hosted by the same machine, though: the misbehaving one is
>>> on a different installation with very similar hardware (3 vs 2 GHz).
>>> All the guest are paravirtual.
>>
>> So you're saying that they are identical Xen and guest kernel binaries,
>> but one of three is showing doubled idle time?
>
> Now I upgraded another domU, and that also shows this doubling effect,
> so I've got two domUs (running on xen2-ha) misbehaving, and other two
> (running on xen2) behaving correctly.

Possibly related: three out of the above four 2.6.26 domUs froze
yesterday afternoon.  The consoles don't show anything and are dead,
they don't react to sysrq, even.  According to xm list, the frozen
domains are constantly running (stuck in r state).

I haven't destroyed them yet, in case it is possible to extract any
info from the system.  If not, please tell me so I can restart them.

On the other hand, I'll have a look whether the same kernel running on
the bare metal produces this idle count discrepancy.
-- 
Thanks,
Feri.

Ps: Please note that xen-devel swallows my mails without a trace,
    probably because I'm not subscribed.

  parent reply	other threads:[~2008-09-21 12:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-18 12:26 Ferenc Wagner
2008-09-18 19:34 ` Jeremy Fitzhardinge
2008-09-18 21:24   ` Ferenc Wagner
2008-09-19 13:20   ` Ferenc Wagner
2008-09-21 12:05   ` Ferenc Wagner [this message]
2008-09-21 12:27   ` Ferenc Wagner
2008-11-07 15:20   ` Ferenc Wagner

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=87hc89g0uw.fsf@tac.ki.iif.hu \
    --to=wferi@niif.hu \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®