https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255104
Mark Johnston changed:
What|Removed |Added
Assignee|b...@freebsd.org|ma...@freebsd.org
Stat
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255104
Joshua Kinard changed:
What|Removed |Added
Keywords|needs-patch |
--- Comment #22 from Joshua Kinar
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255104
--- Comment #21 from Joshua Kinard ---
(In reply to Mark Johnston from comment #14)
> I suspect this bug is the same as the one fixed by
> https://cgit.freebsd.org/src/commit/?id=a1fadf7de25b973a308b86d04c4ada4fa8be193f
> . I've merged it
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255104
--- Comment #20 from Michael Meiszl ---
No, there was no INVARIANT stuff in the git-ted sources.
I added them now an restart from scratch...
will report later.
can take some time, the machine is needed for the next 2 hours, no risk, no
rebo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255104
--- Comment #19 from Mark Johnston ---
(In reply to Michael Meiszl from comment #18)
Assuming you do not already have it on, please compile an INVARIANTS kernel
following the steps here, and try again:
https://lists.freebsd.org/pipermail/fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255104
--- Comment #18 from Michael Meiszl ---
maybe someone has an educated guess what the difference for ipfw is between
started from rc script at boot time or started later on by root from the
console???
The only thing I can think off is a mis
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255104
--- Comment #17 from Michael Meiszl ---
followed your orders. installed git, fetched everything and built a new kernel
(the wanted changes are included, but the file is not really the same as the
other article showed, so there must be more
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255104
--- Comment #16 from Mark Johnston ---
(In reply to Michael Meiszl from comment #15)
freebsd-update can only be used to update to a new release or apply
security/errata patches. The aforementioned patch will be released as an
erratum but t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255104
--- Comment #15 from Michael Meiszl ---
I would volunteer to test it, but "freebsd-update fetch" does not offer me
anything to patch !?!?!?
What am I supposed to do to test it?
--
You are receiving this mail because:
You are the assignee
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255104
Mark Johnston changed:
What|Removed |Added
CC||ma...@freebsd.org
Stat
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255104
--- Comment #13 from Jack ---
I recall previous statement about net.link.ether.ipfw=0 not causing crash, the
server just mysteriously crashed again even with that setting changed.
--
You are receiving this mail because:
You are the assign
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255104
--- Comment #12 from Jack ---
My machine has been crashing nonstop every few hours. I changed
net.link.ether.ipfw=1 to 0 and it hasn't crashed in 19 hours so far. Maybe
related to that sysctl?
--
You are receiving this mail because:
You a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255104
--- Comment #11 from Michael Meiszl ---
Update: started manually, the machine ran for 24hrs like a charm!
maybe somebody else should try this simple trick (set firewall to NO in
rc.conf, reboot, login in and do "service ipfw onestart") and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255104
--- Comment #10 from Michael Meiszl ---
Created attachment 224413
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=224413&action=edit
compressed crashlog
compressed crashlog
--
You are receiving this mail because:
You are the as
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255104
--- Comment #9 from Michael Meiszl ---
yeah, I was too optimistic :-(
It worked, but only unless I did a firewall_enable="YES" into rc.conf and
rebootet :-(
Soon after the reboot the machine got locked up again, only the reset key
helped me
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255104
--- Comment #8 from Michael Meiszl ---
Updated info: I once more tried to update the "real machine", disabling ipfw
during the update process
This worked (like it did before already).
Then I deleted all "table" rules, converting the more th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255104
Jack changed:
What|Removed |Added
CC||xxjack1...@gmail.com
--- Comment #7 from Ja
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255104
--- Comment #6 from Michael Meiszl ---
the sad news is that my freshly installed testmachine does not show up any
problems (yet).
So far, ipfw has not really anything to filter on it, the packets are just
passed on.
I will try to create a m
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255104
Joshua Kinard changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255104
--- Comment #4 from Michael Meiszl ---
Because playing around with a mission critical machine is no real option, I
have set up some old hardware directly with 13.0 and try to reproduce the
crashes. But it will take some time because I have
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255104
--- Comment #3 from Michael Meiszl ---
*** Bug 255295 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255104
Michael Meiszl changed:
What|Removed |Added
CC||mich...@meiszl.de
--- Comment #2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255104
--- Comment #1 from Joshua Kinard ---
Created attachment 224146
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=224146&action=edit
Config for my CUSTOM-13_0 kernel (autogenerated dump from a crash)
Copied from one of the /var/cra
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255104
Bug ID: 255104
Summary: FreeBSD 13.0-RELEASE panic/crash with
ipfw/dummynet/divert & wlan
Product: Base System
Version: 13.0-STABLE
Hardware: Any
OS:
24 matches
Mail list logo
