From: "Michael S. Tsirkin" <mst@redhat.com>
To: Leszek Urbanski <tygrys@moo.pl>
Cc: netdev@vger.kernel.org, linux-nfs@vger.kernel.org,
qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org
Subject: [Qemu-devel] Re: BUG - qdev - partial loss of network connectivity
Date: Tue, 28 Sep 2010 11:50:58 +0200 [thread overview]
Message-ID: <20100928095058.GI12472@redhat.com> (raw)
In-Reply-To: <20100927213203.GA28089@moo.pl>
On Mon, Sep 27, 2010 at 11:32:03PM +0200, Leszek Urbanski wrote:
> <20100926154324.GD21843@redhat.com>; from Michael S. Tsirkin on Sun, Sep 26, 2010 at 17:43:24 +0200
>
> > > > >It's vanilla 2.6.32.22, but I also reproduced this on Debian's 2.6.32-23
> > > > >(based on 2.6.32.21).
> > > > >
> > > > >If offload is the only difference, I'll play with different offload
> > > > >options and check which one causes it.
> > > > >
> > > >
> > > > It's not technically the only difference but it's the most likely
> > > > culprit IMHO.
> > >
> > > udp fragmentation offload is definitely the culprit.
> >
> > I see. Most likely guest bug - won't be the first bug around UFO.
> > If so pls copy netdev linux-nfs and virtualization.
> > Do you see anything in dmesg? Can try 2.6.36-rc5?
>
> (for reference: first post is at:
> http://lists.nongnu.org/archive/html/qemu-devel/2010-09/msg01685.html )
>
> I can't reproduce it on 2.6.36-rc5. Do you have an idea which patch may have
> fixed it, or should I dissect?
bisect, yes: there were many UFO related patches since 2.6.32.
--
MST
next prev parent reply other threads:[~2010-09-28 9:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 17:18 [Qemu-devel] BUG - qdev - partial loss of network connectivity Leszek Urbanski
2010-09-22 17:41 ` Anthony Liguori
2010-09-22 18:20 ` Leszek Urbanski
2010-09-22 18:35 ` Anthony Liguori
2010-09-23 14:04 ` Leszek Urbanski
2010-09-26 15:43 ` [Qemu-devel] " Michael S. Tsirkin
2010-09-27 21:32 ` Leszek Urbanski
2010-09-28 9:50 ` Michael S. Tsirkin [this message]
2010-10-05 21:29 ` Leszek Urbanski
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=20100928095058.GI12472@redhat.com \
--to=mst@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=tygrys@moo.pl \
--cc=virtualization@lists.linux-foundation.org \
/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).