All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Anton Ivanov <anton.ivanov@kot-begemot.co.uk>,
	Thomas Meyer <thomas@m3y3r.de>
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: Mon, 2 Nov 2015 09:37:14 +0100	[thread overview]
Message-ID: <563720BA.20107@nod.at> (raw)
In-Reply-To: <56371B6D.3080506@kot-begemot.co.uk>

Hi!

Am 02.11.2015 um 09:14 schrieb Anton Ivanov:
> I was testing under similar conditions (CPU pinning using taskset -c 0 on a multicore).
> 
> I have removed it and run some retests - I cannot reproduce the hang at this point with my config
> 
> I am going to run a defconfig and compare the results to see if this will give me any insights on the root cause.

I can reproduce on both my build machine (8 core) and my laptop (4 core).
If it helps I can share the rootfs.

On my laptop I was able to reproduce within 5 minutes.
1. make defconfig ARCH=um
2. make -j 4 linux ARCH=um
3. ./linux ubda=../Downloads/Debian-Squeeze-AMD64-root_fs mem=1G
4. login to tty0
5. wait a few minutes
6. try to run top, it will hang in nanosleep

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-11-02  8:37 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
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 [this message]
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=563720BA.20107@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.