From: "Christopher S. Aker" <caker@theshore.net>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: xming <xmingske@gmail.com>, virtualization@lists.linux-foundation.org
Subject: Re: Xen paravirt frontend block hang
Date: Mon, 28 Jan 2008 20:04:36 -0500 [thread overview]
Message-ID: <479E7BA4.5050306@theshore.net> (raw)
In-Reply-To: <479E75E3.6030601@goop.org>
Jeremy Fitzhardinge wrote:
> 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?
Looks like my tree has this changeset already (stock 2.6.24), so that's
not it :/ ... I'll try flooding the console with output.
For what it's worth, it does it on both non-smp and smp compiled domU
kernels. smp kernels continue to function after triggering the hang,
however one CPU gets stuck in iowait -- but I am able to continue to
read from the xvd device.
Are you able to reproduce it with the shell script I provided? It takes
maybe 3 or 4 times through the loop to trigger.
-Chris
next prev parent reply other threads:[~2008-01-29 1:04 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
2008-01-29 1:04 ` Christopher S. Aker [this message]
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-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 ` [Xen-devel] " Christopher S. Aker
2008-03-02 16:03 ` 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=479E7BA4.5050306@theshore.net \
--to=caker@theshore.net \
--cc=jeremy@goop.org \
--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.