All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christopher S. Aker" <caker@theshore.net>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: xen devel <xen-devel@lists.xensource.com>
Subject: Re: High Net and Disk Use == stuck domain
Date: Mon, 01 Dec 2008 16:00:48 -0500	[thread overview]
Message-ID: <49345080.4070105@theshore.net> (raw)
In-Reply-To: <493446E6.2060706@goop.org>

Jeremy Fitzhardinge wrote:
>> Did this one slip by you?  I figured a reproducible bug would be just 
>> too tantalizing to resist.
> 
> Hoping it would go away by itself? ;)
> 
> I'm trying to repro it now, copying ISOs at 25 Mbytes/sec.  How long 
> does it take to happen?

Under a few minutes, usually within 30 seconds.  The affected kernel 
binary is here:

http://theshore.net/~caker/xen/BUGS/D-state/2.6.27.4-linode14

This was built with my non-broken toolchain, too, btw :)

Meanwhile, I'll try to reproduce it in a new environment and come up 
with a better recipe.

>> What's the correct venue for these issues that overlap xen-devel, 
>> lkml, and virtualization/pv_ops stuff -- should I be blasting these to 
>> everybody?
> 
> Me and xen-devel are a good start, and posting in a bugzilla cc:ing me 
> if it looks like its been dropped on the floor.

OK -- targets acquired!

Thanks,
-Chris

      reply	other threads:[~2008-12-01 21:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-21 16:54 High Net and Disk Use == stuck domain Christopher S. Aker
2008-11-21 17:07 ` Stefan de Konink
2008-11-21 17:16   ` Christopher S. Aker
2008-12-01 15:05 ` Christopher S. Aker
2008-12-01 20:19   ` Jeremy Fitzhardinge
2008-12-01 21:00     ` Christopher S. Aker [this message]

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=49345080.4070105@theshore.net \
    --to=caker@theshore.net \
    --cc=jeremy@goop.org \
    --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.