https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256439
--- Comment #30 from crypt47 ---
The server works with this patch for some time. Probably it fixes the problem.
But. Couldn't make a full time testing because the first thing I've noticed was
a broken NAT with pf.:(
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256610
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
Keywords
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241954
--- Comment #9 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=36c7408818c53ae0c1f1aee0250c5d3fe16b06e0
commit 36c7408818c53ae0c1f1aee0250c5d3fe16b06e0
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256439
--- Comment #31 from Mark Johnston ---
(In reply to crypt47 from comment #30)
You mean, there is some new regression in pf when the patch is applied? Are
you still testing 13.0-RELEASE?
--
You are receiving this mail because:
You are on
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254623
Mark Johnston changed:
What|Removed |Added
Status|In Progress |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254015
--- Comment #18 from shamaz.ma...@gmail.com ---
#(In reply to Mark Johnston from comment #17)
The proposed solution works for me, thanks! I was wrong, this is not a bug in
the driver ;)
Is there a chance that it will be committed in releng
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254015
--- Comment #19 from Mark Johnston ---
(In reply to shamaz.mazum from comment #18)
Yes, we will probably release an erratum for this, so it'll be included in
13.0-RELEASE-p3.
--
You are receiving this mail because:
You are on the CC list
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218579
HIROKI MORI changed:
What|Removed |Added
CC||yamori...@yahoo.co.jp
--- Comment #2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218579
--- Comment #22 from Cy Schubert ---
Mine is an Acer 4752, same problem. Windows and Fedora don't have the problem.
This suggests I've missed something in my patch.
But poweroff does work after that initial reboot following WOL. I suspect
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256439
--- Comment #32 from crypt47 ---
I hadn't much time for testing. I've used F13 kernel with F12.2 userland. One
of the jails is setuped to use pf as a NAT. With the test kernel it hadn't
start with error like kernel module is unavailable or
10 matches
Mail list logo
