[Bug 277389] Reproduceable low memory freeze on 14.0-RELEASE-p5
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277389
--- Comment #21 from Mark Millard ---
(In reply to Mark Millard from comment #20)
Hmm. Turns out Wired decreases show in top when top also shows the likes of
(ordered by cpu):
PID JID USERNAMEPRI NICE SIZE RES STATEC TIME CPU
COMMAND
0 0 root 8- 0B6112Ki CPU20 20 0:02 1.19%
[kernel{thread taskq}]
Otherwise [kernel{thread taskq}] is well down the list.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 273665] strlen.3 HISTORY section is truncated
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273665 Wolfram Schneider changed: What|Removed |Added CC||obr...@freebsd.org, ||wo...@freebsd.org Status|New |In Progress URL||https://cgit.freebsd.org/sr ||c/commit/?id=c4ff9276a969a3 ||a691ee1f336ce4ed6c0c9b0b99 --- Comment #5 from Wolfram Schneider --- The fix c4ff9276a969a3a691ee1f336ce4ed6c0c9b0b99 needs to be merged to stable/13 and stable/14 as well. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 277389] Reproduceable low memory freeze on 14.0-RELEASE-p5
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277389 --- Comment #20 from Mark Millard --- (In reply to Mark Millard from comment #19) I updated to a PkgBase vintage of: # uname -apKU FreeBSD 7950X3D-ZFS 15.0-CURRENT FreeBSD 15.0-CURRENT main-n268827-75464941dc17 GENERIC-NODEBUG amd64 amd64 1500015 1500015 and added to /boot/loader.conf : nullfs_load="YES" vfs.nullfs.cache_vnodes=0 I reran the test for such a boot context and the vmstat -z had a notable difference for VNODE, but the Wired value stayed huge. No hangup or OOM activity happened. I'll remind that my prior report had (after the rm): VNODE: 448, 0, 1756979, 325855,17353842, 0, 0, 0 but this test got: VNODE: 448, 0, 836,1846, 43727, 0, 0, 0 Yet: 183850Mi Wired still. [Note added later, well after the below vmstat -z output: it has slowly dropped to 151961Mi Wired and continues to decrease. I'll do another vmstat -z later.] For reference (183850Mi time frame): # rm iozone.DUMMY.* # vmstat -z ITEM SIZE LIMIT USED FREE REQ FAIL SLEEP XDOM kstack_cache: 16384, 0,1865, 4,1933, 0, 0, 0 buffer arena-40: 4096, 0, 0, 0, 0, 0, 0, 0 buffer arena-81: 8192, 0, 0, 0, 0, 0, 0, 0 buffer arena-12: 12288, 0, 0, 0, 0, 0, 0, 0 buffer arena-16: 16384, 0, 10, 0, 10, 0, 0, 0 buffer arena-20: 20480, 0, 0, 0, 0, 0, 0, 0 buffer arena-24: 24576, 0, 0, 0, 0, 0, 0, 0 buffer arena-28: 28672, 0, 0, 0, 0, 0, 0, 0 buffer arena-32: 32768, 0, 1, 0, 1, 0, 0, 0 buffer arena-36: 36864, 0, 0, 0, 0, 0, 0, 0 buffer arena-40: 40960, 0, 0, 0, 0, 0, 0, 0 buffer arena-45: 45056, 0, 0, 0, 0, 0, 0, 0 buffer arena-49: 49152, 0, 0, 0, 0, 0, 0, 0 buffer arena-53: 53248, 0, 0, 0, 0, 0, 0, 0 buffer arena-57: 57344, 0, 0, 0, 0, 0, 0, 0 buffer arena-61: 61440, 0, 0, 0, 0, 0, 0, 0 buffer arena-65: 65536, 0, 0, 0, 0, 0, 0, 0 buf free cache: 432, 0, 11, 199, 11, 0, 0, 0 vm pgcache:4096, 0, 170057, 18447, 315805, 632, 0, 0 vm pgcache:4096, 0,45110709,5482,45353298,2948, 0, 0 UMA Kegs: 384, 0, 152, 1, 152, 0, 0, 0 UMA Zones: 4608, 0, 178, 0, 178, 0, 0, 0 UMA Slabs 0: 80, 0,43974304, 40,44081542, 0, 0, 0 UMA Slabs 1:112, 0, 19, 16, 19, 0, 0, 0 UMA Hash: 256, 0, 0, 0, 0, 0, 0, 0 2 Bucket:32, 0, 506,9700, 65241, 0, 0, 0 4 Bucket:48, 0, 299,7345,2335, 0, 0, 0 8 Bucket:80, 0, 791,4309, 31017, 13, 0, 0 16 Bucket: 144, 0, 690,2950, 1560027, 0, 0, 0 32 Bucket: 256, 0, 603,3762, 1367241, 145, 0, 0 64 Bucket: 512, 0, 19701, 803, 644895, 21, 0, 0 128 Bucket:1024, 0, 16902, 421, 394790, 109, 0, 0 256 Bucket:2048, 0, 182806, 210, 1993341,7129, 0, 0 SMR SHARED: 24, 0, 7, 760, 7, 0, 0, 0 SMR CPU: 32, 0, 7, 760, 7, 0, 0, 0 vmem: 1856, 0, 1, 7, 1, 0, 0, 0 vmem btag: 56, 0, 163197,9655, 170132,1200, 0, 0 VM OBJECT: 264, 0,1344,6486, 68963, 0, 0, 0 RADIX NODE: 144, 0, 143672, 46332, 340396, 0, 0, 0 KMAP ENTRY: 96, 0, 60, 21, 61, 0, 0, 0 MAP ENTRY: 96, 0,1434, 22632, 231811, 0, 0, 0 VMSPACE:616, 0, 30,1044,4748, 0, 0, 0 fakepg: 104, 0, 0, 0, 0, 0, 0, 0 pcpu-4: 4, 0, 0, 0, 0, 0, 0, 0 pcpu-8: 8, 0,4182,6058,4184, 0, 0, 0 pcpu-16: 16, 0, 96,5792, 96, 0, 0, 0 pcpu-32: 32, 0, 0, 0, 0, 0, 0, 0 pcpu-64: 64, 0, 471,1321, 471, 0, 0, 0 malloc-16: 16, 0, 19551,6405,265166105, 0, 0, 0 malloc-32: 32, 0, 14392,
[Bug 231574] [IF_BRIDGE(4)] improvements
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231574 Chris Davidson changed: What|Removed |Added CC||Christopher.davidson@gmail. ||com --- Comment #1 from Chris Davidson --- This looks to be correct and documented accordingly. The examples in question are for running an ifconfig(8) command to add the different interfaces in the configuration. The ifconfig(8) is referenced and the ifconfig(8) does discuss how to use the addm option within the rc.conf(5) file. ifconfig(8) snippet: addm interface Add the interface named by interface as a member of the bridge. The interface is put into promiscuous mode so that it can receive every packet sent on the network. It would be my recommendation to CLOSE this bug. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 216079] NTPD(8) interface command undocumented
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216079 Chris Davidson changed: What|Removed |Added CC||Christopher.davidson@gmail. ||com --- Comment #6 from Chris Davidson --- This bug, on the ntp.org bug, has been CONFIRMED as an issue. There has not been any movement on this for a few years though. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 273665] strlen.3 HISTORY section is truncated
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273665 Chris Davidson changed: What|Removed |Added CC||Christopher.davidson@gmail. ||com --- Comment #4 from Chris Davidson --- I looked into this more, specifically the commit id mentioned in the original submission: git show 4b7f35db44cbf901e994fc9a4bcd4c98ebe8c4a1 This looks to also appear in -CURRENT, looking through previous versions of the manual page, before the commit id above this is what I was able to find. https://man.freebsd.org/cgi/man.cgi?query=strnlen=0=0=FreeBSD+13.1-RELEASE=default=html This release does not go into the details of where it came from, the history section is not available. My question would be: Is there anything mandating the HISTORY section? My recommendation would be to remove the HISTORY stuff, until more information could be found. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 273665] strlen.3 HISTORY section is truncated
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273665 --- Comment #3 from Alexander Ziaee --- I am not familiar with this topic. The other pages say .At v7 and use a semicolon. How do you feel about this? Sh HISTORY The Fn strlen function first appeared in the Programmer's Workbench (PWB/UNIX) and was ported to At v7 ; the Fn strnlen function first appeared in At v7 and was reimplemented for Fx 8 . -- You are receiving this mail because: You are the assignee for the bug.
[Bug 277739] makefs creates UFS filesystem that fsck considers invalid
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277739 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|f...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug.
[Bug 254144] missing some directories and files in OptionalObsoleteFiles.inc
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254144 --- Comment #4 from Mark Linimon --- (In reply to Dmitry Wagin from comment #3) I think it's less that, than the number of PRs has overwhelmed our volunteers. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 277738] Frequent crashes of kernel from pcpu_aux.h (page fault/double fault)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277738 Mark Linimon changed: What|Removed |Added Keywords||crash -- You are receiving this mail because: You are the assignee for the bug.
[Bug 277736] llvm-objdump can crash due to ELFFile::dynamicEntries() not checking p_offset
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277736 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|toolch...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug.
[Bug 254144] missing some directories and files in OptionalObsoleteFiles.inc
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254144 Dmitry Wagin changed: What|Removed |Added Resolution|--- |Feedback Timeout Status|New |Closed --- Comment #3 from Dmitry Wagin --- Nobody cares about that. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 273665] strlen.3 HISTORY section is truncated
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273665 --- Comment #2 from John F. Carr --- strnlen was added to FreeBSD in 69099ba2ec8b01fe51a5c69b98990cde406c5ab8 in 2009. The online version of 4.3 Reno at https://github.com/dank101/4.3BSD-Reno does not have strnlen. It does have strncpy, strncmp, and strncat. >From https://pubs.opengroup.org/onlinepubs/9699919799/functions/strlen.html: "The strnlen() function is added from The Open Group Technical Standard, 2006, Extended API Set Part 1." >From OpenBSD: "The strnlen() function appeared in glibc 2.0 and was reimplemented for OpenBSD 4.8." -- You are receiving this mail because: You are the assignee for the bug.
[Bug 277739] makefs creates UFS filesystem that fsck considers invalid
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277739 John F. Carr changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu ||gzilla/show_bug.cgi?id=2737 ||25 --- Comment #1 from John F. Carr --- This is related to bug #273725, which was considered harmless. In my case fsck wants to clear an inode. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 277740] makefs -t msdos silently ignores hard links
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277740 Bug ID: 277740 Summary: makefs -t msdos silently ignores hard links Product: Base System Version: 14.0-STABLE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: j...@mit.edu When makefs creates an MSDOS filesystem it only uses one of the pathnames of a hard linked file. The other names are silently ignored. It should emit a warning or make multiple copies of the linked file. # ls -Ali /tmp/tree total 8 1646873 -rw-r--r-- 2 root wheel 5 Mar 16 17:04 a 1646873 -rw-r--r-- 2 root wheel 5 Mar 16 17:04 b # makefs -t msdos -s 32m /tmp/tree-fs /tmp/tree Creating `/tmp/tree-fs' /tmp/tree-fs: 65432 sectors in 8179 FAT16 clusters (4096 bytes/cluster) BytesPerSec=512 SecPerClust=8 ResSectors=1 FATs=2 RootDirEnts=512 Media=0xf0 FATsecs=32 SecPerTrack=63 Heads=255 HiddenSecs=0 HugeSectors=65536 Populating `/tmp/tree-fs' Image `/tmp/tree-fs' complete # mdconfig -o ro /tmp/tree-fs md2 # mount -t msdos -o ro /dev/md2 /mnt # ls -Al /mnt total 4 -rwxr-xr-x 1 root wheel 5 Mar 16 13:04 a -- You are receiving this mail because: You are the assignee for the bug.
[Bug 276724] 'man 8 glabel'
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276724 --- Comment #2 from Chris Moerz --- Added a Phabricator review to simplify the patch creation and review: https://reviews.freebsd.org/D44394 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 277717] kernel using 100% CPU in arc_prune in 13.3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277717 Peter Much changed: What|Removed |Added CC||p...@citylink.dinoex.sub.org --- Comment #5 from Peter Much --- (In reply to Marek Zarychta from comment #1) I reported on Feb 6 that problem in bug 275594 is also present in 13.3-BETA1, and on Feb 23 that the patches by Seigo Tanimura do solve my issue. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 277739] makefs creates UFS filesystem that fsck considers invalid
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277739
Bug ID: 277739
Summary: makefs creates UFS filesystem that fsck considers
invalid
Product: Base System
Version: 14.0-STABLE
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: bin
Assignee: b...@freebsd.org
Reporter: j...@mit.edu
I used makefs to create a UFS filesystem. The filesystem is marked clean but
fsck reports errors.
# makefs -s 4g /var/tmp/root-image /usr/obj/stage15
Calculated size of `/var/tmp/root-image': 4294967296 bytes, 27793 inodes
Extent size set to 32768
density reduced from 154535 to 8192
/var/tmp/root-image: 4096.0MB (8388608 sectors) block size 32768, fragment size
4096
using 7 cylinder groups of 626.00MB, 20032 blks, 80128 inodes.
super-block backups (for fsck -b #) at:
64, 1282112, 2564160, 3846208, 5128256, 6410304, 7692352
Populating `/var/tmp/root-image'
Image `/var/tmp/root-image' complete
# mdconfig -f /var/tmp/root-image
md2
# fsck -p /dev/md2
/dev/md2: FILE SYSTEM CLEAN; SKIPPING CHECKS
/dev/md2: clean, 145201 free (25 frags, 18147 blocks, 0.0% fragmentation)
# fsck /dev/md2
** /dev/md2
** Last Mounted on
** Phase 1 - Check Blocks and Sizes
UFS1 cylinder group 0 failed: cgp->cg_old_niblk ("14592") != sblock.fs_ipg
("80128")
UFS1 cylinder group 0 failed: cgp->cg_old_niblk ("14592") != sblock.fs_ipg
("80128")
CYLINDER GROUP 0: INTEGRITY CHECK FAILED
REBUILD CYLINDER GROUP? [yn] y
INVALID INODE I=5632 OWNER=root MODE=120755
SIZE=19 MTIME=Mar 15 06:46 2024
CLEAR? [yn]
Inode number 5632 is
5632 lrwxr-xr-x 1 root wheel 19 Mar 15 06:46
/mnt/usr/share/locale/pt_BR.UTF-8/LC_CTYPE -> ../C.UTF-8/LC_CTYPE
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 274536] panic: rt_tables_get_rnh_ptr: fam out of bounds (255 < 45)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274536 --- Comment #11 from Gleb Smirnoff --- Can you please apply both https://reviews.freebsd.org/D44375 https://reviews.freebsd.org/D44392 and check if that fixes the panic? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 277738] Frequent crashes of kernel from pcpu_aux.h (page fault/double fault)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277738 Bug ID: 277738 Summary: Frequent crashes of kernel from pcpu_aux.h (page fault/double fault) Product: Base System Version: 14.0-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: andreas.coc.ga...@gmail.com Created attachment 249217 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=249217=edit two crash back traces I got frequent crashes (about 1 to 3 per day) of Freebsd 14 running on a NUC6CAYB. either page faults or double faults. Hardware has disable bt, no attached keyboard, monitor, mouse. All crashes are related to /usr/src/sys/amd64/include/pcpu_aux.h:57 Please find attached two crash descriptions. Are the crashes related to acpi problems? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 274536] panic: rt_tables_get_rnh_ptr: fam out of bounds (255 < 45)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274536 --- Comment #10 from Edward Tomasz Napierala --- Negative; the s/254/255/ patch doesn't seem to fix the panic I'm having. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 277736] llvm-objdump can crash due to ELFFile::dynamicEntries() not checking p_offset
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277736 Bug ID: 277736 Summary: llvm-objdump can crash due to ELFFile::dynamicEntries() not checking p_offset Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: r...@lcs.mit.edu Created attachment 249216 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=249216=edit a corrupt ELF file that causes llvm-objdump to crash This line in llvm-project/llvm/lib/Object/ELF.cpp dynamicEntries() forms a pointer from p_offset without checking whether it's too large: Dyn = ArrayRef(reinterpret_cast(base() + Phdr.p_offset), Phdr.p_filesz / sizeof(Elf_Dyn)); As a result a corrupt ELF file can cause objdump to crash. I've attached a demo. # uname -a FreeBSD stock14 15.0-CURRENT FreeBSD 15.0-CURRENT #19 main-n268743-a58813fd701e: Sat Mar 9 07:18:21 AST 2024 root@stock14:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 # objdump --version LLVM (http://llvm.org/): LLVM version 17.0.6 Optimized build with assertions. .. # objdump -p ldd1b.exe .. PLEASE submit a bug report to https://bugs.freebsd.org/submit/ and include the crash backtrace. Stack dump: 0. Program arguments: objdump -p ldd1b.exe #0 0x01230c41 PrintStackTrace /usr/src/contrib/llvm-project/llvm/lib/Support/Unix/Signals.inc:602:13 #1 0x0122f0b5 RunSignalHandlers /usr/src/contrib/llvm-project/llvm/lib/Support/Signals.cpp:105:18 #2 0x01231365 SignalHandler /usr/src/contrib/llvm-project/llvm/lib/Support/Unix/Signals.inc:0:3 #3 0x0008249cf5ff handle_signal /usr/src/lib/libthr/thread/thr_sig.c:0:3 #4 0x0008249cebbb thr_sighandler /usr/src/lib/libthr/thread/thr_sig.c:244:1 #5 0x00082270d2d3 ([vdso]+0x2d3) #6 0x00f96641 dynamicEntries /usr/src/contrib/llvm-project/llvm/lib/Object/ELF.cpp:590:24 #7 0x00df2268 operator bool /usr/src/contrib/llvm-project/llvm/include/llvm/Support/Error.h:559:17 #8 0x00df2268 printDynamicSection /usr/src/contrib/llvm-project/llvm/tools/llvm-objdump/ELFDump.cpp:205:8 #9 0x00df2268 printPrivateHeaders /usr/src/contrib/llvm-project/llvm/tools/llvm-objdump/ELFDump.cpp:431:3 #10 0x00e6a13c dumpObject /usr/src/contrib/llvm-project/llvm/tools/llvm-objdump/llvm-objdump.cpp:2815:7 #11 0x00e654b0 dumpInput /usr/src/contrib/llvm-project/llvm/tools/llvm-objdump/llvm-objdump.cpp:0:5 #12 0x00e654b0 for_each, std::__1::allocator > *>, void (*)(llvm::StringRef)> /usr/obj/usr/src/amd64.amd64/tmp/usr/include/c++/v1/__algorithm/for_each.h:26:5 #13 0x00e654b0 for_each, std::__1::allocator >, std::__1::allocator, std::__1::allocator > > > &, void (*)(llvm::StringRef)> /usr/src/contrib/llvm-project/llvm/include/llvm/ADT/STLExtras.h:1731:10 #14 0x00e654b0 main /usr/src/contrib/llvm-project/llvm/tools/llvm-objdump/llvm-objdump.cpp:3248:3 #15 0x000828a2d0aa __libc_start1 /usr/src/lib/libc/csu/libc_start1.c:157:2 Bus error (core dumped) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 277717] kernel using 100% CPU in arc_prune in 13.3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277717 --- Comment #4 from Christos Chatzaras --- The problem discussed in the link might be relevant: https://forums.freebsd.org/threads/rsync-bad-file-descriptor.92733/ Does anyone know if an errata notice is anticipated? -- You are receiving this mail because: You are the assignee for the bug.
