[Bug 264114] panic: vm_fault_lookup: fault on nofault entry, addr: 0 (wireguard)

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264114 Bug ID: 264114 Summary: panic: vm_fault_lookup: fault on nofault entry, addr: 0 (wireguard) Product: Base System Version: 13.1-RELEASE Hardware: i386

[Bug 188220] freebsd-update(8) destroys installation

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188220 Glen Barber changed: What|Removed |Added Status|Open|Closed Resolution|---

[Bug 188220] freebsd-update(8) destroys installation

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188220 --- Comment #6 from Graham Perrin --- (In reply to jonas.bulow from comment #0) Fast forward eight years. Please, have you encountered this bug with any currently supported RELEASE? -- You are receiving this mail because: You are the a

[Bug 264102] ntp: Doesn't support unprivileged ports (works with ntpdate)

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264102 Cy Schubert changed: What|Removed |Added Assignee|b...@freebsd.org|c...@freebsd.org -- You are receivi

[Bug 264102] ntp: Doesn't support unprivileged ports (works with ntpdate)

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264102 --- Comment #3 from Cy Schubert --- You needn't do a time adjustment in your BIOS to make ntpd "work". ntpd was working from the moment it started on your system. However it adjusts time slowly to avoid upsetting applications, like database

[Bug 264102] ntp: Doesn't support unprivileged ports (works with ntpdate)

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264102 Kubilay Kocak changed: What|Removed |Added CC||c...@freebsd.org Summar

[Bug 264030] [tracking] 13.1-RELEASE issue reports

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264030 Kubilay Kocak changed: What|Removed |Added Depends on||264100 Referenced Bugs: https://

[Bug 264021] efi: failed to allocate staging area: 9

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264021 --- Comment #11 from Mark Millard --- (In reply to Mark Millard from comment #10) Hmm: void geli_export_key_metadata(struct preloaded_file *kfp) { struct keybuf *keybuf; keybuf = malloc(GELI_KEYBUF_SIZE); geli_export_key_buff

[Bug 264021] efi: failed to allocate staging area: 9

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264021 --- Comment #10 from Mark Millard --- (In reply to Mark Millard from comment #9) Looking at the information that the armv7 context reported: . . . Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel

[Bug 264021] efi: failed to allocate staging area: 9

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264021 Mark Millard changed: What|Removed |Added CC||marklmi26-f...@yahoo.com --- Commen

[Bug 264108] bectl should probably fail when given an invalid sort property for -c

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264108 Bug ID: 264108 Summary: bectl should probably fail when given an invalid sort property for -c Product: Base System Version: CURRENT Hardware: Any OS:

[Bug 264021] efi: failed to allocate staging area: 9

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264021 Jessica Clarke changed: What|Removed |Added CC||jrt...@freebsd.org --- Comment #8

[Bug 264021] efi: failed to allocate staging area: 9

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264021 Andrew Turner changed: What|Removed |Added CC||and...@freebsd.org --- Comment #7

[Bug 264103] lib32.txz: Includes files from etc/pam.d

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264103 Ed Maste changed: What|Removed |Added Keywords|pkgbase | -- You are receiving this mail becaus

[Bug 264103] lib32.txz: Includes files from etc/pam.d

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264103 --- Comment #2 from Jessica Clarke --- Well, the -i386 libs in /usr/lib/clang are expected, but not the sanitizer headers. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 264103] lib32.txz: Includes files from etc/pam.d

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264103 Ed Maste changed: What|Removed |Added Keywords||pkgbase -- You are receiving this mail

[Bug 264103] lib32.txz: Includes files from etc/pam.d

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264103 Jessica Clarke changed: What|Removed |Added CC||jrt...@freebsd.org --- Comment #1

[Bug 263879] pkgbase removes critical etc files upon upgrade

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263879 --- Comment #1 from Ed Maste --- Cherry-picking part of what you wrote, > to ... upgrade FreeBSD-runtime... pkg deleted ... and reinstalled it, so all > the etc files that it manages get reset to their defaults. This is caused by FreeBSD-

[Bug 264103] lib32.txz: Includes files from etc/pam.d

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264103 Bug ID: 264103 Summary: lib32.txz: Includes files from etc/pam.d Product: Base System Version: 13.1-RELEASE Hardware: Any OS: Any Status: New Severi

[Bug 263897] panic: Memory modified after free 0xffff0000f2ce1000(131072) val=65766964 @

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263897 --- Comment #6 from Martin Filla --- next panic # mmcsd0: Error indicated: 4 Failed mmcsd0: Error indicated: 1 Timeout mmcsd0: Error indicated: 1 Timeout mmcsd0: Error indicated: 1 Timeout mmcsd0: Error indicated: 1 Timeout panic: VERIFY3

[Bug 264102] ntp doesn't support unprivileged ports (works with ntpdate)

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264102 Jonathan Vasquez changed: What|Removed |Added Status|New |Closed Resolution|---

[Bug 264102] ntp doesn't support unprivileged ports (works with ntpdate)

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264102 --- Comment #2 from Jonathan Vasquez --- After manually going back into my BIOS and setting the clock again, I get the following in the base ntpd (which is good): root@leslie:~ # ntpd -q 20 May 11:12:32 ntpd[3993]: ntpd 4.2.8p15-a (1): Sta

