All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Christopher S. Aker" <caker@theshore.net>
Cc: xming <xmingske@gmail.com>, virtualization@lists.linux-foundation.org
Subject: Re: Xen paravirt frontend block hang
Date: Mon, 28 Jan 2008 16:40:03 -0800	[thread overview]
Message-ID: <479E75E3.6030601@goop.org> (raw)
In-Reply-To: <479E71B7.7060207@theshore.net>

Christopher S. Aker 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).
>
> Were you able to give this a try?  Still doing it on pv_ops 2.6.24.

Hm.  xming reported similar symtoms to your report, which turned out to 
be a result of problems with events getting lost.  This patch - which is 
in 2.6.24 - resolved the issue.  Stock 2.6.24 still has this problem for 
you?  Can you also reproduce it with lots of console output?

Thanks,
    J


changeset:   76060:66bba82b6e9b
parent:      76048:e10ad8f96525
user:        Jeremy Fitzhardinge <jeremy@goop.org>
date:        Wed Jan 23 18:04:54 2008 -0800
files:       arch/x86/xen/enlighten.c
description:
xen: disable vcpu_info placement for now

There have been several reports of Xen guest domains locking up when
using vcpu_info structure placement.  Disable it for now.

Signed-off-by: Jeremy Fitzhardinge <jeremy@xensource.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

committer: Linus Torvalds <torvalds@woody.linux-foundation.org>


diff -r e10ad8f96525 -r 66bba82b6e9b arch/x86/xen/enlighten.c
--- a/arch/x86/xen/enlighten.c  Wed Jan 23 09:58:55 2008 -0800
+++ b/arch/x86/xen/enlighten.c  Wed Jan 23 18:04:54 2008 -0800
@@ -95,7 +95,7 @@ struct shared_info *HYPERVISOR_shared_in
  *
  * 0: not available, 1: available
  */
-static int have_vcpu_info_placement = 1;
+static int have_vcpu_info_placement = 0;
 
 static void __init xen_vcpu_setup(int cpu)
 {

  reply	other threads:[~2008-01-29  0:40 UTC|newest]

Thread overview: 32+ 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
2008-01-29  0:22   ` Christopher S. Aker
2008-01-29  0:40     ` Jeremy Fitzhardinge [this message]
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-02-28 20:03               ` Jeremy Fitzhardinge
2008-02-28 20:03                 ` Jeremy Fitzhardinge
2008-03-18 16:02               ` Jeremy Fitzhardinge
2008-02-28 20:00 ` Jeremy Fitzhardinge
2008-02-28 20:00 ` Jeremy Fitzhardinge
2008-02-28 20:00   ` Jeremy Fitzhardinge
2008-03-02  0:43   ` Christopher S. Aker
2008-03-02  0:43   ` Christopher S. Aker
2008-03-02  0:43     ` Christopher S. Aker
2008-03-02 15:35     ` Jeremy Fitzhardinge
2008-03-02 15:35     ` Jeremy Fitzhardinge
2008-03-02 15:35       ` Jeremy Fitzhardinge
2008-03-02 16:03       ` Christopher S. Aker
2008-03-02 16:03       ` Christopher S. Aker
2008-03-02 16:03         ` Christopher S. Aker
2008-03-18 16:01         ` [Xen-devel] " Jeremy Fitzhardinge
2008-03-18 16:01         ` Jeremy Fitzhardinge
2008-03-18 16:01           ` Jeremy Fitzhardinge
2008-03-25  1:37           ` [Xen-devel] " Christopher S. Aker
2008-03-25  1:37           ` Christopher S. Aker
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=479E75E3.6030601@goop.org \
    --to=jeremy@goop.org \
    --cc=caker@theshore.net \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=xmingske@gmail.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.