[Bug 279546] ctladm.8 is inconsistent about "ctladm port"'s "-l" option

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279546 --- Comment #5 from commit-h...@freebsd.org --- A commit in branch stable/14 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=95fbdf9df5b0918668517298d3ca77b65361b756 commit 95fbdf9df5b0918668517298d3ca77b65361b756 Author:

[Bug 281574] bc(1) runs in endless loop

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281574 John F. Carr changed: What|Removed |Added CC||j...@mit.edu --- Comment #3 from Jo

[Bug 281589] FreeBSD 13.4 bootloader rev 3.0 fails to load kernel with mfsbsd-created image

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281589 Bug ID: 281589 Summary: FreeBSD 13.4 bootloader rev 3.0 fails to load kernel with mfsbsd-created image Product: Base System Version: 13.4-RELEASE Hardware: Any

[Bug 238006] syslogd not starting because of missing /var/run/log

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238006 --- Comment #14 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=5d045d556b1cfeb1487d49017b536afb3df105d3 commit 5d045d556b1cfeb1487d49017b536afb3df105d3 Author:

[Bug 267817] No sound with Intel Comet Lake PCH-LP cAVS sound card

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267817 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|multime...@freebsd.org -- You are

[Bug 281570] What's reponame? (and what's pkg-name?) Missing explanation

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281570 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|p...@freebsd.org -- You are receiv

[Bug 281573] pkg fetch seems to indicate you can't specify pkg-name if you use -o

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281573 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|p...@freebsd.org -- You are receiv

[Bug 271460] ctld ports become inaccessible due to concurrent service restarts

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271460 Alan Somers changed: What|Removed |Added Flags||mfc-stable14?, |

[Bug 271460] ctld ports become inaccessible due to concurrent service restarts

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271460 --- Comment #4 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=5f89aea7b74aa4605b25af62e31303097a4a48cc commit 5f89aea7b74aa4605b25af62e31303097a4a48cc Author:

[Bug 267817] No sound with Intel Comet Lake PCH-LP cAVS sound card

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267817 --- Comment #3 from Joe B --- (In reply to Alexander Ziaee from comment #2) Hello, Here you go [joe@freebsd1 ~]$ mixer pcm0:mixer: on hdaa0 (play) (default) vol = 1.00:1.00 pbk pcm = 1.00:1.00 pbk Tell me i

[Bug 259968] ASLR by default tracking PR

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259968 Mark Linimon changed: What|Removed |Added Depends on||256477 Referenced Bugs: https://b

[Bug 267817] No sound with Intel Comet Lake PCH-LP cAVS sound card

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267817 Alexander Ziaee changed: What|Removed |Added CC||zi...@runbox.com Compon

[Bug 259968] ASLR by default tracking PR

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259968 Justine Akehurst changed: What|Removed |Added CC||justine.akehu...@dell.com --- C

[Bug 281574] bc(1) runs in endless loop

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281574 --- Comment #2 from Wolfram Schneider --- (In reply to Wolfram Schneider from comment #1) the previous version is not affected (as on freefall right now) /usr/bin/bc --version bc 6.7.6 -- You are receiving this mail because: You are the

[Bug 281574] bc(1) runs in endless loop

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281574 Wolfram Schneider changed: What|Removed |Added Status|New |Open CC|

[Bug 281574] bc(1) runs in endless loop

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281574 Wolfram Schneider changed: What|Removed |Added Assignee|freebsd-...@freebsd.org |b...@freebsd.org Har

[Bug 281570] What's reponame? (and what's pkg-name?) Missing explanation

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281570 refodap...@cetnob.com changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu

[Bug 281573] pkg fetch seems to indicate you can't specify pkg-name if you use -o

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281573 refodap...@cetnob.com changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu

[Bug 281570] What's reponame? (and what's pkg-name?) Missing explanation

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281570 --- Comment #2 from refodap...@cetnob.com --- Thanks, however, I feel it could be more clearly and explicitly stated in "pkg help fetch" and (potentially also in "man pkg.conf"). Right now it's a bit confusing(In reply to Muhammad Moinur Rah

