All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ian.Campbell@eu.citrix.com, konrad.wilk@oracle.com,
	pbonzini@redhat.com, xen-devel@lists.xensource.com
Subject: Re: Prepping a bugfix push
Date: Thu, 03 Dec 2009 15:22:24 -0800	[thread overview]
Message-ID: <4B184830.7070107@goop.org> (raw)
In-Reply-To: <20091203193540.GB4228@kremvax.cs.ubc.ca>

On 12/03/09 11:35, Brendan Cully wrote:
> Not a patch, but I've just tried out xm save -c again with the latest
> xen changes, and while I no longer see the grant table version panic,
> the guest's devices (aside from the console) appear to be wedged on
> resume. Is anyone else seeing this?
>
> After a while on the console I see messages like this:
>
> INFO: task syslogd:2219 blocked for more than 120 seconds.
>
> which I assume is trouble with the block device.
>    

Is there any backtrace or other info associated with this?

     J

  parent reply	other threads:[~2009-12-03 23:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03 19:26 Prepping a bugfix push Jeremy Fitzhardinge
2009-12-03 19:35 ` Brendan Cully
2009-12-03 19:38   ` Jeremy Fitzhardinge
2009-12-03 23:22   ` Jeremy Fitzhardinge [this message]
2009-12-04  0:24     ` Brendan Cully
2009-12-04  1:10       ` Jeremy Fitzhardinge
2009-12-04  4:29         ` Brendan Cully
2009-12-04  7:46         ` Ian Campbell
2009-12-04 15:50           ` Ian Campbell
2009-12-04 16:37             ` Jeremy Fitzhardinge
2009-12-04 16:56               ` Ian Campbell
2009-12-05  0:05                 ` Jeremy Fitzhardinge
2009-12-04 17:01               ` Brendan Cully
2009-12-04 17:12                 ` Jeremy Fitzhardinge
2009-12-04 10:45 ` Ian Campbell
2009-12-04 14:10   ` Konrad Rzeszutek Wilk
2009-12-04 16:18     ` Jeremy Fitzhardinge

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=4B184830.7070107@goop.org \
    --to=jeremy@goop.org \
    --cc=Ian.Campbell@eu.citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=pbonzini@redhat.com \
    --cc=xen-devel@lists.xensource.com \
    /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.