qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] TAP network breaks after debugger break-in
Date: Mon, 6 Jul 2015 15:40:52 +0800	[thread overview]
Message-ID: <20150706074052.GD9051@ad.nay.redhat.com> (raw)
In-Reply-To: <20150706073618.GC9051@ad.nay.redhat.com>

On Mon, 07/06 15:36, Fam Zheng wrote:
> On Mon, 07/06 10:27, Max Filippov wrote:
> > On Mon, Jul 6, 2015 at 4:55 AM, Fam Zheng <famz@redhat.com> wrote:
> > > On Sat, 07/04 10:47, Max Filippov wrote:
> > >> Hello,
> > >>
> > >> I'm using QEMU with TAP network and after the commit
> > >> 0a2df857a703 "Merge remote-tracking branch
> > >> 'remotes/stefanha/tags/net-pull-request' into staging"
> > >> I've noticed that activation of debugger connected to QEMU's
> > >> gdbstub during network I/O almost always breaks network
> > >> connection: network stops working completely after return
> > >> from the debugger.
> > >>
> > >> Stefan, Fam, any hint on where to start debugging it?
> > >>
> > >
> > > Which NIC are you using?
> > 
> > opencores_eth.
> > 
> 
> Does reverting a90a7425cf592a3afeff3eaf32f543b83050ee5c work?
> 

Sorry, there are dependencies, I should say "bisect between a90a7425cf5 and
a90a7425cf5^" :)

Fam

  reply	other threads:[~2015-07-06  7:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-04  7:47 [Qemu-devel] TAP network breaks after debugger break-in Max Filippov
2015-07-06  1:55 ` Fam Zheng
2015-07-06  7:27   ` Max Filippov
2015-07-06  7:36     ` Fam Zheng
2015-07-06  7:40       ` Fam Zheng [this message]
2015-07-06  7:45       ` Max Filippov
2015-07-06  7:57         ` Fam Zheng
2015-07-06 11:34           ` Max Filippov
2015-07-06 15:36             ` Stefan Hajnoczi
2015-07-06 15:47               ` Max Filippov

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=20150706074052.GD9051@ad.nay.redhat.com \
    --to=famz@redhat.com \
    --cc=jcmvbkbc@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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 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).