[Bug 281573] pkg fetch seems to indicate you can't specify pkg-name if you use -o

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281573 Bug ID: 281573 Summary: pkg fetch seems to indicate you can't specify pkg-name if you use -o Product: Documentation Version: Latest Hardware: Any OS:

[Bug 281570] What's reponame? (and what's pkg-name?) Missing explanation

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281570 Muhammad Moinur Rahman changed: What|Removed |Added CC||b...@freebsd.org --- Comm

[Bug 281570] What's reponame? (and what's pkg-name?) Missing explanation

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281570 Bug ID: 281570 Summary: What's reponame? (and what's pkg-name?) Missing explanation Product: Documentation Version: Latest Hardware: Any OS: Any

[Bug 281471] ASLR: jemalloc RES memory keeps on increasing until process cores

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281471 --- Comment #11 from Rupesh Pilania --- (In reply to Rupesh Pilania from comment #7) We found that MALLOC_OPTIONS was set to X in our env, which was causing cores with above aslr patch for compat/10 libraries. Setting MALLOC_OPTIONS = "XDm"

[Bug 281560] gve (4) uma deadlock during high tcp throughput

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281560 Mark Linimon changed: What|Removed |Added Keywords||vendor Assignee|b...@free

[Bug 281560] gve (4) uma deadlock during high tcp throughput

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281560 Bug ID: 281560 Summary: gve (4) uma deadlock during high tcp throughput Product: Base System Version: 14.1-RELEASE Hardware: amd64 OS: Any Status: New

[Bug 281555] False positives from /etc/periodic/security/100.chksetuid after freebsd-update

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281555 Bug ID: 281555 Summary: False positives from /etc/periodic/security/100.chksetuid after freebsd-update Product: Base System Version: 13.3-RELEASE

[Bug 228069] tar(1) fails to append newer files only (-u, --update), but always appends all files (like -r).

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228069 --- Comment #4 from titus m --- There is another problem. If tar needs to strip the first / in the file path it seems it wont detect that the file is already present in the archive ###

[Bug 228069] tar(1) fails to append newer files only (-u, --update), but always appends all files (like -r).

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228069 --- Comment #3 from cweim...@gmail.com --- If the man page clarified that -u may not act as expected unless using pax format it would be very helpful. It looks like OpenBSD just changed tar to use pax format by default. https://marc.info/

[Bug 280303] /lib/libc++ requires a new version of /lib/libcxxrt

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280303 Kyle Evans changed: What|Removed |Added Assignee|toolch...@freebsd.org |b...@freebsd.org --- Comment #11 from

[Bug 238006] syslogd not starting because of missing /var/run/log

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238006 --- Comment #13 from Harald Schmalzbauer --- (In reply to Mark Johnston from comment #12) > I'm not sure what that diff is. The diff I mentioned is just a local MFC of syslogd(8). All changes up to d556719e15d6 (plus your test). I suspec

[Bug 228069] tar(1) fails to append newer files only (-u, --update), but always appends all files (like -r).

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228069 --- Comment #2 from Harald Schmalzbauer --- (In reply to titus m from comment #1) Thanks for the explanation! I generally use --posix (pax format) when it comes to backups, path length is (was) another reason. Hopefully I'll find some time

[Bug 228069] tar(1) fails to append newer files only (-u, --update), but always appends all files (like -r).

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228069 titus m changed: What|Removed |Added CC||ti...@edc.ro --- Comment #1 from titus m

[Bug 281547] nvd->nda + /dev/diskid + zfs triggers locking issues and partition not in /dev

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281547 --- Comment #5 from Russell Stuart --- Created attachment 253619 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=253619&action=edit Problem 2 the console when FreeBSD 14 fails to boot -- You are receiving this mail because: You

[Bug 281547] nvd->nda + /dev/diskid + zfs triggers locking issues and partition not in /dev

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281547 --- Comment #4 from Russell Stuart --- Created attachment 253618 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=253618&action=edit Problem 2 "ls -lR /dev" showing missing /dev/nvd0pX entries -- You are receiving this mail becau

[Bug 281547] nvd->nda + /dev/diskid + zfs triggers locking issues and partition not in /dev

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281547 --- Comment #3 from Russell Stuart --- Created attachment 253617 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=253617&action=edit Problem 2 - the configuration just before the reboot into FreeBSD 14 -- You are receiving this m

