From: Jeff Dike <jdike@addtoit.com>
To: Nix <nix@esperi.org.uk>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] actually useful backtrace from a CPU-chewing hang
Date: Fri, 2 May 2008 15:57:20 -0400 [thread overview]
Message-ID: <20080502195720.GB10369@c2.user-mode-linux.org> (raw)
In-Reply-To: <87bq3o5yeo.fsf@hades.wkstn.nix>
On Fri, May 02, 2008 at 07:55:11PM +0100, Nix wrote:
> No behavioural change :(
Oh well.
> I'm trying something else now, arranging for os_nsecs() itself to do the
> never-backwards stuff on the assumption that something depends on
> monotonic timers not skipping backwards which presently they might
> (there are callers of os_nsecs() outside of os-Linux/time.c, notably in
> kernel/time.c, and currently they see an unadjusted time, jumping
> backwards and forwards and whatever).
This sounds like a reasonable idea.
Another thing you might try is the following:
get two extra windows
in one, get a "strace -p uml-pid -o strace.out -tt" ready
in two, get a "date ; sudo date -s "now-5 sec" ; date" ready
hit return in one, then in two, then in your UML window
when the UML gives you another prompt (or you've decided it's
hung), ^C the strace
Look at the times reported by the dates, find the time change in the
strace log, and send the section following that (and a bit before) to
me.
Jeff
--
Work email - jdike at linux dot intel dot com
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2008-05-02 19:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-25 19:59 [uml-devel] actually useful backtrace from a CPU-chewing hang Nix
2008-04-25 22:06 ` Nix
2008-04-26 18:31 ` Nix
2008-04-27 14:02 ` Nix
2008-04-28 16:44 ` Jeff Dike
2008-04-30 21:49 ` Nix
2008-05-01 15:13 ` Jeff Dike
2008-05-01 23:34 ` Nix
2008-05-02 16:30 ` Jeff Dike
2008-05-02 18:55 ` Nix
2008-05-02 19:57 ` Jeff Dike [this message]
2008-05-02 23:21 ` Nix
2008-05-03 0:56 ` Jeff Dike
2008-05-03 10:08 ` Nix
2008-05-09 15:16 ` Jeff Dike
2008-05-09 17:13 ` vincent-perrier
2008-05-09 20:32 ` Nix
2008-05-14 17:23 ` Jeff Dike
2008-05-14 18:03 ` vincent-perrier
2008-05-14 18:18 ` vincent-perrier
2008-05-14 18:29 ` vincent-perrier
2008-05-14 19:39 ` Jeff Dike
2008-05-14 20:12 ` Nix
2008-05-14 20:31 ` Nix
2008-05-14 20:43 ` Jeff Dike
2008-05-14 22:02 ` Nix
2008-05-19 18:54 ` [uml-devel] plug_and_play_clownix_network vincent-perrier
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=20080502195720.GB10369@c2.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=nix@esperi.org.uk \
--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