https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261694
--- Comment #3 from igor.polov...@gmail.com ---
when /etc/resolv.conf in jail
nameserver 10.108.1.12 or nameserver 8.8.8.8
getaddrinfo works correctly.
when /etc/resolv.conf in jail
nameserver 127.0.0.1
getaddrinfo hangs on recvfrom with 5-
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261755
--- Comment #6 from Herbert J. Skuhra ---
Is this the correct patch? 'ssh -V' shows 8.7p1 not 8.8p1.
I've tested the patch on two systems. It applies with some whitespace warnings
but otherwise all is OK so far.
/home/herbert/c7d1ed4105bb
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261755
--- Comment #7 from Marek Zarychta ---
Patience is required here. Ed will do MFC of OpenSSH 8.8p1 to stable/13 and not
only ssh will be updated but also libs required to have 2FA ssh with FIDO2
support will be added. It's going to be a set
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261771
--- Comment #5 from Louis ---
Created attachment 231634
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=231634&action=edit
dmesg.boot as requested
Here the requested dnesg.boot file
--
You are receiving this mail because:
You a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261771
--- Comment #6 from Louis ---
Created attachment 231635
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=231635&action=edit
Requested PCI-config file
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261771
--- Comment #7 from Louis ---
I did attach the requested files and here also the result of uname -a
uname -a
FreeBSD truenas.pc.lan 13.0-STABLE FreeBSD 13.0-STABLE #0
truenas/13-stable-c073d5cd0: Sun Feb 6 01:31:09 EST 2022
r...@tnbu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261711
--- Comment #2 from Volker ---
okay, sorry for the delay but now i have tested with an plain freeBSD
13-release (no opnsense offset). same result, VXLAN over wireguard isnt working
now. here is my test environment config:
system1:
- netwo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261711
--- Comment #3 from Volker ---
i have add an fix and define the MTU value for both wireguard interfaces to
1420 and VXLAN to 1370. but nothing changed...
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261291
--- Comment #12 from Alan Somers ---
I reproduced the issue again. Deliberately this time, by downing one leg of
the LAGG during high traffic. This time I tailored the packet capture more
narrowly, so it didn't drop any packets (the origi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261728
Daniel Tameling changed:
What|Removed |Added
CC||tamelingdan...@gmail.com
--- Com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261794
Bug ID: 261794
Summary: graphics/drm-kmod or x11-drivers/xf86-driver-intel?
Xorg does not come up in screen native resolution.
Product: Base System
Version: Unspecified
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260116
Björn Svensson changed:
What|Removed |Added
Attachment #231307|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261781
--- Comment #1 from Konstantin Belousov ---
I do not understand what are you saying.
If scale * delta overflows, which we detect by calculating
ffsl(scale) + fls(delta), we do more complicated calculation that moves
overflow to bt->sec, an
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261694
--- Comment #4 from igor.polov...@gmail.com ---
https://forums.freebsd.org/threads/jail-network-interface-lo.76054/post-468396
"Jails don't need a lo(4) interface. They'll work just fine without it. But
keep in mind that there's no 127.0.0.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261781
--- Comment #2 from Jaroslaw Pelczar ---
(In reply to Konstantin Belousov from comment #1)
scale = 295147905178
ffsl(295147905178) = 2
scale_bits = 2
delta = 64100295
fls(delta) = 26
2 + 26 < 63 => but overflow occurs.
--
You are recei
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260116
--- Comment #8 from Björn Svensson ---
I have noted that the non-blocking section
(https://datatracker.ietf.org/doc/html/rfc6458#section-3.2) mention that an
application should use caution when writing to a 1-to-many style socket and
using
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260116
--- Comment #9 from Michael Tuexen ---
(In reply to Björn Svensson from comment #8)
I think for 1-to-1 style sockets it should work and it worked (I think) until
the socket layer in FreeBSD was changed. I'll look into the patch soon.
--
Y
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260116
Michael Tuexen changed:
What|Removed |Added
Assignee|b...@freebsd.org|tue...@freebsd.org
--
You are re
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261781
--- Comment #3 from Konstantin Belousov ---
I see, do you mean the following:
diff --git a/lib/libc/sys/__vdso_gettimeofday.c
b/lib/libc/sys/__vdso_gettimeofday.c
index c1457a54d37e..cf1400cdf291 100644
--- a/lib/libc/sys/__vdso_gettimeofda
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261781
--- Comment #4 from Jaroslaw Pelczar ---
(In reply to Konstantin Belousov from comment #3)
Yes, it seems to do the trick :) I tested such fix locally for 8 hours and it
looks like it works fine.
--
You are receiving this mail because:
Yo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261781
--- Comment #5 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=a1f9326607dea5ab6979935e3ca2d7402dcc7cc1
commit a1f9326607dea5ab6979935e3ca2d7402dcc7cc1
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261728
--- Comment #7 from Oleg ---
As I said in my previous message, sh doesn't like * either. Maybe some other
special characters besides }, ), and * need to be added to your the patch?
Thanks! Hopefully, when you make additional changes to your
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261803
Bug ID: 261803
Summary: System hang under load (possibly only when running
bhyve)
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261781
Kubilay Kocak changed:
What|Removed |Added
Assignee|b...@freebsd.org|k...@freebsd.org
Keyword
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261755
Kubilay Kocak changed:
What|Removed |Added
Status|New |Open
Keywords|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261291
--- Comment #13 from Rick Macklem ---
Ok, I looked and this time the packet trace makes it clear.
The ESXi client is broken.
If you look at the seqid after the clientid in packet #477
(the Exchange_ID reply), you will see it is 0.
If you
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261291
--- Comment #14 from Alan Somers ---
Great find! We are following up with VMWare now. About that error code
though, if I'm reading the RFC correctly, it seems like we should send
NFS4ERR_SEQ_MISORDERED instead of NFS4ERR_STALE_CLIENTID, a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261291
--- Comment #15 from Rick Macklem ---
Well, deciding what the correct error is can be fun.
Here's the definition of NFS4ERR_SEQ_MISORDERED
in RFC5661:
15.1.11.8. NFS4ERR_SEQ_MISORDERED (Error Code 10063)
The requester sent a Sequence o
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247829
Kubilay Kocak changed:
What|Removed |Added
Assignee|b...@freebsd.org|a...@freebsd.org
Flag
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261291
--- Comment #16 from Rick Macklem ---
Created attachment 231662
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=231662&action=edit
return NFSERR_SEQMISORDERED for CREATE_SESSION with wrong seqid
This patch changes the NFSv4.1/4.2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261808
Bug ID: 261808
Summary: zfs's rc.d script doesn't work with "late" devices
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
S
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261808
--- Comment #1 from Daniel Engberg ---
The log is from FreeBSD 13-STABLE (about 2 days ago) using a RockPro64
(aarch64) but the rc.d is the same in -CURRENT so the same issue exists there
too as far as I can tell.
--
You are receiving thi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261679
--- Comment #3 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=3e4e8d5cbfcd2161d7cdd513ad9d7d88f703fcb8
commit 3e4e8d5cbfcd2161d7cdd513ad9d7d88f703fcb8
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261794
--- Comment #1 from Stefan B. ---
Found the cause of this issue:
Unlike with radeonkms/andgpu and nvidia drivers, the Intel driver does _not_
ignore the HorizSync and VertRefresh ranges in the xorg.conf file, even if the
EDID information te
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261794
Stefan B. changed:
What|Removed |Added
Keywords||i915
Summary|graphics/drm-k
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261808
--- Comment #2 from Daniel Engberg ---
Hmm.. I guess there's something else going on, delaying the execution of the
script doesn't help.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261763
Ed Maste changed:
What|Removed |Added
CC||ema...@freebsd.org
--- Comment #1 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261751
Ed Maste changed:
What|Removed |Added
CC||ema...@freebsd.org
--- Comment #1 from
38 matches
Mail list logo