[Bug 281547] nvd->nda + /dev/diskid + zfs triggers locking issues and partition not in /dev

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281547 --- Comment #2 from Russell Stuart --- Created attachment 253616 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=253616&action=edit problem 1: The FreeBSD 14 console when booting has failed -- You are receiving this mail because

[Bug 281547] nvd->nda + /dev/diskid + zfs triggers locking issues and partition not in /dev

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281547 Russell Stuart changed: What|Removed |Added CC||russell.stu...@akips.com --- Comm

[Bug 281547] nvd->nda + /dev/diskid + zfs triggers locking issues and partition not in /dev

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281547 Bug ID: 281547 Summary: nvd->nda + /dev/diskid + zfs triggers locking issues and partition not in /dev Product: Base System Version: 14.1-STABLE Hardware: Any

[Bug 281541] rpcinfo: format of argument to -a flag is undocumented

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281541 Bug ID: 281541 Summary: rpcinfo: format of argument to -a flag is undocumented Product: Documentation Version: Latest Hardware: Any OS: Any Status: New

[Bug 281528] SCSI tag-queue error with Samsung 870 EVO SSD [incl. workaround]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281528 --- Comment #1 from w...@psr.com --- Possibly related Forum article from 2018, about a Samsung 860 EVO: https://forums.freebsd.org/threads/cam-status-uncorrectable-parity-crc-error.67691/ -- You are receiving this mail because: You are the

[Bug 279381] FreeBSD 13.3-RELEASE breaks isp driver with Qlogic QLE2692 16Gb fibre channel cards

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279381 --- Comment #6 from drkspc --- (In reply to Joerg Pulz from comment #5) Looks good so far, both 13.3 with the additional patch and 13.4 do the trick on our test server. -- You are receiving this mail because: You are the assignee for the

[Bug 221221] netboot: shutting down netbooted machine hangs at "syncing disks... 1 1 1 1 1"

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221221 Janet Whitley changed: What|Removed |Added CC||keitharke...@gmail.com --- Comment

[Bug 281528] SCSI tag-queue error with Samsung 870 EVO SSD [incl. workaround]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281528 Bug ID: 281528 Summary: SCSI tag-queue error with Samsung 870 EVO SSD [incl. workaround] Product: Base System Version: Unspecified Hardware: Any OS: A

[Bug 281524] msdosfs error over USB causes a kernel panic

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281524 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|f...@freebsd.org Keywords

[Bug 281526] Linuxulator - fstatat unsupported flag 0x800

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281526 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|emulat...@freebsd.org -- You are r

[Bug 281526] Linuxulator - fstatat unsupported flag 0x800

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281526 --- Comment #1 from sporran-musin...@icloud.com --- Created attachment 253595 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=253595&action=edit linux binary linuxulator start OK example strace when successfully started -- You a

[Bug 281526] Linuxulator - fstatat unsupported flag 0x800

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281526 Bug ID: 281526 Summary: Linuxulator - fstatat unsupported flag 0x800 Product: Base System Version: 14.1-STABLE Hardware: amd64 OS: Any Status: New S

[Bug 281524] msdosfs error over USB causes a kernel panic

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281524 Bug ID: 281524 Summary: msdosfs error over USB causes a kernel panic Product: Base System Version: 14.1-RELEASE Hardware: amd64 OS: Any Status: New

[Bug 281520] zfs panic: VERIFY(!txg_list_member(&vd->vdev_ms_list, msp, t)) failed after install

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281520 Mark Linimon changed: What|Removed |Added Keywords||crash Assignee|b...@freeb

[Bug 281511] FFS mount(8) test scenario hangs in "sdstart"

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281511 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|k...@freebsd.org --- Comment #2 fro

[Bug 281511] FFS mount(8) test scenario hangs in "sdstart"

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281511 Mark Linimon changed: What|Removed |Added Flags||mfc-stable14?, |

[Bug 281471] ASLR: jemalloc RES memory keeps on increasing until process cores

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281471 Mark Linimon changed: What|Removed |Added Status|New |Open --- Comment #10 from Mark Lini

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 ob

[Bug 281511] FFS mount(8) test scenario hangs in "sdstart"

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281511 Konstantin Belousov changed: What|Removed |Added Status|New |In Progress -- You are rece

