linux-um archives
 help / color / mirror / Atom feed
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: Wed, 14 May 2008 21:12:12 +0100	[thread overview]
Message-ID: <87r6c4y7ab.fsf@hades.wkstn.nix> (raw)
In-Reply-To: <20080514193912.GA11531@c2.user-mode-linux.org> (Jeff Dike's message of "Wed, 14 May 2008 15:39:12 -0400")

On 14 May 2008, Jeff Dike verbalised:

> I finally reproduced this using 2.6.25.1 (2.6.25-mm1 was no good) with
> your config.

YAY! (I wonder why this was so .config-dependent? You'd think it would
trigger on anything, but I couldn't even make it happen on all my
hosts...)

> The patch below fixes it for me.  You'll notice a certain similarity
> between this and a previous patch that you posted.  It's not clear to
> me why yours didn't work.

As far as I can tell it's identical in behaviour in the !NO_HZ
case.

Annoyingly, now I've upgraded the host to 2.6.25 (hence sans skas3),
timings or something have changed such that I now can't make the freeze
happen at all. I'll reboot the host into 2.6.24.x shortly to get skas
back and try again.


Oh, and, it's pedantic of me, I know, but what does this do if time goes
backwards in the NO_HZ case? (Or is handling that a 2.6.26 thing?)

-------------------------------------------------------------------------
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-14 20:12 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
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 [this message]
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=87r6c4y7ab.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