linux-um archives
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: "Bram Matthys (Syzop)" <syzop@vulnscan.org>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] umls unresponsive & consuming 100% cpu time
Date: Tue, 13 May 2008 11:40:33 -0400	[thread overview]
Message-ID: <20080513154033.GA8867@c2.user-mode-linux.org> (raw)
In-Reply-To: <48255FC4.4040805@vulnscan.org>

On Sat, May 10, 2008 at 10:41:40AM +0200, Bram Matthys (Syzop) wrote:
> I also saw this on my console (which does not react either btw), not sure
> when it appeared.. at or very short after/before the time setting:
> Stub registers -
> ~        0 - 621a
> ~        1 - 13
> ~        2 - 621a
> ~        3 - 6215
> ~        4 - 8
> ~        5 - bfae182c
> ~        6 - 0
> ~        7 - 7b
> ~        8 - 7b
> ~        9 - 0
> ~        10 - 0
> ~        11 - ffffffff
> ~        12 - 1000be
> ~        13 - 73
> ~        14 - 200246
> ~        15 - bfae1810
> ~        16 - 7b
> wait_stub_done : failed to wait for SIGTRAP, pid = 26141, n = 26141, errno =
> 0, status = 0x1c7f

For this one, try this patch:

Index: linux-2.6.22/arch/um/os-Linux/skas/process.c
===================================================================
--- linux-2.6.22.orig/arch/um/os-Linux/skas/process.c	2008-04-14 10:44:33.000000000 -0400
+++ linux-2.6.22/arch/um/os-Linux/skas/process.c	2008-05-13 11:37:35.000000000 -0400
@@ -55,7 +55,7 @@ static int ptrace_dump_regs(int pid)
  * Signals that are OK to receive in the stub - we'll just continue it.
  * SIGWINCH will happen when UML is inside a detached screen.
  */
-#define STUB_SIG_MASK (1 << SIGVTALRM)
+#define STUB_SIG_MASK ((1 << SIGVTALRM) | (1 << SIGWINCH))
 
 /* Signals that the stub will finish with - anything else is an error */
 #define STUB_DONE_MASK (1 << SIGTRAP)

I doubt it will fix the time problem.  I'm going to chase vincent's
problem on the assusmption that you're seeing the same thing.  When I
figure that out, we'll see how true that is.


> The old 2.6.20.1 uml's react fine when setting time backwards, btw (well..
> within reasonable limits)

UML got its timekeeping redone as part of the tickless work and I'm
still shaking out bugs...

       	    	       Jeff


-- 
Work email - jdike at linux dot intel dot com

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft 
Defy all challenges. Microsoft(R) Visual Studio 2008. 
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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-05-13 15:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-07 14:00 [uml-devel] umls unresponsive & consuming 100% cpu time Bram Matthys (Syzop)
2008-05-07 20:23 ` Nix
2008-05-08 10:02   ` [SPAM] " Bram Matthys (Syzop)
2008-05-09 15:45 ` Jeff Dike
2008-05-10  8:41   ` [SPAM] " Bram Matthys (Syzop)
2008-05-13 15:40     ` Jeff Dike [this message]
2008-05-14  8:41     ` Sakari Ailus
2008-05-19 16:16       ` Jeff Dike
2008-05-31  9:16         ` Bram Matthys (Syzop)

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=20080513154033.GA8867@c2.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=syzop@vulnscan.org \
    --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