[Bug 281520] zfs panic: VERIFY(!txg_list_member(&vd->vdev_ms_list, msp, t)) failed after install

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281520 Bug ID: 281520 Summary: zfs panic: VERIFY(!txg_list_member(&vd->vdev_ms_list, msp, t)) failed after install Product: Base System Version: 15.0-CURRENT Hardware: arm64

[Bug 281511] FFS mount(8) test scenario hangs in "sdstart"

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281511 --- Comment #1 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=4b273a7fb9e6d9a006c5ac7cbd27f5d006569edb commit 4b273a7fb9e6d9a006c5ac7cbd27f5d006569edb Author:

[Bug 281518] [PATCH] bsdinstall: improve pkg installation support in installation media live environment

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281518 Li-Wen Hsu changed: What|Removed |Added CC|lw...@freebsd.org | Assignee|b...@freebsd.org

[Bug 281518] [PATCH] bsdinstall: improve pkg installation support in installation media live environment

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281518 Bug ID: 281518 Summary: [PATCH] bsdinstall: improve pkg installation support in installation media live environment Product: Base System Version: CURRENT Hardware: An

[Bug 281511] FFS mount(8) test scenario hangs in "sdstart"

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281511 Bug ID: 281511 Summary: FFS mount(8) test scenario hangs in "sdstart" Product: Base System Version: 15.0-CURRENT Hardware: Any OS: Any Status: New S

[Bug 272940] A link without delimiters in vi(1) is broken by a trailing full stop

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272940 Alexander Ziaee changed: What|Removed |Added Status|New |Closed Resolution|---

[Bug 281218] Quectel LTE MODEM not working anymore

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281218 --- Comment #10 from Franco Fichtner --- net/mpd5, but it's only a theory. It's rather difficult to reproduce it seems. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 281494] stand/i386/boot0: print location of string F6 PXE is not aligned

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281494 --- Comment #2 from Tatsuki Makino --- Created attachment 253558 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=253558&action=edit photo of the screen with patched boot0 displayed Here is a photo of the screen showing the patche

[Bug 281494] stand/i386/boot0: print location of string F6 PXE is not aligned

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281494 --- Comment #1 from Tatsuki Makino --- Created attachment 253557 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=253557&action=edit proposal patch for stand/i386/boot0 \n before Boot: at prompt is to create a blank line. There, c

[Bug 281494] stand/i386/boot0: print location of string F6 PXE is not aligned

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281494 Bug ID: 281494 Summary: stand/i386/boot0: print location of string F6 PXE is not aligned Product: Base System Version: Unspecified Hardware: Any OS: A

[Bug 274014] hmt.ko kernel panic - Asus Expertbook B5602

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274014 Vladimir Kondratyev changed: What|Removed |Added Assignee|b...@freebsd.org|w...@freebsd.org -- You are

[Bug 274014] hmt.ko kernel panic - Asus Expertbook B5602

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274014 --- Comment #4 from Vladimir Kondratyev --- Created attachment 253554 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=253554&action=edit hid-parser.diff Recently I was able to reproduce the panic on ASUS TUF laptop. It appeared

[Bug 281471] ASLR: jemalloc RES memory keeps on increasing until process cores

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281471 --- Comment #9 from Rupesh Pilania --- Issue exists in 13.4 as well. FreeBSD rupesh2 13.4-RC3 FreeBSD 13.4-RC3 releng/13.4-n258255-087b246271b6 GENERIC amd64 root@rupesh2:/home/rpilania # setenv MALLOC_CONF "xmalloc:true,dirty_decay_ms:0,r

[Bug 270460] i386 CURRENT guest boot time panics in emulators/virtualbox-ose on amd64 host (FreeBSD 13.1, Windows 10, FreeBSD 13.2-RELEASE-p1)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270460 --- Comment #21 from Paul Floyd --- (In reply to Mark Linimon from comment #20) Yes it is for https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281475 I wasn’t paying attention to which browser tab I was adding stuff to. -- You are recei

[Bug 281218] Quectel LTE MODEM not working anymore

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281218 Mark Linimon changed: What|Removed |Added CC||lini...@freebsd.org --- Comment #9

