All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: Nix <nix@esperi.org.uk>
Cc: Thomas Gleixner <tglx@timesys.com>,
	user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Lockups with the fixed timer code :/
Date: Thu, 24 Apr 2008 16:37:32 -0400	[thread overview]
Message-ID: <20080424203732.GA11688@c2.user-mode-linux.org> (raw)
In-Reply-To: <87bq3z81q5.fsf@hades.wkstn.nix>

On Thu, Apr 24, 2008 at 08:57:54PM +0100, Nix wrote:
> On 16 Apr 2008, nix@esperi.org.uk stated:
> > This *is* a change in behaviour: the backtrace is different! Yay! :)
> 
> I upgraded the guest to 2.6.25 a week ago and it stopped happening.
> There is hope.  (Mind you it's stopped going wrong for week-long periods
> before...)

OK, yell if it starts happening again...

    	       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

  reply	other threads:[~2008-04-24 20:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-05 16:45 [uml-devel] Lockups with the fixed timer code :/ Nix
2008-04-14 14:40 ` Jeff Dike
2008-04-15 19:47   ` Nix
2008-04-15 20:59     ` Ryan Finnie
2008-04-16 19:44     ` Nix
2008-04-24 19:57       ` Nix
2008-04-24 20:37         ` Jeff Dike [this message]
2008-04-24 22:18           ` Nix

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=20080424203732.GA11688@c2.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=nix@esperi.org.uk \
    --cc=tglx@timesys.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 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.