https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
--- Comment #37 from commit-h...@freebsd.org ---
A commit references this bug:
Author: mw
Date: Tue May 12 18:44:41 UTC 2020
New revision: 360985
URL: https://svnweb.freebsd.org/changeset/base/360985
Log:
MFC r360777: Optimize ENA Rx ref
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
--- Comment #36 from commit-h...@freebsd.org ---
A commit references this bug:
Author: mw
Date: Thu May 7 11:28:40 UTC 2020
New revision: 360777
URL: https://svnweb.freebsd.org/changeset/base/360777
Log:
Optimize ENA Rx refill for low m
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
--- Comment #35 from Colin Percival ---
I believe that this patch should fix the underlying problem, which is in the
ENA driver: https://reviews.freebsd.org/D24546
If you're able to build a custom kernel, please test that patch and report
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
--- Comment #34 from Leif Pedersen ---
(In reply to Colin Percival from comment #32)
You bet. Sorry, I was away for a few days. I opened
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234838
--
You are receiving this mail because:
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
--- Comment #33 from Mike Walker ---
I'm experiencing packet loss w/ENA & FreeBSD 12.0, relevant bug report here:
bug #234754
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
--- Comment #32 from Colin Percival ---
Leif, could you open a new PR for that and CC me? I'll get some people to look
at it but I think it's an unrelated issue so I don't want to force them to wade
through this entire thread.
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
--- Comment #31 from Leif Pedersen ---
ena in 12.0-RELEASE is still not stable on AWS. We see these kernel messages a
few times per day:
ena_com_prepare_tx() [TID:100766]: Not enough space in the tx queue
ena0: failed to prepare tx bufs
e
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
--- Comment #30 from Richard Paul ---
You'll need to try this out on 12.0 berend I think will be the response.
We have completed our migration to GCP, from AWS, now so can't make any more
progress on this.
--
You are receiving this mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
--- Comment #29 from ber...@pobox.com ---
This is on 11.2-RELEASE-p7.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-virtualization@freebsd.org mailing list
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
ber...@pobox.com changed:
What|Removed |Added
CC||ber...@pobox.com
--- Comment #28
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
--- Comment #27 from Richard Paul ---
@jaehak
That is not this issue and has been rectified already in v12. v12 should be
out in December and this problem will go away for you (and us we're actually
seeing disruption on our production sys
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
jaehak changed:
What|Removed |Added
CC||cran...@gmail.com
--- Comment #26 from ja
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
--- Comment #25 from Richard Paul ---
This has been sat on my to do list for a while. I'm hoping that if I can get
my next job out of the way this week I'll revisit this.
Further to my previous posts we seem to see that on instances faced
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
--- Comment #24 from Alex Dupre ---
A bit OT, but is there a particular reason for the FreeBSD 11.2 AMI to support
C5 instances and not M5?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
--- Comment #23 from p...@nomadlogic.org ---
I have a c5.large ec2 instance i'm running to test this using 12.0-ALPHA5. In
the same VPC I have a system using a xn ethernet interface. I am running
iperf3 between these two systems and gettin
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
--- Comment #22 from Colin Percival ---
(In reply to Ling from comment #21)
I think the up/down state flapping is unrelated to the panics other people were
seeing, so I'd like to know if other people can reproduce the issues they saw.
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
--- Comment #21 from Ling ---
(In reply to Colin Percival from comment #15)
I tested on 12.0-alpha2 and 12.0-alpha5 on c5.large and t3.micro and did not
see any ena up and down message again.
so I think this issue has been fixed.
--
You a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
--- Comment #20 from Leif Pedersen ---
(In reply to Colin Percival from comment #19)
Cool. I may be able to clone that machine to 12 later this week and try to
reproduce it...I need to finish some urgent work first.
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
--- Comment #19 from Colin Percival ---
The reason I was asking about HEAD is that we're currently at 12.0-ALPHA5 --
we're going to have 12.0-RELEASE before the release engineering team goes back
and does the next release from stable/11 (ak
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
Leif Pedersen changed:
What|Removed |Added
CC||l...@ofwilsoncreek.com
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
p...@nomadlogic.org changed:
What|Removed |Added
CC||p...@nomadlogic.org
--- Comme
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
--- Comment #16 from Colin Percival ---
Can anyone reproduce this on HEAD? If this is still broken I'd like to make
sure it's fixed before 12.0-RELEASE, but so far this seems quite elusive.
--
You are receiving this mail because:
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
--- Comment #15 from Colin Percival ---
ENA flapping every 30 minutes is almost certainly due to the MTU being set
thanks to DHCP announcing support for jumbograms. That particular bug is fixed
in HEAD (r333454).
AFAIK this should not cau
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
Ling changed:
What|Removed |Added
CC||i...@gamesofa.com
--- Comment #14 from Ling
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
--- Comment #13 from Richard Paul ---
Okay, so we thought that this was resolved with the move to an R4.2Xlarge. It
wasn't, the server page faulted last night with the same old page fault
process/trap number etc.
Our next approach, I gues
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
--- Comment #12 from Colin Percival ---
Sadly nvme hotplug/unplug is still broken in 11.2 -- unfortunately it turned
out that some of the people who would have been fixing that were also the
people who needed to work on fixing the Spectre/M
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
--- Comment #11 from Richard Paul ---
Hi Colin,
I read the article about these drives earlier this year thanks, (p.s. is this
more usable now in 11.2 or are we still waiting on an ability to hot remove
drives), specifically on this test in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
--- Comment #10 from Colin Percival ---
Have you been attaching/detaching EBS volumes while your [mc]5 instances are
running? AFAIK the nvme driver is completely stable aside from that.
--
You are receiving this mail because:
You are the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
--- Comment #9 from Richard Paul ---
So, I managed to produce sufficient load to force this to happen on an m5.large
instance. I have tried to replicate this on a r4.large instance and have
failed to do so so far but I will keep trying.
A
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
--- Comment #8 from Richard Paul ---
Just to help you out with pts
-
To run the benchmark in pts you need to install it using the
phoronix-test-suite package:
#~ pkg install phoronix-test-suite
#~ phoronix-test
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
--- Comment #7 from Richard Paul ---
I missed a couple of configuration options we'd set:
--
sysctl:
kern.ipc.soacceptqueue: 8192
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
--- Comment #6 from Richard Paul ---
Okay, with a bit of effort and this is testing against the v0.7.0 ENA driver on
FreeBSD 11.1p11 I got a reboot. But this was not easy to get to reproduce.
Here's what I did to get this to die.event
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
--- Comment #5 from Richard Paul ---
Hi Colin,
Thanks for responding to this issue. You're right to point out that this may
be down to the difference in hypervisors. M5 seem to be based on HVM too so
for our purposes maybe moving over to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
--- Comment #4 from Colin Percival ---
Sorry, I'm coming to this late -- somehow I never saw this PR earlier.
It's possible that this is an ENA driver bug, but C5 also has the added
complication of using an entirely different virtualizatio
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
--- Comment #3 from Richard Paul ---
(In reply to Richard Paul from comment #2)
Just a quick grab of our DB server's current throughput with `systat -ifstat
-pps`:
ena0 in 4.498 Kp/s 4.498 Kp/s 279.347 Mp
out
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
Richard Paul changed:
What|Removed |Added
CC||rich...@primarysite.net
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
Terje Elde changed:
What|Removed |Added
CC||te...@elde.net
--- Comment #1 from Te
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org|freebsd-virtualization@Free
38 matches
Mail list logo