[Bug 281452] Realtek 'if_re' module crashes on module load

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281452 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|n...@freebsd.org --- Comment #3 fro

[Bug 281460] if_ovpn doesn't work with crypto.ko

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281460 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|n...@freebsd.org --- Comment #2 fro

[Bug 281456] makefs zfs is tricky to get right with multiple partitions, matching freebsd install default

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281456 Mark Linimon changed: What|Removed |Added CC||d...@freebsd.org Assignee

[Bug 281469] Lock order reversal in mlx5 during boot.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281469 Mark Linimon changed: What|Removed |Added Summary|Lock issue during boot. |Lock order reversal in mlx5

[Bug 281483] [librt] timer_delete segfaults with incorrect timer id

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281483 Mark Linimon changed: What|Removed |Added Keywords||crash -- You are receiving this ma

[Bug 270460] i386 CURRENT guest boot time panics in emulators/virtualbox-ose on amd64 host (FreeBSD 13.1, Windows 10, FreeBSD 13.2-RELEASE-p1)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270460 Mark Linimon changed: What|Removed |Added CC||lini...@freebsd.org --- Comment #20

[Bug 281489] linux: unsupported ioctl TIOCGPTPERR / linux_ioctl_fallback cmd=0x5441 ('T',65) and cmd=0x541c ('T',28) is not implemented..

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281489 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|emulat...@freebsd.org -- You are r

[Bug 281489] linux: unsupported ioctl TIOCGPTPERR / linux_ioctl_fallback cmd=0x5441 ('T',65) and cmd=0x541c ('T',28) is not implemented..

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281489 Bug ID: 281489 Summary: linux: unsupported ioctl TIOCGPTPERR / linux_ioctl_fallback cmd=0x5441 ('T',65) and cmd=0x541c ('T',28) is not implemented.. Product: Base Syst

[Bug 270460] i386 CURRENT guest boot time panics in emulators/virtualbox-ose on amd64 host (FreeBSD 13.1, Windows 10, FreeBSD 13.2-RELEASE-p1)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270460 --- Comment #19 from Paul Floyd --- Ignore all the previous changes - I was working with the wrong browser tab. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 270460] i386 CURRENT guest boot time panics in emulators/virtualbox-ose on amd64 host (FreeBSD 13.1, Windows 10, FreeBSD 13.2-RELEASE-p1)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270460 Paul Floyd changed: What|Removed |Added Hardware|amd64 |i386 -- You are receiving this mail

[Bug 270460] i386 CURRENT guest boot time panics in emulators/virtualbox-ose on amd64 host (FreeBSD 13.1, Windows 10, FreeBSD 13.2-RELEASE-p1)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270460 Paul Floyd changed: What|Removed |Added Attachment #253546|1 |0 is patch|

[Bug 270460] i386 CURRENT guest boot time panics in emulators/virtualbox-ose on amd64 host (FreeBSD 13.1, Windows 10, FreeBSD 13.2-RELEASE-p1)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270460 Paul Floyd changed: What|Removed |Added Attachment #253546||maintainer-approval+ Fla

[Bug 270460] i386 CURRENT guest boot time panics in emulators/virtualbox-ose on amd64 host (FreeBSD 13.1, Windows 10, FreeBSD 13.2-RELEASE-p1)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270460 Paul Floyd changed: What|Removed |Added Hardware|i386|amd64 -- You are receiving this mail

[Bug 270460] i386 CURRENT guest boot time panics in emulators/virtualbox-ose on amd64 host (FreeBSD 13.1, Windows 10, FreeBSD 13.2-RELEASE-p1)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270460 --- Comment #17 from Paul Floyd --- What's new (at least), the following bugfixes (numbers are kde.org bugzilla IDs). 202770 open fd at exit --log-socket=127.0.0.1:1500 with --track-fds=yes 276780 An instruction in fftw (Fast Fourier Tra

[Bug 281471] ASLR: jemalloc RES memory keeps on increasing until process cores

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281471 Rupesh Pilania changed: What|Removed |Added Version|Unspecified |13.3-RELEASE --- Comment #8 from

