https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606
Kristof Provost changed:
What|Removed |Added
Resolution|--- |Overcome By Events
S
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606
--- Comment #28 from punkt.de Hosting Team ---
I guess someone with the necessary superpowers should close this. Correct?
Kind regards,
Patrick
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606
Mark Linimon changed:
What|Removed |Added
Keywords||patch
--
You are receiving this ma
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606
--- Comment #27 from Kristof Provost ---
(In reply to punkt.de Hosting Team from comment #25)
I'd try reverting this:
https://svnweb.freebsd.org/base?view=revision&revision=313050 and seeing if you
can reproduce it then.
I do not understand
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606
--- Comment #26 from punkt.de Hosting Team ---
Created attachment 187326
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=187326&action=edit
Diff of if_bridge.c for 11.0 and 11.1
--
You are receiving this mail because:
You are th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606
--- Comment #25 from punkt.de Hosting Team ---
Hey guys,
I am trying to reproduce the problem on a not yet productive server.
Un(?)fortunately this system is rock-stable for almost two weeks now.
I just noticed that this test system runs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606
--- Comment #24 from punkt.de Hosting Team ---
Created attachment 187001
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=187001&action=edit
`netstat -m` output while the bridge is in wedged state
--
You are receiving this mail b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606
--- Comment #23 from punkt.de Hosting Team ---
Hey guys,
it hit us again in production. Saturday night, 4am. Sorry - I missed that
DTrace diagnose, but I can add two things at least:
We are using igb(4) interfaces in that machine, not ix(
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606
--- Comment #22 from Kristof Provost ---
(In reply to punkt.de Hosting Team from comment #21)
That should tell us if the problem is specific to the ix cards, or not. If it's
not it's most likely a bridge issue.
It might be worth taking a l
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606
--- Comment #21 from punkt.de Hosting Team ---
Hi, all,
to recapitulate, our symptoms are
* no traffic reaching the jails and their epair(4) interfaces across the
bridge, anymore
* same for outbound traffic from the jails to the wire
* ne
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606
--- Comment #20 from Fabian Keil ---
Created attachment 186372
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=186372&action=edit
ElectroBSD r323013-16c8587cb1b5 dmesg on HP Proliant
TL;DR: I'm attaching a dmesg output as request
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606
--- Comment #19 from Eric Joyner ---
(In reply to Kristof Provost from comment #18)
I don't really have any, either. :p
@Fabian, can you report your system configuration (network card, OS, boot
dmesg, driver versions), too? I'm going to a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606
Kristof Provost changed:
What|Removed |Added
CC||e...@freebsd.org
--- Comment #18
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606
--- Comment #17 from punkt.de Hosting Team ---
Hi there,
we applied Fabian's patches for TCP and if_bridge (thanks!) but unfortunately
the production server's jails came to a halt again last night. Depending on
your point of view at a fort
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606
--- Comment #16 from Fabian Keil ---
Created attachment 185916
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=185916&action=edit
Set UMA_ZONE_NOFREE and preallocate zone item(s)
I've been using the attached workaround in Electro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606
--- Comment #15 from Kurt Jaeger ---
See
https://lists.freebsd.org/pipermail/freebsd-stable/2017-August/087723.html
for another report which looks similar.
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606
--- Comment #14 from Aiko Barz ---
Maybe nothing you like to hear, but I tried the pufferfish.
It is running for some days now without issues so far and it handles the
workload quite well. We cannot utilize the full 10Gbit/s at the moment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606
Fabian Keil changed:
What|Removed |Added
CC||f...@fabiankeil.de
--- Comment #13 f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606
--- Comment #12 from Aiko Barz ---
I am sorry…
We had a spontaneous failover[1] at Saturday once more. Since I installed the
latest firmware blobs for every piece of hardware, what can I do now? I don't
find anything in the logs. It just s
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606
--- Comment #11 from Aiko Barz ---
I installed the latest firmware (17.5.10) on those Intel X520 10G cards today.
Dell replied within 10 minutes(!) with a bootable ISO image, which was able to
do those nasty firmware updates incrementally(
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606
--- Comment #10 from Aiko Barz ---
One (possibly stupid) question:
ifconfig does not list LRO. That means, it is not enabled on those cards.
Right?
sysctl lists some LRO values like lro_flushed and lro_queued. They are all zero
though.
I
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606
--- Comment #9 from Aiko Barz ---
(In reply to Aiko Barz from comment #8)
The Lifecycle method does not work at the moment. But I installed the firmware
version 16.5.20 from 05/12/2016. That firmware was offered as a Redhat shell
script pa
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606
--- Comment #8 from Aiko Barz ---
(In reply to Andrey V. Elsukov from comment #7)
We did not have those issues with 10.1. But I keep your advise in mind.
I currently try to upgrade all those firmware-packages. Unfortunately the Dell
Lifec
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606
Andrey V. Elsukov changed:
What|Removed |Added
CC||a...@freebsd.org
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606
--- Comment #6 from Aiko Barz ---
Hardware: Dell PowerEdge R320
* Intel Xeon E5-2430 v2 (2,5GHz, 6C, 15MB Cache, 7,2GT/s QPI, 80W, Turbo)
* PowerEdge R320 Mainboard, TPM
* Intel Ethernet I350 DP 1Gbit/s Serveradapter, Low Profile
* Intel X5
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606
--- Comment #5 from Kristof Provost ---
Right, that confirms we're not dealing with a memory leak.
I've had a quick look at the ixgbe/if_ix code. It resets the hardware if you
bring it down, so one possible explanation is that there's somet
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606
--- Comment #4 from Aiko Barz ---
Yesterday the other bridge stopped working. Here is the memory situation of the
not working device:
$ sysctl hw | egrep 'hw.(phys|user|real)'
hw.physmem: 17095405568
hw.usermem: 14090272768
hw.realmem: 171
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606
--- Comment #3 from Kristof Provost ---
It doesn't look like it's running out of memory. It'd be good to confirm this
when it's in the faulty state, just to be sure.
--
You are receiving this mail because:
You are the assignee for the bug
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606
--- Comment #2 from Aiko Barz ---
Today the other Bridge-Server had this issue.
But I forget to collect the memory situation before applying the workaround. :(
My current workaround:
$ ifconfig ix0 down
$ ifconfig ix0 up
$ ifconfig ix1 dow
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606
Kristof Provost changed:
What|Removed |Added
CC||k...@freebsd.org
--- Comment #1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217606
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org|freebsd-net@FreeBSD.org
--
You are
31 matches
Mail list logo
