https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=150917
Eugene Grosbein changed:
What|Removed |Added
Resolution|--- |FIXED
See Also|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257195
Kubilay Kocak changed:
What|Removed |Added
Severity|Affects Only Me |Affects Some People
F
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257286
Kubilay Kocak changed:
What|Removed |Added
Keywords||easy, regression
Severit
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257195
--- Comment #20 from iron.ud...@gmail.com ---
(In reply to commit-hook from comment #19)
Just tested your patch. The server doesn't panic. All seems good.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257285
--- Comment #7 from Deyan ---
(In reply to Mark Johnston from comment #4)
I suppose it was the 13.0 RELEASE
I followed this manual:
https://docs.freebsd.org/doc/6.1-RELEASE/usr/share/doc/handbook/kernelconfig-building.html
Procedure 2. Bui
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257285
--- Comment #6 from Deyan ---
(In reply to Mark Johnston from comment #5)
I have such a rule in ipfw:
${fw} 500 divert natd ip from any to any in via ${oif}
my natd.conf has these lines:
interface ${natd_interface}
dynamic yes
unregistere
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257195
Michael Tuexen changed:
What|Removed |Added
Status|Open|In Progress
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257195
--- Comment #19 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=a730d82378d3cdf5356775ec0c23ad2ca40c5edb
commit a730d82378d3cdf5356775ec0c23ad2ca40c5edb
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257285
--- Comment #5 from Mark Johnston ---
Hmm, ipdivert might be a red herring, I didn't notice the large offset before:
#7 0xffc0319f at ip_divert_event_tag+0xe29cc977
Assuming that you are in fact using divert sockets though (e.g., some ipf
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257285
--- Comment #4 from Mark Johnston ---
(In reply to Deyan from comment #2)
Which branch did you build the kernel from?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257286
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257285
--- Comment #3 from Deyan ---
I just managed to apply patches up to p3.
freebsd-update output said:
The following files will be updated as part of updating to
13.0-RELEASE-p3:
/bin/freebsd-version
/boot/kernel/if_vlan.ko
/boot/kernel/ipdiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257285
Mark Linimon changed:
What|Removed |Added
Keywords||panic
Assignee|b...@freeb
Hello,
I have a set of NFS(v3) client/server machines which have been working fine
for me for the last years. However, lately the client side sometimes
complains about:
---
Jul 15 01:41:55 client kernel: nfs server server:/data:
lockd not responding
Jul 15 01:41:55 client kernel: nfs server serve
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257268
Gordon Bergling changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
Keywo
15 matches
Mail list logo