[Bug 281471] ASLR: jemalloc RES memory keeps on increasing until process cores

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281471 --- Comment #7 from Rupesh Pilania --- This patch https://github.com/freebsd/freebsd-src/commit/d8e6f4946cec0b84a6997d62e791b8cf993741b2 Bringing RES memory to almost similar to FreeBSD 14.1 and FreeBSD 10.4. Seems to be resolving the prob

[Bug 281483] [librt] timer_delete segfaults with incorrect timer id

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281483 Bug ID: 281483 Summary: [librt] timer_delete segfaults with incorrect timer id Product: Base System Version: 14.1-RELEASE Hardware: Any OS: Any Status: New

[Bug 281479] [meta] Linux source compatibility tracking issue

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281479 Mark Linimon changed: What|Removed |Added Keywords||tracking -- You are receiving this

[Bug 246943] [patch] calendar(1): Do not send reports for uids < 1000, except root

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246943 Ed Maste changed: What|Removed |Added CC||ema...@freebsd.org Status|N

[Bug 281471] ASLR: jemalloc RES memory keeps on increasing until process cores

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281471 --- Comment #6 from Rupesh Pilania --- This patch https://github.com/freebsd/freebsd-src/commit/d8e6f4946cec0b84a6997d62e791b8cf993741b2 Bringing RES memory to almost similar to FreeBSD 14.1 and FreeBSD 10.4. Seems to be resolving the prob

[Bug 281471] ASLR: jemalloc RES memory keeps on increasing until process cores

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281471 --- Comment #5 from Rupesh Pilania --- (In reply to Brooks Davis from comment #3) Applied patch suggested by you but no difference seen. https://github.com/freebsd/freebsd-src/commit/268f19aacc6af8f64c438e8515213023a2e66ed7 -- You are rec

[Bug 281479] [meta] Linux source compatibility tracking issue

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281479 Bug ID: 281479 Summary: [meta] Linux source compatibility tracking issue Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Sev

[Bug 281471] ASLR: jemalloc RES memory keeps on increasing until process cores

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281471 --- Comment #4 from Rupesh Pilania --- (In reply to Brooks Davis from comment #3) Thankyou for your reply. I will try after applying this patch. Tested with FreeBSD 14.1. Issue is not seen. sysctl -a | grep aslr kern.elf32.aslr.shared_pag

[Bug 281471] ASLR: jemalloc RES memory keeps on increasing until process cores

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281471 Brooks Davis changed: What|Removed |Added CC||bro...@freebsd.org --- Comment #3 f

[Bug 281471] ASLR: jemalloc RES memory keeps on increasing until process cores

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281471 --- Comment #2 from Rupesh Pilania --- Issue should exists on 13.3 and 13.4 as well. Will check and update the OS Tag. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 281471] ASLR: jemalloc RES memory keeps on increasing until process cores

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281471 --- Comment #1 from Rupesh Pilania --- mem-fragment program reference was taken from https://engineering.linkedin.com/blog/2021/taming-memory-fragmentation-in-venice-with-jemalloc#:~:text=Jemalloc #include #include #include #include

[Bug 281471] ASLR: jemalloc RES memory keeps on increasing until process cores

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281471 Bug ID: 281471 Summary: ASLR: jemalloc RES memory keeps on increasing until process cores Product: Base System Version: Unspecified Hardware: arm64 OS

[Bug 281433] Changing kern.elf64 sysctl's requires press-button reboot

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281433 dewa...@heuristicsystems.com.au changed: What|Removed |Added Status|New |Closed Re

[Bug 281433] Changing kern.elf64 sysctl's requires press-button reboot

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281433 --- Comment #5 from dewa...@heuristicsystems.com.au --- (In reply to dewayne from comment #4) A self inflicted issue from the outset. Of course the combination that I want is kern.elf64.allow_wx: 1 -> 0 kern.elf64.nxstack: 1 -> 1 For the i

[Bug 280978] Kernel panics with vfs.nfsd.enable_locallocks=1 and nfs clients doing hdf5 file operations

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280978 Rick Macklem changed: What|Removed |Added Assignee|b...@freebsd.org|rmack...@freebsd.org St

[Bug 281469] Lock issue during boot.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281469 Bug ID: 281469 Summary: Lock issue during boot. Product: Base System Version: 14.1-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Onl

<    1   2   3   4   5   6   7   8   9   10   >