linux-um archives
 help / color / mirror / Atom feed
From: Nix <nix@esperi.org.uk>
To: Jeff Dike <jdike@addtoit.com>
Cc: Thomas Gleixner <tglx@timesys.com>,
	user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Lockups with the fixed timer code :/
Date: Tue, 15 Apr 2008 20:47:08 +0100	[thread overview]
Message-ID: <87y77elx37.fsf@hades.wkstn.nix> (raw)
In-Reply-To: <20080414144052.GA7186@c2.user-mode-linux.org> (Jeff Dike's message of "Mon, 14 Apr 2008 10:40:52 -0400")

On 14 Apr 2008, Jeff Dike spake thusly:
> Below is another patch for you to try.  I spent most of last week
> chasing this one.  The symptoms are somewhat similar to yours -
> intermittent UML hangs, although not with UML spinning, and it still
> pings.

Having not quite the same symptoms is interesting.

I added instrumentation to spot huge offsets on the offchance that it
was going negative... whereupon it ceased to hang for an entire week
after a week of dying multiple times a day :/

> The problem is NTP adjusting the multiplier part of the clock-provided
> cycles-to-ns conversion function.  UML pretended to have a ns clock,
> with a multiplier of 1.  When NTP adjusted that down in order to slow
> down the clock, that became 0, and time stopped.

Oh, I didn't think that clock_interval might be *variable*. So much for
my instrumentation hack then. :)

... hang on, wouldn't this only happen if you had NTP running on your
guest? (I don't. For that matter, *why* would you have NTP running on
your guest? The guest just gets the time of day from the host anyway!)

(And why does the clocksource system allow NTP to reduce the clock
interval so far that it becomes zero anyway? Shouldn't this be barred?
What am I missing?)

> The fix below is to switch to a usec clock, with a multiplier of 1000,
> which can be adjusted with much more granualarity.

OK, trying that. (I'll extend the instrumentation patch to watch for
zero cycle_interval as well, and see what happens. With luck nothing
will happen except that the crashes will stop... except that they
already *have* stopped for me. Annoying.)

-- 
`The rest is a tale of post and counter-post.' --- Ian Rawlings
                                                   describes USENET

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2008-04-15 19:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-05 16:45 [uml-devel] Lockups with the fixed timer code :/ Nix
2008-04-14 14:40 ` Jeff Dike
2008-04-15 19:47   ` Nix [this message]
2008-04-15 20:59     ` Ryan Finnie
2008-04-16 19:44     ` Nix
2008-04-24 19:57       ` Nix
2008-04-24 20:37         ` Jeff Dike
2008-04-24 22:18           ` Nix

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=87y77elx37.fsf@hades.wkstn.nix \
    --to=nix@esperi.org.uk \
    --cc=jdike@addtoit.com \
    --cc=tglx@timesys.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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