All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Thomas Meyer <thomas@m3y3r.de>,
	Anton Ivanov <anton.ivanov@kot-begemot.co.uk>
Cc: "user-mode-linux-devel@lists.sourceforge.net"
	<user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] [PATCH v3] um: Switch clocksource to hrtimers
Date: Sat, 31 Oct 2015 16:21:31 +0100	[thread overview]
Message-ID: <5634DC7B.3010707@nod.at> (raw)
In-Reply-To: <1446304594.3238.11.camel@m3y3r.de>

Am 31.10.2015 um 16:16 schrieb Thomas Meyer:
> mhh. strange. I didn't see this behaviour on my machine, but my machine
> is a rare single core system so, likely a race condition while relaying
> the timer interrupt to the userspace process.

Here I can trigger it by starting UML, logging in and waiting ~5min.
Then i try to run "top" --> top hangs forever.

> But I'm out of ideas how this could happen!

Maybe some stupid timeslice over/underflow.

> what happens when you send the hanging process a SIGVTALRM signal? does
> it proceed correctly?

You mean sending SIGVTALRM to the UML host process?
It runs normally, I can also login on other ttys.

Thanks,
//richard

------------------------------------------------------------------------------
_______________________________________________
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:[~2015-10-31 15:21 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-21  8:42 [uml-devel] [PATCH v3] um: Switch clocksource to hrtimers Anton Ivanov
2015-10-25 18:46 ` Anton Ivanov
2015-10-26 10:12   ` Richard Weinberger
2015-10-29  6:23     ` Anton Ivanov
2015-10-31 13:54       ` Richard Weinberger
2015-10-31 15:10         ` Thomas Meyer
2015-10-31 15:13           ` Richard Weinberger
2015-10-31 15:16             ` Thomas Meyer
2015-10-31 15:21               ` Richard Weinberger [this message]
2015-10-31 15:24                 ` Thomas Meyer
2015-10-31 15:30                   ` Richard Weinberger
2015-10-31 15:44                     ` Thomas Meyer
2015-10-31 16:22                       ` Anton Ivanov
2015-10-31 19:08                         ` Richard Weinberger
2015-10-31 20:17                           ` Anton Ivanov
2015-10-31 19:06                       ` Richard Weinberger
2015-11-02  8:14                 ` Anton Ivanov
2015-11-02  8:37                   ` Richard Weinberger
2015-11-02  8:41                     ` Anton Ivanov
2015-11-02  8:52                       ` Richard Weinberger
2015-11-02  8:57                         ` Anton Ivanov
2015-11-02  9:12                           ` Richard Weinberger
2015-11-02  9:53                             ` Anton Ivanov
2015-11-02 10:01                               ` Richard Weinberger
2015-11-02 10:59                                 ` Anton Ivanov
2015-11-02 11:00                                   ` Anton Ivanov
2015-11-02 14:30                                 ` Anton Ivanov
2015-11-02 15:25                                   ` Richard Weinberger
2015-11-02 16:19                                     ` Anton Ivanov

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=5634DC7B.3010707@nod.at \
    --to=richard@nod.at \
    --cc=anton.ivanov@kot-begemot.co.uk \
    --cc=thomas@m3y3r.de \
    --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 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.