virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Christopher S. Aker" <caker@theshore.net>
Cc: virtualization@lists.linux-foundation.org
Subject: Re: Xen paravirt frontend block hang
Date: Fri, 28 Dec 2007 22:00:56 -0800	[thread overview]
Message-ID: <4775E298.2000505@goop.org> (raw)
In-Reply-To: <47759EFD.5050101@theshore.net>

Christopher S. Aker wrote:
> Jeremy Fitzhardinge wrote:
>> I'll try to track this down asap.  Have you tried any other kernel
>> versions?  In other words, did it just start happening, or its always
>> done it?  Also, could you try 2.6.24-rc6, just to make sure it hasn't
>> already been fixed (which is possible if its something that happened in
>> a higher layer or something).
>
> I've only just recently started using the paravirt_ops kernels, but
> all the ones I've tried have exhibited the problem, so I'm not sure
> when the hang was introduced.  It doesn't happen with a xensource
> 2.6.18 tree domU.
>
> 2.6.23.8, 2.6.23.12, and 2.6.24-rc6 <-- pv_ops kernels I've tried that
> have the hang.

Yeah, its all fairly new code.  But the pvops blockfront shouldn't have
any functional differences from the 2.6.18 version of the driver, so
something seems to have got broken along the way.

    J

  reply	other threads:[~2007-12-29  6:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-26 19:33 Xen paravirt frontend block hang Christopher S. Aker
2007-12-28 23:14 ` Jeremy Fitzhardinge
2007-12-29  1:12   ` Christopher S. Aker
2007-12-29  6:00     ` Jeremy Fitzhardinge [this message]
2008-01-29  0:22   ` Christopher S. Aker
2008-01-29  0:40     ` Jeremy Fitzhardinge
2008-01-29  1:04       ` Christopher S. Aker
2008-02-06 12:37         ` xming
2008-02-07  4:09           ` Jeremy Fitzhardinge
2008-02-07 14:12             ` xming
2008-02-28 20:03               ` Jeremy Fitzhardinge
2008-03-18 16:02               ` Jeremy Fitzhardinge
2008-02-28 20:00 ` Jeremy Fitzhardinge
     [not found] ` <47C712EF.1060703@goop.org>
2008-03-02  0:43   ` Christopher S. Aker
     [not found]   ` <47C9F818.4020200@theshore.net>
2008-03-02 15:35     ` Jeremy Fitzhardinge
     [not found]     ` <47CAC931.1000107@goop.org>
2008-03-02 16:03       ` Christopher S. Aker
     [not found]       ` <47CACFBE.5010007@theshore.net>
2008-03-18 16:01         ` [Xen-devel] " Jeremy Fitzhardinge
     [not found]         ` <47DFE75B.7080404@goop.org>
2008-03-25  1:37           ` Christopher S. Aker

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=4775E298.2000505@goop.org \
    --to=jeremy@goop.org \
    --cc=caker@theshore.net \
    --cc=virtualization@lists.linux-foundation.org \
    /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;
as well as URLs for NNTP newsgroup(s).