[Bug 261690] NFSv4 mount on Linux client hangs during complex access patterns (gcc bootstrapping on client)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261690 --- Comment #3 from Joshua Kinard --- (In reply to Björn Fischer from comment #1) You might want to see if Ubuntu has pulled in the latest updates from the Linux 5.4.y stable/longterm series. It looks like a number of race conditions in the NFS4 and packet processing layers were caught by syzkaller runs and fixed in the last few 5.4 LTS updates. My scenario, running 5.4.179, the oopses I mentioned have seemingly left as mysteriously as they arrived, so my thinking is the flaw was on the Linux-side and not on the FreeBSD-side. It's possible those fixes may have resolved your case as well. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 253862] prometheus_sysctl_exporter outputs invalid format
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253862 Thomas Steen Rasmussen / Tykling changed: What|Removed |Added CC||tho...@gibfest.dk --- Comment #7 from Thomas Steen Rasmussen / Tykling --- This is still an issue on 13-STABLE as of a few days ago. It is outputting data which is not valid - it doesn't work. The workaround by Lapo Luchini in comment #5 works, but this behaviour should be built into the prometheus_system_exporter itself. The program could/should maintain a list of keys already output and skip if duplicates are found. I don't have time to look at creating a patch right now, hopefully someone else does :) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 246670] bsdtar: Fails to extract (UTF-8) under QEMU_EMULATING
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246670 Charlie Li changed: What|Removed |Added CC||port...@freebsd.org Attachment #231791||maintainer-approval?(portmg Flags||r...@freebsd.org) --- Comment #9 from Charlie Li --- Created attachment 231791 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=231791&action=edit set C.UTF-8 as ports tree locale Following bug 246618, comment 10, as FreeBSD 11 has been EOL. A number of ports are affected. At least the ones I use or otherwise known: * textproc/py-sphinx * devel/py-wheel * sysutils/py-ansible-core -- You are receiving this mail because: You are the assignee for the bug.
[Bug 246670] bsdtar: Fails to extract (UTF-8) under QEMU_EMULATING
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246670 Danilo G. Baio changed: What|Removed |Added Assignee|b...@freebsd.org|port...@freebsd.org --- Comment #10 from Danilo G. Baio --- (In reply to Charlie Li from comment #9) More examples can be found here (Just check the build logs): https://portsfallout.com/fallout?category=extract -- You are receiving this mail because: You are the assignee for the bug.
[Bug 261928] drm-kmod / vt newcons: Loading the drm-kmod driver creates a gap in the vt newcons scrollback buffer
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261928 Bug ID: 261928 Summary: drm-kmod / vt newcons: Loading the drm-kmod driver creates a gap in the vt newcons scrollback buffer Product: Base System Version: Unspecified Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: sblachm...@gmail.com When the drm-kmod driver (i915kms, radeonkms, amdgpu) is kldloaded, a big gap in the vt newcons scrollback buffer is being created. There are almost a screenful of blank lines being inserted when the screen is being resized. This does not create an impression of careful programming, in particular when also taking into consideration that old output is being overwritten at (possibly random) positions (see PR261641: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261641 ). Instead of this behavior, the output should just be continued where the current printing position in the console was before loading the drm-kmod driver. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 224496] mpr and mps drivers seems to have issues with large seagate drives
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224496 leopoldo.20b75...@mailbeaver.net changed: What|Removed |Added CC||leopoldo.20b7513b@mailbeave ||r.net --- Comment #53 from leopoldo.20b75...@mailbeaver.net --- I just started experiencing this issue with my setup with 3 IBM M1015 HBAs and ST1NM002G SAS drives. Has anyone tested their setup with TrueNAS Scale? Since the platform is based on Linux I was hoping this bug was not present. I may try switching when Scale is out of RC status later this month. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 261935] Point bin/date/date.1 to strftime(3) directly instead of through strptime(3) for the +"..." format reference.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261935 Bug ID: 261935 Summary: Point bin/date/date.1 to strftime(3) directly instead of through strptime(3) for the +"..." format reference. Product: Documentation Version: Latest Hardware: Any OS: Any Status: New Keywords: needs-patch Severity: Affects Only Me Priority: --- Component: Manual Pages Assignee: b...@freebsd.org Reporter: paua...@gundo.com CC: d...@freebsd.org date(1) refers the reader to strptime(3) for a description of the format characters, and that in turn sends the reader to strftime(3) for that info. I'd refer the reader to strftime(3) directly instead, or in addition if there's a reason I'm missing to point to strptime(3). -- You are receiving this mail because: You are the assignee for the bug.
[Bug 261728] If sh became a usable interactive shell, then why can't it tab-autocomplete file.(mine).1.txt and file.(mine).2.txt?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261728 --- Comment #9 from Oleg --- (In reply to Daniel Tameling from comment #8) Thanks! -- You are receiving this mail because: You are the assignee for the bug.
Problem reports for b...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- New |197876 | [devfs] an error in devfs leads to data loss and New |198797 | [PATCH] Added an option to install BSDstats to bs New |202362 | ntp: restore refclocks selection (10.2-RELEASE re New |202740 | vi/ex string substitution problem when there is m New |204097 | witness_initialize() does not perform bound check New |206336 | [patch] usr.sbin/freebsd-update allow proxy confi New |209213 | UEFI Loader shows only black screen with Nvidia G New |210804 | installerconfig - using ZFS create in custom scri New |223470 | freebsd-update: Cannot identify running kernel (/ New |230620 | "install -d" issue New |235085 | [PATCH] Option to make rc.d/sysctl more verbose ( New |252123 | fetch(3): Fix wrong usage of proxy when request i Open|177821 | sysctl: Some security.jail nodes are funky, dupli Open|182466 | [headers] [patch] make self-contained Open|183618 | [panic] Dell PowerEdge R620 -- PERC H710 Mini (mf Open|187015 | agpgart: Panic make_dev_credv: bad si_name (error Open|192573 | Add ps(1) option: Print process start time in sec Open|194925 | [pf] [ifconfig] interface group keywords do not w Open|197921 | scheduler: Allow non-migratable threads to bind t Open|206528 | Emulex LPe 16002 FC HBA Not Recognized by oce(4) Open|206649 | cyapa(4): Add common gestures for Cypress APA I2C Open|207940 | stand/efi/boot1: Add boot partition selection Open|212608 | sockstat(1) and lsof(8) can not identity the owne Open|220246 | syslogd does not send RFC3164-conformant messages Open|221305 | Mouse cursor loss when moving cursor while loadin Open|221550 | kern.bootfile returns only /kernel on mips64 (ERL Open|221854 | makefs: Reject UFS labels that are too long to fi Open|226893 | freebsd-update: Support patchlevel argument for f Open|231810 | [build] release always fails with "mkimg: partiti Open|233578 | Unprivileged local user can prevent other users l Open|233988 | freebsd-update: Improve progress output on termin Open|236718 | system panics with message: vm_fault_hold: fault Open|237287 | moused(8) ignores button release events in virtua Open|237924 | Possible infinite loop in function empty_aux_buff Open|238183 | cam/scsi/scsi_sa.c: warnings issued by static ana Open|238486 | Possible buffer overflow bug in sc_allocate_keybo Open|238550 | Touchpad (via SMBus) not working: Synaptics (SYN1 Open|238638 | mfi: Remove unnecessary pointer printing in mfi.c Open|238837 | init: Remove P_SYSTEM flag from PID 1 to allow ea Open|241697 | i915kms: Kernel panic loading module on custom ke Open|247132 | Fix build error: use of undeclared identifier 'cp Open|248352 | mfi(4): Remove RAID map sync functionality Open|257149 | CFLAGS not passed to whole build New |260138 | TPM2 Support in bootloader / kernel in order to r New |261306 | Geli rc.d script does not support insertion of US Open|179832 | manual page of mac_from_text suggests incorrect f 46 problems total for which you should take action.
[Bug 261939] Kerberized NFS mount requires the gssd to be restarted
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261939 Bug ID: 261939 Summary: Kerberized NFS mount requires the gssd to be restarted Product: Base System Version: Unspecified Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: misc Assignee: b...@freebsd.org Reporter: rmack...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug.
[Bug 261939] Kerberized NFS mount requires the gssd to be restarted
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261939 --- Comment #1 from Rick Macklem --- Created attachment 231803 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=231803&action=edit Modify rc.d/gssd so that daemon starts after NETWORKING, kdc Arno Tuber reported via email that he had to restart the gssd daemon after booting, to get a Kerberized NFS mount to work. When I did an rcorder in /etc/rc.d, I noticed that the gssd would start before NETWORKING and the kdc. The latter would only matter if the KDC is on the same machine, but the gssd will need to use NETWORKING to communicate with the KDC. This patch adds NETWORKING and kdc to the REQUIRE line in /etc/rc.d/gssd so that the daemon starts later. Hopefully Arno will be able to test this and report if it fixes the problem for him? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 261939] Kerberized NFS mount requires the gssd to be restarted
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261939 Rick Macklem changed: What|Removed |Added Flags||mfc-stable13?, ||mfc-stable12? Assignee|b...@freebsd.org|rmack...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug.
[Bug 261866] ixgbe(4): Resets media type -> autoselect after setting any other type on Intel 82599ES
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261866 Kubilay Kocak changed: What|Removed |Added CC||kbowl...@freebsd.org, ||n...@freebsd.org, ||rst...@freebsd.org Status|New |Open Assignee|b...@freebsd.org|n...@freebsd.org Keywords||needs-qa Summary|ixgbe(4) with optics not|ixgbe(4): Resets media type |setting media type |-> autoselect after setting ||any other type on Intel ||82599ES Severity|Affects Only Me |Affects Many People Flags||maintainer-feedback?(rstone ||@FreeBSD.org), ||maintainer-feedback?(kbowli ||n...@freebsd.org), ||mfc-stable13?, ||mfc-stable12? --- Comment #1 from Kubilay Kocak --- @Reporter Are you able to test 13-R and/or 14-CURRENT snapshots to confirm reproducibility in those versions? ^Triage: - Request feedback from committer of base r312544 and Kevin -- You are receiving this mail because: You are the assignee for the bug.
[Bug 261895] drm-kmod: Console screen disappears, goes black when loading drm-kmod driver
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261895 Alexey Dokuchaev changed: What|Removed |Added CC||da...@freebsd.org Resolution|--- |Works As Intended Status|New |Closed --- Comment #1 from Alexey Dokuchaev --- Unfortunately, syscons(4) and KMS (kernel mode setting) do not play well together, yet the system doesn't crash or hang, you just get a black screen but you still can type commands. While it does look like a bug, in fact this is documented behavior: https://docs.freebsd.org/en/books/handbook/x11/#x-config-kms -- You are receiving this mail because: You are the assignee for the bug.
[Bug 242457] freebsd-update from 12.0-R to 12.1-R borked base source, rendering system unable to build kernel
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242457 Stefan B. changed: What|Removed |Added Status|New |Closed Resolution|--- |Overcome By Events --- Comment #1 from Stefan B. --- 12.1 no longer supported - closed. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 261889] [PATCH] ucred.9: fix typo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261889 --- Comment #2 from commit-h...@freebsd.org --- A commit in branch stable/13 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=ece3a3facf90aa057fdbe0d0ea6a19444c38d9ca commit ece3a3facf90aa057fdbe0d0ea6a19444c38d9ca Author: Johan Jansson AuthorDate: 2022-02-11 16:46:37 + Commit: Konstantin Belousov CommitDate: 2022-02-14 07:08:51 + ucred.9: fix typo PR: 261889 (cherry picked from commit d4b0fa45dc1531fafb1f3f1a1956056597a4722c) share/man/man9/ucred.9 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 261453] Fix a possible Null pointer dereference in ocs_hw_get_profile_list_cb()
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261453 --- Comment #4 from commit-h...@freebsd.org --- A commit in branch stable/12 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=9199f5e0ba5c20e2f170b549a743a550d9b38ec8 commit 9199f5e0ba5c20e2f170b549a743a550d9b38ec8 Author: Ram Kishore Vegesna AuthorDate: 2022-02-09 10:14:12 + Commit: Ram Kishore Vegesna CommitDate: 2022-02-14 07:11:11 + ocs_fc: Fix a possible Null pointer dereference Fix a possible Null pointer dereference in ocs_hw_get_profile_list_cb() PR: 261453 Reported by: lwhsu MFC after: 3 days (cherry picked from commit 7bf31432fd03e2a5a815d1cc81de9a7b1ea3d3ca) sys/dev/ocs_fc/ocs_hw.c | 5 + 1 file changed, 5 insertions(+) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 261453] Fix a possible Null pointer dereference in ocs_hw_get_profile_list_cb()
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261453 --- Comment #5 from commit-h...@freebsd.org --- A commit in branch stable/13 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=2748f68db95e2e921814472f9c1b77ef49b8fde6 commit 2748f68db95e2e921814472f9c1b77ef49b8fde6 Author: Ram Kishore Vegesna AuthorDate: 2022-02-09 10:14:12 + Commit: Ram Kishore Vegesna CommitDate: 2022-02-14 07:12:55 + ocs_fc: Fix a possible Null pointer dereference Fix a possible Null pointer dereference in ocs_hw_get_profile_list_cb() PR: 261453 Reported by: lwhsu MFC after: 3 days (cherry picked from commit 7bf31432fd03e2a5a815d1cc81de9a7b1ea3d3ca) sys/dev/ocs_fc/ocs_hw.c | 5 + 1 file changed, 5 insertions(+) -- You are receiving this mail because: You are the assignee for the bug.