[Bug 264021] efi: failed to allocate staging area: 9

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264021 Marek Zarychta changed: What|Removed |Added CC||freebsd-...@freebsd.org --- Comme

[Bug 264102] ntp doesn't support unprivileged ports (works with ntpdate)

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264102 --- Comment #1 from Jonathan Vasquez --- I tested OpenNTPD and I can see if immediately connects to the freebsd ntp pool (Excluding the offset adjustment since -s was removed and it's using an "improved" variation on -s as default, although

[Bug 264021] efi: failed to allocate staging area: 9

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264021 --- Comment #5 from Martin Filla --- (In reply to Danilo Egea Gondolfo from comment #3) This commit is works cb2ae6163174b90e999326ecec3699ee093a5d43 -- You are receiving this mail because: You are the assignee for the bug.

[Bug 264102] ntp doesn't support unprivileged ports (works with ntpdate)

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264102 Bug ID: 264102 Summary: ntp doesn't support unprivileged ports (works with ntpdate) Product: Base System Version: 13.1-STABLE Hardware: Any OS: Any

[Bug 264016] kernel crashes on boot: panic: aprobedone: invalid action state 0xfd

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264016 --- Comment #4 from Sergei Masharov --- I have disconnected all disks from problematic SATA controllers and system was booted without any problems. After that I have connected one disk and system also boot, but with several errors in the c

[Bug 264067] ldconfig: aout is not supported

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264067 --- Comment #6 from p5b2ea8...@t-online.de --- Now after running mergemaster -UFi the ldconfig lines were presented to interact on (among others) Having completed mergemaster and checkig with grep the lines were deleted. Now what to conclu

[Bug 264081] sort -s (i.e., stable sort) does not work correctly

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264081 Kyle Kneisl changed: What|Removed |Added Resolution|--- |Works As Intended Status

[Bug 264029] [patch] truss(1): add ppoll(2) argument decoding

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264029 --- Comment #4 from commit-h...@freebsd.org --- A commit in branch stable/12 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=ca4703ef1f65dbeb8c7870dec7afc7cdf026d217 commit ca4703ef1f65dbeb8c7870dec7afc7cdf026d217 Author:

[Bug 264067] ldconfig: aout is not supported

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264067 --- Comment #5 from p5b2ea8...@t-online.de --- Interesting because this was done: etcupdate extract etcupdate Now I did run etcupdate again. While the process ended with not a single line of output, checking with grep showed that the ldco

[Bug 264029] [patch] truss(1): add ppoll(2) argument decoding

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264029 --- Comment #3 from commit-h...@freebsd.org --- A commit in branch stable/13 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=657219c49dc0c5289245c4817f5691cc0357c6f7 commit 657219c49dc0c5289245c4817f5691cc0357c6f7 Author:

[Bug 260011] Unresponsive NFS mount on AWS EFS

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260011 --- Comment #12 from Alex Dupre --- I happened again, I've attached the outputs of the requested programs. While locked it was continuing to emit the following messages: nfs server fs-xxx.efs.us-east-1.amazonaws.com:/: is alive again nfs

[Bug 260011] Unresponsive NFS mount on AWS EFS

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260011 --- Comment #11 from Alex Dupre --- Created attachment 234053 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=234053&action=edit nfsstat -E -c -- You are receiving this mail because: You are the assignee for the bug.

[Bug 260011] Unresponsive NFS mount on AWS EFS

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260011 --- Comment #10 from Alex Dupre --- Created attachment 234052 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=234052&action=edit netstat -a -- You are receiving this mail because: You are the assignee for the bug.

[Bug 260011] Unresponsive NFS mount on AWS EFS

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260011 --- Comment #9 from Alex Dupre --- Created attachment 234051 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=234051&action=edit procstat -kk -- You are receiving this mail because: You are the assignee for the bug.

[Bug 260011] Unresponsive NFS mount on AWS EFS

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260011 --- Comment #8 from Alex Dupre --- Created attachment 234050 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=234050&action=edit ps axHL -- You are receiving this mail because: You are the assignee for the bug.

[Bug 264094] setting net.inet.tcp.cc.algorithm to htcp triggers panic on the most recent CURRENT

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264094 Michael Tuexen changed: What|Removed |Added CC||tue...@freebsd.org St

[Bug 264094] setting net.inet.tcp.cc.algorithm to htcp triggers panic on the most recent CURRENT

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264094 Marek Zarychta changed: What|Removed |Added Summary|seting |setting |net.in

[Bug 264094] seting net.inet.tcp.cc.algorithm to htcp triggers panic on the most recent CURRENT

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264094 Bug ID: 264094 Summary: seting net.inet.tcp.cc.algorithm to htcp triggers panic on the most recent CURRENT Product: Base System Version: CURRENT Hardware: arm64

[Bug 264021] efi: failed to allocate staging area: 9

2022-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264021 Marek Zarychta changed: What|Removed |Added CC||zarych...@plan-b.pwste.edu.