From: Nix <nix@esperi.org.uk>
To: Jeff Dike <jdike@addtoit.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] actually useful backtrace from a CPU-chewing hang
Date: Fri, 09 May 2008 21:32:54 +0100 [thread overview]
Message-ID: <87fxsr9q15.fsf@hades.wkstn.nix> (raw)
In-Reply-To: <1210353202.31648.8.camel@localhost> (vincent-perrier@club-internet.fr's message of "Fri, 09 May 2008 19:13:22 +0200")
On 9 May 2008, vincent-perrier@club-internet.fr verbalised:
> The download is long, the untar too, but the freeze is garanteed!
If this doesn't work I can give you an account on, hm, the box which
freezes uses a UML for its network link so if you flip the time on it
you'd get cut off... and on the other machine it doesn't freeze at all,
even if I slam the time backwards and forwards in 5s increments
constantly.
I wonder if I have to be pushing network packets around or something
before it goes wrong? (I can certainly send you the binary that's going
wrong for me, and induce a core dump when it's gone wrong and send you
that: it'll be 90Mb+ though. I'm not sure how useful that is.)
--
`If you are having a "ua luea luea le ua le" kind of day, I can only
assume that you are doing no work due [to] incapacitating nausea caused
by numerous lazy demons.' --- Frossie
-------------------------------------------------------------------------
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-09 20:33 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
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 [this message]
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=87fxsr9q15.fsf@hades.wkstn.nix \
--to=nix@esperi.org.uk \
--cc=jdike@addtoit.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