All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nivedita Singhvi <niv@us.ibm.com>
To: Sean Dague <sean@dague.net>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>, xen-devel@lists.xensource.com
Subject: Re: Re: help with bugs
Date: Thu, 04 Aug 2005 13:49:36 -0700	[thread overview]
Message-ID: <42F27F60.3020401@us.ibm.com> (raw)
In-Reply-To: <20050804201841.GA17269@underhill.no-ip.org>

Sean Dague wrote:

> On Thu, Aug 04, 2005 at 04:04:34PM +0100, Ian Pratt wrote:
> 
>>
>>I'd like to appeal for some help tracking down a couple of bugs that
>>we're struggling to reproduce:
>>
>> BUG62  eth0 -> veth0 in network script can loose network

Yep, working on this one. --Nivedita

I didn't see your original mail, so not sure if you listed
any others - but was workin on 103 which seems to have gone
awayin current code (we're trying to narrow it to the
NET GRANT code (not yet confirmed).

> I can make this bug come and go at will based on which of the 2 network
> interfaces are part of the bridge.  I added that information into the
> bugzilla bug, hopefully that helps.


>> BUG130 time running fast bug
>> BUG76  shared irq's fail under high load
>>

thanks,
Nivedita

  reply	other threads:[~2005-08-04 20:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-04 15:04 help with bugs Ian Pratt
2005-08-04 19:53 ` Anthony Liguori
2005-08-04 20:18 ` Sean Dague
2005-08-04 20:49   ` Nivedita Singhvi [this message]
2005-08-04 20:54     ` Jerone Young
2005-08-04 20:59       ` Nivedita Singhvi
2005-08-04 20:49 ` David F Barrera
2005-08-05  8:29 ` Gerd Knorr
  -- strict thread matches above, loose matches on Subject: below --
2005-08-04 22:00 Ian Pratt
2005-08-04 23:48 Ian Pratt
2005-08-05 12:23 ` Sean Dague
2005-08-05 14:09 Ian Pratt

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=42F27F60.3020401@us.ibm.com \
    --to=niv@us.ibm.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=sean@dague.net \
    --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.