All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <808588@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 808588] Re: Netperf tests cause i82551 network down
Date: Mon, 06 Feb 2017 22:52:38 -0000	[thread overview]
Message-ID: <20170206225238.6191.8738.malone@wampee.canonical.com> (raw)
In-Reply-To: 20110711030201.19964.12865.malonedeb@gac.canonical.com

The patch mentioned in comment #3 had been included in the kernel here:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=7734f6e6bcd7ba78b00e93e74a4ddafd9886cdea
So I guess we can close this bug nowadays? Or can you still reproduce this issue with the current kernel and current version of QEMU?

** Changed in: qemu
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/808588

Title:
  Netperf tests cause i82551 network down

Status in QEMU:
  Incomplete

Bug description:
  1. boot up a guest with 82551 nic
  # qemu-kvm -net nic,model=i82551 ...
  2. launch netperf server in the guest
  3.on the host 
  for b in 32 64 128 256 512 1024 1460 2048 4096 8192  9000 16384 32768  65495 65507
  do ./netperf -t TCP_STREAM -f m -H <guest ip> -P 0 -l 10 -- -m $b
  done

  for b in 32 64 128 256 512 1024 1460 2048 4096 8192  9000 16384 32768  65495 65507
  do ./netperf -t UDP_STREAM -f m -H <guest ip> -P 0 -l 10 -- -m $b
  done

  
  Result:
  Guest network becomes down

  
  netperf client output:
  ./netperf -t TCP_STREAM -f m -H 10.66.9.39 -P 0 -l 10 -- -m 32
   87380  16384     32    10.97      19.61
  ./netperf -t TCP_STREAM -f m -H 10.66.9.39 -P 0 -l 10 -- -m 64
   87380  16384     64    11.55      79.68
  ./netperf -t TCP_STREAM -f m -H 10.66.9.39 -P 0 -l 10 -- -m 128
   87380  16384    128    10.16      14.20
  ./netperf -t TCP_STREAM -f m -H 10.66.9.39 -P 0 -l 10 -- -m 256
   87380  16384    256    11.17      12.85
  ./netperf -t TCP_STREAM -f m -H 10.66.9.39 -P 0 -l 10 -- -m 512
   87380  16384    512    10.01      16.38
  ./netperf -t TCP_STREAM -f m -H 10.66.9.39 -P 0 -l 10 -- -m 1024
  Interrupted system call
  netperf: remote error 4./netperf -t TCP_STREAM -f m -H 10.66.9.39 -P 0 -l 10 -- -m 1460
  establish control: are you sure there is a netserver listening on 10.66.9.39 at port 12865?
  establish_control could not establish the control connection from 0.0.0.0 port 0 address family AF_UNSPEC to 10.66.9.39 port 12865 address family AF_UNSPEC
  ./netperf -t TCP_STREAM -f m -H 10.66.9.39 -P 0 -l 10 -- -m 2048

  
  qemu debug message:
  ....
  EE100   nic_receive             command 0x0000, link 0x3d3e6822, addr 0xffffffff, size 1518
  EE100   nic_can_receive         0x29a0180
  EE100   nic_receive             0x29a0180 received broadcast, len=60
  EE100   nic_receive             Receive buffer (0 bytes) too small for data (60 bytes); data truncated
  EE100   nic_receive             command 0x8000, link 0x37b32022, addr 0xffffffff, size 0
                                                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  EE100   nic_receive             receive: Running out of frames
                                                   ^^^^^^^^^^^^^^^^^^^^^^^^
  EE100   eepro100_write1         addr=Command/Status+1 val=0x20

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/808588/+subscriptions

  parent reply	other threads:[~2017-02-06 23:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-11  3:02 [Qemu-devel] [Bug 808588] [NEW] Netperf tests cause i82551 network down kongjianjun
2011-07-11  3:02 ` [Qemu-devel] [Bug 808588] " kongjianjun
2011-07-11  3:03 ` kongjianjun
2011-07-11  9:38 ` Amos Kong
2011-07-11 18:29 ` Stefan Weil
2011-07-14  8:16 ` Amos Kong
2017-02-06 22:52 ` Thomas Huth [this message]
2017-09-13  7:45 ` Thomas Huth

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=20170206225238.6191.8738.malone@wampee.canonical.com \
    --to=808588@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.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 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.