https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203976
Kristof Provost changed:
What|Removed |Added
Resolution|--- |Overcome By Events
S
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203976
Kristof Provost changed:
What|Removed |Added
Blocks||204186
--
You are receiving thi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203976
--- Comment #11 from Kristof Provost ---
To be clear: this panic will not happen on CURRENT, because the code (scrub
crop/drop-ovl) in which it occurs has been removed.
Right now I don't plan to investigate this problem any further.
--
Y
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203976
--- Comment #10 from i...@inbox.ru ---
(In reply to Mark Linimon from comment #9)
I think need kernel fixes to prevent such problems in future.
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203976
--- Comment #9 from Mark Linimon ---
To submitter: so can this PR be closed now?
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing li
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203976
--- Comment #8 from i...@inbox.ru ---
(In reply to Kristof Provost from comment #6)
You were right, i replaced "corp" by "reassemble" - now it works fine.
Thanks a lot!
--
You are receiving this mail because:
You are the assignee for the b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203976
--- Comment #7 from i...@inbox.ru ---
(In reply to Kristof Provost from comment #6)
indeed i use crop. Can't test right at this time since i rolled back to 9.3,
but i'll test it soon and reply results.
--
You are receiving this mail becaus
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203976
--- Comment #6 from Kristof Provost ---
Are you running with 'scrub fragment crop' or 'scrub fragment drop-ovl' by any
chance?
If so, can you confirm that the problem goes away if you switch to 'scrub
fragment reassemble'?
The crop/drop-
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203976
--- Comment #5 from Kristof Provost ---
(In reply to ikv from comment #4)
You can censor the IP addresses, if you like, but knowing what type of scrub
options you've got, and if you're using anything like route-to, dup-to, ... is
quite usef
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203976
--- Comment #4 from i...@inbox.ru ---
(In reply to Kristof Provost from comment #3)
I wont posting my rules. By the way, i have this problem on 2 different systems
with different pf rulesets.
rules are simple - pass, block, nat - nothing ext
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203976
--- Comment #3 from Kristof Provost ---
I'm not suggesting your rules are wrong (the panic should never happen, no
matter what the rules are), but knowing what they are is useful during
debugging.
--
You are receiving this mail because:
Y
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203976
--- Comment #2 from i...@inbox.ru ---
(In reply to Kristof Provost from comment #1)
These rules works fine on freebsd 9.3.
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203976
Kristof Provost changed:
What|Removed |Added
CC||k...@freebsd.org
--- Comment #1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203976
Bug ID: 203976
Summary: panic: page fault on regular traffic routing
Product: Base System
Version: 10.2-RELEASE
Hardware: Any
OS: Any
Status: New
Se
14 matches
Mail list logo
