freebsd-current  

Messages by Thread

• • Re: changes to ps -d? Michael Gmelin
  • Re: changes to ps -d? Ronald Klop
  • Re: changes to ps -d? Piotr P. Stefaniak
  • Re: changes to ps -d? Jamie Landeg-Jones
  • Re: changes to ps -d? Jamie Landeg-Jones
• Re: vfs.zfs.bclone_enabled (was: FreeBSD 14.0-BETA2 Now Available) Mark Millard
  • Re: vfs.zfs.bclone_enabled (was: FreeBSD 14.0-BETA2 Now Available) [block_cloning and zilsaxattr missing from loader's features_for_read] Mark Millard
  • Re: vfs.zfs.bclone_enabled (was: FreeBSD 14.0-BETA2 Now Available) [block_cloning and zilsaxattr missing from loader's features_for_read] Alexander Motin
  • Re: vfs.zfs.bclone_enabled (was: FreeBSD 14.0-BETA2 Now Available) [block_cloning and zilsaxattr missing from loader's features_for_read] Mark Millard
• Re: [Intel AlderLake] Read&Write files to FAT32 or UFS partition cause data corrupt due to P-Core&E-Core Michael Butler
  • Re: [Intel AlderLake] Read&Write files to FAT32 or UFS partition cause data corrupt due to P-Core&E-Core Mike Karels
  • Re: [Intel AlderLake] Read&Write files to FAT32 or UFS partition cause data corrupt due to P-Core&E-Core Michael Butler
  • Re: [Intel AlderLake] Read&Write files to FAT32 or UFS partition cause data corrupt due to P-Core&E-Core Konstantin Belousov
• Re: CURRRENT snapshot won't boot due missing ZFS feature void
  • Re: CURRRENT snapshot won't boot due missing ZFS feature Warner Losh
  • Re: CURRRENT snapshot won't boot due missing ZFS feature void
  • Re: CURRRENT snapshot won't boot due missing ZFS feature void
  • Re: CURRRENT snapshot won't boot due missing ZFS feature Mark Millard
  • Re: CURRRENT snapshot won't boot due missing ZFS feature Toomas Soome
  • Re: CURRRENT snapshot won't boot due missing ZFS feature Warner Losh
  • Re: CURRRENT snapshot won't boot due missing ZFS feature Michael Gmelin
  • Re: CURRRENT snapshot won't boot due missing ZFS feature void
  • Re: CURRRENT snapshot won't boot due missing ZFS feature void
  • Re: CURRRENT snapshot won't boot due missing ZFS feature void
  • Re: CURRRENT snapshot won't boot due missing ZFS feature void
  • Re: CURRRENT snapshot won't boot due missing ZFS feature Tomoaki AOKI
• buildkernel: Cleaning for nvidia-driver-470-470.161.03: [all] Stopped -- signal 22 Graham Perrin
• time instability Sulev-Madis Silber
• FreeBSD 14.0-BETA2 Now Available Glen Barber
  • vfs.zfs.bclone_enabled (was: FreeBSD 14.0-BETA2 Now Available) Graham Perrin
  • Re: vfs.zfs.bclone_enabled (was: FreeBSD 14.0-BETA2 Now Available) Alexander Motin
  • Re: vfs.zfs.bclone_enabled (was: FreeBSD 14.0-BETA2 Now Available) Martin Matuska
  • Re: vfs.zfs.bclone_enabled (was: FreeBSD 14.0-BETA2 Now Available) Mark Johnston
  • Re: vfs.zfs.bclone_enabled (was: FreeBSD 14.0-BETA2 Now Available) Tomoaki AOKI
  • Re: vfs.zfs.bclone_enabled (was: FreeBSD 14.0-BETA2 Now Available) Alexander Motin
  • Re: vfs.zfs.bclone_enabled (was: FreeBSD 14.0-BETA2 Now Available) Tomoaki AOKI
• [2 WEEKS LEFT REMINDER] Call for 2023Q3 status reports Lorenzo Salvadore
• A lock order reversal that I've not seen before (zfs and tmpfs during poudriere bulk using USE_TMPFS=all) Mark Millard
• Re: git: 8d49fd7331bc - main - pf: remove DIOCGETRULE and DIOCGETSTATUS : net/py-libdnet and net/scapy now broken, kyua test suite damaged Mark Millard
  • Re: git: 8d49fd7331bc - main - pf: remove DIOCGETRULE and DIOCGETSTATUS : net/py-libdnet and net/scapy now broken, kyua test suite damaged Kristof Provost
  • Fwd: git: 8d49fd7331bc - main - pf: remove DIOCGETRULE and DIOCGETSTATUS : net/py-libdnet and net/scapy now broken, kyua test suite damaged Mark Millard
  • Re: git: 8d49fd7331bc - main - pf: remove DIOCGETRULE and DIOCGETSTATUS : net/py-libdnet and net/scapy now broken, kyua test suite damaged Kristof Provost
• sys/net/if_lagg_test:status_stress can lead to use-after-free in main (both before and after stable/14 was created), at least on aarch64 Mark Millard
• Continually count the number of open files Graham Perrin
  • Re: Continually count the number of open files Ronald Klop
  • Re: Continually count the number of open files Bakul Shah
  • Re: Continually count the number of open files Graham Perrin
  • Re: Continually count the number of open files Bakul Shah
  • Re: Continually count the number of open files Tomoaki AOKI
  • Re: Continually count the number of open files David Chisnall
  • Re: Continually count the number of open files Mateusz Guzik
• ZFS Panics Still Cy Schubert
  • Re: ZFS Panics Still Graham Perrin
  • Re: ZFS Panics Still Cy Schubert
• kernel trap 12 .. cam_periph_release_locked_buses() panics under panic? Bjoern A. Zeeb
  • Re: kernel trap 12 .. cam_periph_release_locked_buses() panics under panic? Warner Losh
  • Re: kernel trap 12 .. cam_periph_release_locked_buses() panics under panic? Bjoern A. Zeeb
  • Re: kernel trap 12 .. cam_periph_release_locked_buses() panics under panic? Warner Losh
• aarch64 main [so: 15] panic's in kyua's sys/net/if_lagg_test:status_stress Mark Millard
  • Re: aarch64 main [so: 15] panic's in kyua's sys/net/if_lagg_test:status_stress [confirmed with snapshot kernel] Mark Millard
  • Re: aarch64 main [so: 15] panic's in kyua's sys/net/if_lagg_test:status_stress [confirmed with snapshot kernel] Mark Millard
• Re: 14-ALPHA2 panic on cold boot cglogic
  • Re: 14-ALPHA2 panic on cold boot cglogic
  • Re: 14-ALPHA2 panic on cold boot Mark Johnston
  • Re: 14-ALPHA2 panic on cold boot cglogic
  • Re: 14-ALPHA2 panic on cold boot Santiago Martinez
  • Re: 14-ALPHA2 panic on cold boot cglogic
• Looks like the kyua zfs tests likely are not used on aarch64 or other contexts with unsigned char Mark Millard
  • Re: Looks like the kyua zfs tests likely are not used on aarch64 or other contexts with unsigned char Mike Karels
  • Re: Looks like the kyua zfs tests likely are not used on aarch64 or other contexts with unsigned char Mark Millard
  • Re: Looks like the kyua zfs tests likely are not used on aarch64 or other contexts with unsigned char Mark Millard
  • Re: Looks like the kyua zfs tests likely are not used on aarch64 or other contexts with unsigned char Warner Losh
  • Re: Looks like the kyua zfs tests likely are not used on aarch64 or other contexts with unsigned char Mark Millard
  • Re: Looks like the kyua zfs tests likely are not used on aarch64 or other contexts with unsigned char Dag-Erling Smørgrav
  • Re: Looks like the kyua zfs tests likely are not used on aarch64 or other contexts with unsigned char Mark Millard
  • Re: Looks like the kyua zfs tests likely are not used on aarch64 or other contexts with unsigned char Mark Millard
• 15/14 upgrades break old sudo, maybe bump PAM's shlib? John Baldwin
• 15.0-CURRENT build broken in lib/libmagic Rainer Hurling
  • Re: 15.0-CURRENT build broken in lib/libmagic Rainer Hurling
  • Re: 15.0-CURRENT build broken in lib/libmagic Dag-Erling Smørgrav
  • Re: 15.0-CURRENT build broken in lib/libmagic Rainer Hurling
  • Re: 15.0-CURRENT build broken in lib/libmagic Dag-Erling Smørgrav
  • Re: 15.0-CURRENT build broken in lib/libmagic Rainer Hurling
  • Re: 15.0-CURRENT build broken in lib/libmagic Dag-Erling Smørgrav
  • Re: 15.0-CURRENT build broken in lib/libmagic Rainer Hurling
• sed in CURRENT fails in textproc/jq Yuri
  • Re: sed in CURRENT fails in textproc/jq Antoine Brodin
  • Re: sed in CURRENT fails in textproc/jq Dag-Erling Smørgrav
  • Re: sed in CURRENT fails in textproc/jq Robert Clausecker
  • Re: sed in CURRENT fails in textproc/jq Warner Losh
  • Re: sed in CURRENT fails in textproc/jq Lorenzo Salvadore
  • Re: sed in CURRENT fails in textproc/jq Robert Clausecker
  • Re: sed in CURRENT fails in textproc/jq Warner Losh
  • Re: sed in CURRENT fails in textproc/jq Dag-Erling Smørgrav
  • Re: sed in CURRENT fails in textproc/jq Robert Clausecker
  • Re: sed in CURRENT fails in textproc/jq Alexander Leidinger
• Re: git: ed03cfc5d231 - main - textproc/jq: Add USES=bison; Use gsed to fix configuration failure on 15 Antoine Brodin
• FreeBSD 14.0-BETA1 Now Available Glen Barber
  • Re: FreeBSD 14.0-BETA1 Now Available Ed Maste
• Acer C720 Chromebook Cypress Trackpad Matthias Apitz
  • Re: Acer C720 Chromebook Cypress Trackpad Matthias Apitz
• main [and, likely, stable/14]: do not set vfs.zfs.bclone_enabled=1 with that zpool feature enabled because it still leads to panics Mark Millard
  • Re: main [and, likely, stable/14]: do not set vfs.zfs.bclone_enabled=1 with that zpool feature enabled because it still leads to panics Mark Millard
  • Re: main [and, likely, stable/14]: do not set vfs.zfs.bclone_enabled=1 with that zpool feature enabled because it still leads to panics Glen Barber
  • Re: main [and, likely, stable/14]: do not set vfs.zfs.bclone_enabled=1 with that zpool feature enabled because it still leads to panics Mark Millard
  • Re: main [and, likely, stable/14]: do not set vfs.zfs.bclone_enabled=1 with that zpool feature enabled because it still leads to panics Alexander Motin
  • Re: main [and, likely, stable/14]: do not set vfs.zfs.bclone_enabled=1 with that zpool feature enabled because it still leads to panics Mark Millard
  • Re: main [and, likely, stable/14]: do not set vfs.zfs.bclone_enabled=1 with that zpool feature enabled because it still leads to panics Mark Millard
  • Re: main [and, likely, stable/14]: do not set vfs.zfs.bclone_enabled=1 with that zpool feature enabled because it still leads to panics Martin Matuska
  • Re: main [and, likely, stable/14]: do not set vfs.zfs.bclone_enabled=1 with that zpool feature enabled because it still leads to panics Mark Millard
  • Re: main [and, likely, stable/14]: do not set vfs.zfs.bclone_enabled=1 with that zpool feature enabled because it still leads to panics Alexander Motin
  • Re: main [and, likely, stable/14]: do not set vfs.zfs.bclone_enabled=1 with that zpool feature enabled because it still leads to panics Martin Matuska
  • Re: main [and, likely, stable/14]: do not set vfs.zfs.bclone_enabled=1 with that zpool feature enabled because it still leads to panics Mark Millard
  • Re: main [and, likely, stable/14]: do not set vfs.zfs.bclone_enabled=1 with that zpool feature enabled because it still leads to panics Mark Millard
  • Re: main [and, likely, stable/14]: do not set vfs.zfs.bclone_enabled=1 with that zpool feature enabled because it still leads to panics Mark Millard
  • Re: main [and, likely, stable/14]: do not set vfs.zfs.bclone_enabled=1 with that zpool feature enabled because it still leads to panics Mark Millard
  • Re: main [and, likely, stable/14]: do not set vfs.zfs.bclone_enabled=1 with that zpool feature enabled because it still leads to panics Alexander Motin
  • Re: main [and, likely, stable/14]: do not set vfs.zfs.bclone_enabled=1 with that zpool feature enabled because it still leads to panics Tomoaki AOKI
  • Re: main [and, likely, stable/14]: do not set vfs.zfs.bclone_enabled=1 with that zpool feature enabled because it still leads to panics Pawel Jakub Dawidek
• sysutils/panicmail and boot environments Graham Perrin
• Re: Possible regression in main causing poor performance Mark Millard
  • Re: Possible regression in main causing poor performance Cy Schubert
• Re: Stray characters in command history Sulev-Madis Silber
• FYI: ^T use during poudriere bulk vs. /bin/sh operation: I got a "Unsafe ckmalloc() call" Abort trap that left a mess Mark Millard
  • Re: FYI: ^T use during poudriere bulk vs. /bin/sh operation: I got a "Unsafe ckmalloc() call" Abort trap that left a mess Jilles Tjoelker
• 14.0-CURRENT boots fine but keyboard does not work Matthias Apitz
  • Re: 14.0-CURRENT boots fine but keyboard does not work Michael Gmelin
  • Re: 14.0-CURRENT boots fine but keyboard does not work Matthias Apitz
  • Re: 14.0-CURRENT boots fine but keyboard does not work Michael Gmelin
  • Re: 14.0-CURRENT boots fine but keyboard does not work Matthias Apitz
  • Re: 14.0-CURRENT boots fine but keyboard does not work Michael Gmelin
  • Re: 14.0-CURRENT boots fine but keyboard does not work Warner Losh
  • Re: 14.0-CURRENT boots fine but keyboard does not work Matthias Apitz
  • Re: 14.0-CURRENT boots fine but keyboard does not work Warner Losh
  • Re: 14.0-CURRENT boots fine but keyboard does not work Matthias Apitz
  • Re: 14.0-CURRENT boots fine but keyboard does not work Warner Losh
  • Re: 14.0-CURRENT boots fine but keyboard does not work Steve Kargl
  • Re: 14.0-CURRENT boots fine but keyboard does not work Warner Losh
  • Re: 14.0-CURRENT boots fine but keyboard does not work Matthias Apitz
• Re: Possible issue with linux xattr support? Felix Palmen
  • Re: Possible issue with linux xattr support? Felix Palmen
  • Re: Possible issue with linux xattr support? Dmitry Chagin
  • Re: Possible issue with linux xattr support? Felix Palmen
  • Re: Possible issue with linux xattr support? Dmitry Chagin
  • Re: Possible issue with linux xattr support? Felix Palmen
  • Re: Possible issue with linux xattr support? Felix Palmen
  • Re: Possible issue with linux xattr support? Dmitry Chagin
  • Re: Possible issue with linux xattr support? Dmitry Chagin
• Re: Speed improvements in ZFS Alexander Leidinger
  • Re: Speed improvements in ZFS Mateusz Guzik
  • Re: Speed improvements in ZFS Alexander Leidinger
  • Re: Speed improvements in ZFS George Michaelson
  • Re: Speed improvements in ZFS Alexander Leidinger
• Re: make-memstick.sh creates in 14.0-CURRENT run-away processes Matthias Apitz
• An attempted test of main's "git: 2ad756a6bbb3" "merge openzfs/zfs@95f71c019" that did not go as planned Mark Millard
  • Re: An attempted test of main's "git: 2ad756a6bbb3" "merge openzfs/zfs@95f71c019" that did not go as planned Alexander Motin
  • Re: An attempted test of main's "git: 2ad756a6bbb3" "merge openzfs/zfs@95f71c019" that did not go as planned Mark Millard
  • Re: An attempted test of main's "git: 2ad756a6bbb3" "merge openzfs/zfs@95f71c019" that did not go as planned Mark Millard
  • Re: An attempted test of main's "git: 2ad756a6bbb3" "merge openzfs/zfs@95f71c019" that did not go as planned Mark Millard
  • Re: An attempted test of main's "git: 2ad756a6bbb3" "merge openzfs/zfs@95f71c019" that did not go as planned Alexander Motin
  • Re: An attempted test of main's "git: 2ad756a6bbb3" "merge openzfs/zfs@95f71c019" that did not go as planned Mark Millard
  • Re: An attempted test of main's "git: 2ad756a6bbb3" "merge openzfs/zfs@95f71c019" that did not go as planned Alexander Motin
  • Re: An attempted test of main's "git: 2ad756a6bbb3" "merge openzfs/zfs@95f71c019" that did not go as planned Mark Millard
  • Re: An attempted test of main's "git: 2ad756a6bbb3" "merge openzfs/zfs@95f71c019" that did not go as planned Mark Millard
  • Re: An attempted test of main's "git: 2ad756a6bbb3" "merge openzfs/zfs@95f71c019" that did not go as planned Mark Millard
  • Re: An attempted test of main's "git: 2ad756a6bbb3" "merge openzfs/zfs@95f71c019" possible file odd result Mark Millard
  • Re: An attempted test of main's "git: 2ad756a6bbb3" "merge openzfs/zfs@95f71c019" possible file odd result Mark Millard
  • Re: An attempted test of main's "git: 2ad756a6bbb3" "merge openzfs/zfs@95f71c019" that did not go as planned Mark Millard
• Re: [Bug 273506] main [so: 15] aarch64 kyua python use fails with: . . . and dlerror is reporting "/usr/lib/ossl-modules/legacy.so: Undefined symbol \"MD4_Update\"", '\000' <repeats 449 times> Mark Millard
  • Re: [Bug 273506] main [so: 15] aarch64 kyua python use fails with: . . . and dlerror is reporting "/usr/lib/ossl-modules/legacy.so: Undefined symbol \"MD4_Update\"", '\000' <repeats 449 times> [crude patch] Mark Millard
• Re: 100% CPU time for sysctl command, not killable Mateusz Guzik
  • Re: 100% CPU time for sysctl command, not killable Alexander Leidinger
  • Re: 100% CPU time for sysctl command, not killable Alexander Leidinger
• Re: user problems when upgrading to v15 Dimitry Andric
  • Re: user problems when upgrading to v15 John Baldwin
  • Re: user problems when upgrading to v15 brian whalen
  • /var/db/etcupdate/ in hier(7) (was: user problems when upgrading to v15) Graham Perrin
• Re: FreeBSD-15 kernel panic when the amdtemp device is in the kernel Herbert J. Skuhra
  • Re: FreeBSD-15 kernel panic when the amdtemp device is in the kernel Gary Jennejohn
  • Re: FreeBSD-15 kernel panic when the amdtemp device is in the kernel Herbert J. Skuhra
  • Re: FreeBSD-15 kernel panic when the amdtemp device is in the kernel Gary Jennejohn
• kernel 100% CPU, and ports-mgmt/poudriere-devel 'Inspecting ports tree for modifications to git checkout...' for an extraordinarily long time Graham Perrin
  • Re: kernel 100% CPU, and ports-mgmt/poudriere-devel 'Inspecting ports tree for modifications to git checkout...' for an extraordinarily long time Mateusz Guzik
  • Re: kernel 100% CPU, and ports-mgmt/poudriere-devel 'Inspecting ports tree for modifications to git checkout...' for an extraordinarily long time Graham Perrin
  • Re: kernel 100% CPU, and ports-mgmt/poudriere-devel 'Inspecting ports tree for modifications to git checkout...' for an extraordinarily long time Alexander Motin
  • Re: kernel 100% CPU, and ports-mgmt/poudriere-devel 'Inspecting ports tree for modifications to git checkout...' for an extraordinarily long time Mateusz Guzik
  • Re: kernel 100% CPU … Graham Perrin
  • Re: kernel 100% CPU Graham Perrin
  • Re: kernel 100% CPU Juraj Lutter
  • Re: kernel 100% CPU Graham Perrin
  • Re: kernel 100% CPU Mateusz Guzik
  • Re: kernel 100% CPU Graham Perrin
  • Re: kernel 100% CPU Graham Perrin
  • Re: kernel 100% CPU Mateusz Guzik
  • Re: kernel 100% CPU Graham Perrin
  • Re: kernel 100% CPU Mateusz Guzik
  • Re: kernel 100% CPU Graham Perrin
  • Re: kernel 100% CPU Mateusz Guzik
  • Re: kernel 100% CPU, and ports-mgmt/poudriere-devel 'Inspecting ports tree for modifications to git checkout...' for an extraordinarily long time Michael Gmelin
  • Re: kernel 100% CPU, and ports-mgmt/poudriere-devel 'Inspecting ports tree for modifications to git checkout...' for an extraordinarily long time Graham Perrin

• Later messages