https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229384
Kubilay Kocak changed:
What|Removed |Added
Status|New |Closed
Flags|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229384
Steven Hartland changed:
What|Removed |Added
CC||s...@freebsd.org
--- Comment #18
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229384
Andres Montalban changed:
What|Removed |Added
CC||amontal...@gmail.com
--- Commen
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229384
--- Comment #16 from commit-h...@freebsd.org ---
A commit references this bug:
Author: loos
Date: Mon Aug 20 01:01:34 UTC 2018
New revision: 338081
URL: https://svnweb.freebsd.org/changeset/base/338081
Log:
MFC r312770 and r337854:
Af
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229384
--- Comment #15 from Kajetan Staszkiewicz ---
No patch I fetched from HEAD made 11.2 fully stable, so yes, none "sounds like
fixing". But I think we are dealing here with two separate bugs.
One is really easy to trigger by just adding same
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229384
--- Comment #14 from Kajetan Staszkiewicz ---
The issues described here happen both on VM and hardware. I switched to testing
things on VMs because they reboot way faster. They do happen on hardware too.
--
You are receiving this mail bec
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229384
Michael changed:
What|Removed |Added
CC||m.mu...@spam-fetish.org
--- Comment #13
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229384
--- Comment #12 from Vinícius Zavam ---
(In reply to Kajetan Staszkiewicz from comment #11)
as I said, the main idea was to get as closest as possible to what we get from
11.2-RELEASE in order to help you (and others). with all respect, th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229384
--- Comment #11 from Kajetan Staszkiewicz ---
The fix is mentioned in my message dated 2018-08-03 15:36:02 UTC. Please stop
fixating on the fact that I have patched kernel and start reading my messages
*thoroughly* instead.
The issue seems
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229384
--- Comment #10 from Vinícius Zavam ---
(In reply to Kajetan Staszkiewicz from comment #9)
good that you really took it personal (although that was not the intention).
the idea was/is to have the closest scenario to reproduce any panic reg
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229384
--- Comment #9 from Kajetan Staszkiewicz ---
Non-patched 11.2-RELEASE-p1 kernel with only change being lines:
options INVARIANTS
options INVARIANT_SUPPORT
in kernel configuration file produces the same result and to cause it
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229384
Kajetan Staszkiewicz changed:
What|Removed |Added
Version|11.1-RELEASE|11.2-RELEASE
--
You are re
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229384
--- Comment #8 from Kajetan Staszkiewicz ---
I can test it again on clean kernel if you wish, but I will compile it with
INVARIANTS nevertheless, as they make the issue pop up immediately.
When it comes to patches, the ones for carp system
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229384
--- Comment #7 from Vinícius Zavam ---
(In reply to Kajetan Staszkiewicz from comment #6)
avoiding the use of rc to setup carp, MFC/MFH direct to 'releng', running your
custom base system and kernel (SomethingCompletelyDifferent)? I would
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229384
--- Comment #6 from Kajetan Staszkiewicz ---
I don't use rc system to configure carps at all. They are done dynamically
whenever required by new configuraion from some external system. I'm not runnig
a clean 11.2-RELEASE. There are some cus
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229384
--- Comment #5 from Vinícius Zavam ---
FreeBSD 11.2-RELEASE #0 r335510: Fri Jun 22 04:32:14 UTC 2018
r...@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 1102000 1102000
root@freebsd-11-2-a:~ # ifconfig | grep carp
carp:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229384
--- Comment #4 from Vinícius Zavam ---
(In reply to Kajetan Staszkiewicz from comment #3)
hey, thanks for the information and more details on this one. appreciated!
would you mind to share your setup a little bit more? like, rc.conf? you
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229384
--- Comment #3 from Kajetan Staszkiewicz ---
Maybe I did not made myself clear. Carp is set up correctly and operates
flawlessly until multiple addresses are added and removed in a short period of
time during some testes which are run on th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229384
Vinícius Zavam changed:
What|Removed |Added
CC||egyp...@googlemail.com
--- Commen
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229384
--- Comment #1 from Kajetan Staszkiewicz ---
The issue of conflicting carps happens on 11.2 too. At this very moment
ifconfig shows correct addresses, though. Can I somehow see which addresses are
used by carp to calculate checksum? I can d
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229384
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receiv
21 matches
Mail list logo
