https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200319
--- Comment #32 from Palle Girgensohn ---
I just tried to reproduce the problem on FreeBSD-13.0.RELEASE using the
attached script, but it just runs on smoothly. Is there anything else I need to
add to the mix to reproduce the lock-up?
Than
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200319
--- Comment #31 from Palle Girgensohn ---
(In reply to Kristof Provost from comment #30)
Splendid! Then I will try stable/13 and see if that resolves my problems.
Thanks!
--
You are receiving this mail because:
You are on the CC list fo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200319
--- Comment #30 from Kristof Provost ---
(In reply to Palle Girgensohn from comment #29)
I'd expect this issue to have gone away with
fffd27e5f3b9700b6556a8c4fbd9503593a5ba33 (on main,
fffd27e5f3b9700b6556a8c4fbd9503593a5ba33 on stable/13).
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200319
--- Comment #29 from Palle Girgensohn ---
(In reply to Kristof Provost from comment #27)
Can you please just refer to which commit fixes this issue? The locking seems
to be committed last October 2020?
commit 4af1bd81573675599d68069b247c6
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200319
Kubilay Kocak changed:
What|Removed |Added
Keywords|needs-qa|
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200319
Kristof Provost changed:
What|Removed |Added
Resolution|--- |FIXED
Status|Open
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200319
Mark Linimon changed:
What|Removed |Added
Attachment #156928|0 |1
is patch|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200319
--- Comment #26 from Kristof Provost ---
The test script attached to this bug should reproduce the problem. Just make
sure you load the carp module, because the script doesn't.
I also have experimental patches for 12 here:
https://people.f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200319
--- Comment #25 from Palle Girgensohn ---
Hi,
So, I could test the patch in 13-CURRENT?
Do you have a suggestion for reproducing the problem?
Palle
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200319
--- Comment #24 from Kristof Provost ---
(In reply to Palle Girgensohn from comment #23)
If my theory of the problem (in comment #16) is correct it may be resolved by
the bridge performance work (see https://reviews.freebsd.org/D24250 for t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200319
Palle Girgensohn changed:
What|Removed |Added
CC||gir...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200319
--- Comment #22 from Oleg Sharoyko ---
Another workaround is to switch to netgraph. I have eventually did that
(ng_bridge, ng_ether, ng_eiface). I had to write some startup scripts to manage
netgraph topology but my system has been very sta
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200319
Kubilay Kocak changed:
What|Removed |Added
URL|https://reviews.freebsd.org |
|/D3133
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200319
--- Comment #20 from Kristof Provost ---
(In reply to Kristof Provost from comment #19)
I may have been conflating two different issues.
To clarify: if the system fully freezes then these sysctls won't help. If the
system keeps running, bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200319
--- Comment #19 from Kristof Provost ---
(In reply to Gyver Def from comment #18)
The problem is being worked on.
In the mean time the following sysctl tweaks should make the problem less
likely to trigger:
net.isr.bindthreads=1
net.isr.m
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200319
Gyver Def changed:
What|Removed |Added
CC||g...@wp.pl
--- Comment #18 from Gyver
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200319
mlav...@gmail.com changed:
What|Removed |Added
CC||mlav...@gmail.com
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200319
--- Comment #16 from Kristof Provost ---
Thanks Oleg,
The demo script nvass attached also worked for me to trigger the problem. I've
not yet tried your setup, but I'm confident it'll also work.
I think I understand the problem in general
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200319
Oleg Sharoyko changed:
What|Removed |Added
CC||osharo...@gmail.com
--- Comment #1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200319
--- Comment #14 from nv...@gmx.com ---
(In reply to Kristof Provost from comment #13)
At the same time the network stack is not functioning anymore. No IP, ARP, TCP
etc. For example, if you get inside the CARP jails and type "ifconfig bridge
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200319
--- Comment #13 from Kristof Provost ---
(In reply to nvass from comment #12)
For anyone else who wants to try: the script doesn't load the carp module, so
load it manually first.
The manifestation of it isn't exactly what I expected. I do
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200319
--- Comment #12 from nv...@gmx.com ---
Created attachment 201585
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=201585&action=edit
script to demosntrate the carp-on-bridge deadlock
Hi,
I wrote a small script to reproduce the pro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200319
--- Comment #11 from Kristof Provost ---
(In reply to Thomas Steen Rasmussen / Tykling from comment #10)
I'm not too familiar with the relevant code, but if you can create a test
script to reproduce the problem I can try taking a look.
(As
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200319
Thomas Steen Rasmussen / Tykling changed:
What|Removed |Added
CC||tho...@gibfest.d
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200319
--- Comment #9 from Luiz Otavio O Souza,+55 (14) 99772-1255
---
The patch (in that review) is misleading, it fixes the issue by accident.
The right fix needs a bit of work.
pfSense has an updated version of the original workaround, which
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200319
Kubilay Kocak changed:
What|Removed |Added
Flags||mfc-stable11?,
|
On 07/21/15 05:37, Jason Unovitch wrote:
On 07/20/2015 08:26, Nikos Vassiliadis wrote:
Hi,
regarding this bug... When carp information is about to be printed,
it stops. All network activity has stopped by then. For example:
bridge0: flags=8943
metric 0 mtu 1280
ether 02:48:9e:59:98:
On 07/20/2015 08:26, Nikos Vassiliadis wrote:
Hi,
regarding this bug... When carp information is about to be printed,
it stops. All network activity has stopped by then. For example:
bridge0: flags=8943
metric 0 mtu 1280
ether 02:48:9e:59:98:00
inet 156.0.0.2 netmask 0xffc0
Hi,
regarding this bug... When carp information is about to be printed,
it stops. All network activity has stopped by then. For example:
bridge0: flags=8943 metric 0
mtu 1280
ether 02:48:9e:59:98:00
inet 156.0.0.2 netmask 0xffc0 broadcast 156.0.0.63
inet 156.0.0.10
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200319
Hiroki Sato changed:
What|Removed |Added
Assignee|freebsd-net@FreeBSD.org |h...@freebsd.org
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200319
Jason Unovitch changed:
What|Removed |Added
CC||jason.unovi...@gmail.com
--- Comm
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200319
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org|freebsd-net@FreeBSD.org
K
32 matches
Mail list logo
