freebsd-current  

Messages by Thread

• Re: LRO Kernel Panic on Hyper-V VM Michael Tuexen
  • Re: LRO Kernel Panic on Hyper-V VM Michael Tuexen
  • Re: LRO Kernel Panic on Hyper-V VM Shawn Webb
• FreeBSD Git Weekly 2026-04-06 to 2026-04-12 Graham Percival
• Building VM-IMAGE(s) from Source vermaden
  • Re: Building VM-IMAGE(s) from Source Colin Percival
  • Re: Building VM-IMAGE(s) from Source vermaden
  • Re: Building VM-IMAGE(s) from Source vermaden
  • Re: Building VM-IMAGE(s) from Source vermaden
  • Re: Building VM-IMAGE(s) from Source Dag-Erling Smørgrav
  • Re: Building VM-IMAGE(s) from Source vermaden
  • Re: Building VM-IMAGE(s) from Source Sulev-Madis Silber
  • Re: Building VM-IMAGE(s) from Source Kurt Jaeger
  • Re: Building VM-IMAGE(s) from Source vermaden
  • Re: Building VM-IMAGE(s) from Source David Chisnall
  • Re: Building VM-IMAGE(s) from Source Kurt Jaeger
  • Re: Building VM-IMAGE(s) from Source David Chisnall
  • Re: Building VM-IMAGE(s) from Source vermaden
  • Re: Building VM-IMAGE(s) from Source vermaden
• Re: Panic: cache_vop_rename: lingering negative entry Minsoo Choo
  • Re: Panic: cache_vop_rename: lingering negative entry Jan Martin Mikkelsen
  • Re: Panic: cache_vop_rename: lingering negative entry Konstantin Belousov
  • Re: Panic: cache_vop_rename: lingering negative entry Jan Martin Mikkelsen
  • Re: Panic: cache_vop_rename: lingering negative entry Jan Martin Mikkelsen
  • Re: Panic: cache_vop_rename: lingering negative entry Konstantin Belousov
  • Re: Panic: cache_vop_rename: lingering negative entry Jan Martin Mikkelsen
  • Re: Panic: cache_vop_rename: lingering negative entry Konstantin Belousov
  • Re: Panic: cache_vop_rename: lingering negative entry Jan Martin Mikkelsen
  • Re: Panic: cache_vop_rename: lingering negative entry Jan Martin Mikkelsen
• FreeBSD Git Weekly 2026-03-30 to 2026-04-05, and 2026-Q1 Graham Percival
• Re: debug files now have program headers Dimitry Andric
  • Re: debug files now have program headers Gleb Popov
  • Re: debug files now have program headers Ed Maste
  • Re: debug files now have program headers Paul Floyd
• pkgbase breakage in main due to libucl upgrade Lexi Winter
  • Re: pkgbase breakage in main due to libucl upgrade Adrian Chadd
  • Re: pkgbase breakage in main due to libucl upgrade Lexi Winter
• Re: make RELEASE (here: kernel): template.ucl: line: 33, column: 0 - 'key must begin with a letter', character: '.' A FreeBSD User
  • Re: make RELEASE (here: kernel): template.ucl: line: 33, column: 0 - 'key must begin with a letter', character: '.' Lexi Winter
  • Re: make RELEASE (here: kernel): template.ucl: line: 33, column: 0 - 'key must begin with a letter', character: '.' A FreeBSD User
• Re: Getting boottime early in booting Warner Losh
  • Re: Getting boottime early in booting Konstantin Belousov
  • Re: Getting boottime early in booting Rick Macklem
  • Re: Getting boottime early in booting Rick Macklem
  • Re: Getting boottime early in booting Konstantin Belousov
  • Re: Getting boottime early in booting julian
  • Re: Getting boottime early in booting Dag-Erling Smørgrav
  • Re: Getting boottime early in booting Rick Macklem
  • Re: Getting boottime early in booting Rick Macklem
  • Re: Getting boottime early in booting Rick Macklem
• Proposal: remove IPv6-only RA draft bits to adopt DHCP option (RFC 8925) Pouria Mousavizadeh Tehrani
  • Re: Proposal: remove IPv6-only RA draft bits to adopt DHCP option (RFC 8925) Bjoern A. Zeeb
  • Re: Proposal: remove IPv6-only RA draft bits to adopt DHCP option (RFC 8925) Pouria Mousavizadeh Tehrani
  • Re: Proposal: remove IPv6-only RA draft bits to adopt DHCP option (RFC 8925) Marek Zarychta
• Re: Panic: "knote ... was already on knlist..." after main-n284826-d9d7b5948649 Konstantin Belousov
  • Re: Panic: "knote ... was already on knlist..." after main-n284826-d9d7b5948649 David Wolfskill
  • Re: Panic: "knote ... was already on knlist..." after main-n284826-d9d7b5948649 Kyle Evans
  • Re: Panic: "knote ... was already on knlist..." after main-n284826-d9d7b5948649 David Wolfskill
• Re: Etcupdate runtime has more than doubled....Why? Dimitry Andric
  • Re: Etcupdate runtime has more than doubled....Why? bob prohaska
  • Re: Etcupdate runtime has more than doubled....Why? Charlie Li
  • Re: Etcupdate runtime has more than doubled....Why? bob prohaska
  • Re: Etcupdate runtime has more than doubled....Why? Mark Millard
  • Re: Etcupdate runtime has more than doubled....Why? bob prohaska
  • Re: Etcupdate runtime has more than doubled....Why? David Wolfskill
  • Re: Etcupdate runtime has more than doubled....Why? Tomoaki AOKI
  • Re: Etcupdate runtime has more than doubled....Why? Mark Millard
  • Re: Etcupdate runtime has more than doubled....Why? Mark Millard
  • Re: Etcupdate runtime has more than doubled....Why? bob prohaska
• [LAST OFFICIAL REMINDER] Call for 2026Q1 status reports Lorenzo Salvadore
• FreeBSD Git Weekly 2026-03-23 to 2026-03-29 Graham Percival
• Anybody used Blackship? Alan Somers
  • Re: Anybody used Blackship? Adrian Chadd
• Re: RFC: atime and ZFS snapshots Konstantin Belousov
• FreeBSD Git Weekly 2026-03-16 to 2026-03-22 Graham Percival
  • Re: FreeBSD Git Weekly 2026-03-16 to 2026-03-22 Rainer Hurling
• Re: kern_sig.c pfault with non-sleepable locks held Tomoaki AOKI
  • Re: kern_sig.c pfault with non-sleepable locks held Bjoern A. Zeeb
• March 2026 stabilization week Gleb Smirnoff
  • Re: March 2026 stabilization week Gleb Smirnoff
  • Re: March 2026 stabilization week Poul-Henning Kamp
  • Re: March 2026 stabilization week polyduekes
  • Re: March 2026 stabilization week Martin Cracauer
• Re: CURRENT (after commit b1f72dd2a9a5e69a310b9e76b55f16cff433b8da): silently crashing when make -jXX buildworld Alexander Leidinger
• Re: CURRENT (after commit b1f72dd2a9a5e69a310b9e76b55f16cff433b8da): silently crashing when make -jXX buildworld Herbert J. Skuhra
  • Re: CURRENT (after commit b1f72dd2a9a5e69a310b9e76b55f16cff433b8da): silently crashing when make -jXX buildworld David Wolfskill
  • Re: CURRENT (after commit b1f72dd2a9a5e69a310b9e76b55f16cff433b8da): silently crashing when make -jXX buildworld Tomoaki AOKI
  • Re: CURRENT (after commit b1f72dd2a9a5e69a310b9e76b55f16cff433b8da): silently crashing when make -jXX buildworld Herbert J. Skuhra
  • Re: CURRENT (after commit b1f72dd2a9a5e69a310b9e76b55f16cff433b8da): silently crashing when make -jXX buildworld Tomoaki AOKI
  • Re: CURRENT (after commit b1f72dd2a9a5e69a310b9e76b55f16cff433b8da): silently crashing when make -jXX buildworld Herbert J. Skuhra
  • Re: CURRENT (after commit b1f72dd2a9a5e69a310b9e76b55f16cff433b8da): silently crashing when make -jXX buildworld A FreeBSD User
• Re: buildworld failure: main-n284554-1aecb32021ce -> main-n284582-33345b883485 Michael Butler
  • Re: buildworld failure: main-n284554-1aecb32021ce -> main-n284582-33345b883485 Wismos
  • Re: buildworld failure: main-n284554-1aecb32021ce -> main-n284582-33345b883485 Enji Cooper (yaneurabeya)
• Re: guest kernel fails to start when cpuset is used Miroslav Lachman
  • Re: guest kernel fails to start when cpuset is used Nikos Vassiliadis
• userret: returning with the following locks held Zhenlei Huang
  • Re: userret: returning with the following locks held Konstantin Belousov
  • Re: userret: returning with the following locks held Zhenlei Huang
• FreeBSD Git Weekly 2026-03-09 to 2026-03-15 Graham Percival
• Re: zfs module not loaded anymore on e.g MINIMAL Warner Losh
  • Re: zfs module not loaded anymore on e.g MINIMAL h v
  • Re: zfs module not loaded anymore on e.g MINIMAL h v
  • Re: zfs module not loaded anymore on e.g MINIMAL Warner Losh
  • Re: zfs module not loaded anymore on e.g MINIMAL Martin Matuska
  • Re: zfs module not loaded anymore on e.g MINIMAL h v
  • Re: zfs module not loaded anymore on e.g MINIMAL Dag-Erling Smørgrav
  • Re: zfs module not loaded anymore on e.g MINIMAL Warner Losh
  • Re: zfs module not loaded anymore on e.g MINIMAL Dag-Erling Smørgrav
  • Re: zfs module not loaded anymore on e.g MINIMAL Dag-Erling Smørgrav
  • Re: zfs module not loaded anymore on e.g MINIMAL Warner Losh
• Re: Huge build times increase after updating from 14.3 to 14.4 [15.0 and main suffer such extra time as well] Mark Millard
• [1 MONTH LEFT REMINDER] Call for 2026Q1 status reports Lorenzo Salvadore
• Re: panic: supervisor write data, protection violation (vn_read/copyout_smap_erms?) Michael Butler
  • Re: panic: supervisor write data, protection violation (vn_read/copyout_smap_erms?) David Wolfskill
  • Re: panic: supervisor write data, protection violation (vn_read/copyout_smap_erms?) Michael Butler
  • Re: panic: supervisor write data, protection violation (vn_read/copyout_smap_erms?) Ian FREISLICH
• Re: buildkernel failure [in_prot.c:61:2: error: use of undeclared identifier 'RA_LOCKED'] Gleb Smirnoff
  • Re: buildkernel failure [in_prot.c:61:2: error: use of undeclared identifier 'RA_LOCKED'] Ian Freislich
• Re: Recent -CURRENT and drm-66-kmod panic Rainer Hurling
  • Re: Recent -CURRENT and drm-66-kmod panic Roman Bogorodskiy
  • Re: Recent -CURRENT and drm-66-kmod panic Roman Bogorodskiy
  • Re: Recent -CURRENT and drm-66-kmod panic Rainer Hurling
  • Re: Recent -CURRENT and drm-66-kmod panic Roman Bogorodskiy
• FreeBSD Git Weekly 2026-03-02 to 2026-03-08 Graham Percival
• Re: git: c499ad6f997c - main - virtio: Use bus_dma for ring and indirect buffer allocations [Really: kernel: vtnet0: watchdog timeout on queue xx] Mark Millard
  • Re: git: c499ad6f997c - main - virtio: Use bus_dma for ring and indirect buffer allocations [Really: kernel: vtnet0: watchdog timeout on queue xx] Michael Butler
• Re: timeouts on vtnet? Philip Paeps
• Re: where does one find the graphics/wifi/bluetooth firmware packages in the packagebase install medium? Chris
• Re: LINT-NOINET failure in gre; warnings in tcp and pf Bjoern A. Zeeb
  • Re: LINT-NOINET failure in gre; warnings in tcp and pf Michael Tuexen
  • Re: LINT-NOINET failure in gre; warnings in tcp and pf Michael Tuexen
• FreeBSD Git Weekly 2026-02-23 to 2026-03-01 Graham Percival
• Call for 2026Q1 status reports Lorenzo Salvadore
• FYI: The elapsed time shown for beefy24 [main-amd64] and beefy23 [150amd64-default] stopped over 2hrs ago Mark Millard
  • 504 gateway time-outs (was: FYI: The elapsed time shown for beefy24 [main-amd64] and beefy23 [150amd64-default] stopped over 2hrs ago) Graham Perrin
  • Re: 504 gateway time-outs (was: FYI: The elapsed time shown for beefy24 [main-amd64] and beefy23 [150amd64-default] stopped over 2hrs ago) Kevin Oberman
  • Re: 504 gateway time-outs (was: FYI: The elapsed time shown for beefy24 [main-amd64] and beefy23 [150amd64-default] stopped over 2hrs ago) Kevin Oberman
  • Re: 504 gateway time-outs Mark Millard
  • Re: 504 gateway time-outs Kevin Oberman
  • Re: 504 gateway time-outs Mark Millard
  • Re: 504 gateway time-outs (was: FYI: The elapsed time shown for beefy24 [main-amd64] and beefy23 [150amd64-default] stopped over 2hrs ago) Philip Paeps
  • Re: 504 gateway time-outs Mark Millard
  • Re: 504 gateway time-outs Mark Millard
• FreeBSD Git Weekly 2026-02-16 to 2026-02-22 Graham Percival
• FreeBSD Status Report - Fourth Quarter 2025 Lorenzo Salvadore
  • Re: FreeBSD Status Report - Fourth Quarter 2025 Lorenzo Salvadore
• February 2026 stabilization week Gleb Smirnoff
  • Re: February 2026 stabilization week Poul-Henning Kamp
  • Re: February 2026 stabilization week Gleb Smirnoff
• Re: "make installworld": /usr/tests/bin/ed: No such file or directory David Wolfskill
• FreeBSD Git Weekly 2026-02-09 to 2026-02-15 Graham Percival
• Re: Buildkernel failure (error: declaration of 'struct socket' will not be visible outside of this function) Mark Johnston
  • Re: Buildkernel failure (error: declaration of 'struct socket' will not be visible outside of this function) Ian FREISLICH
  • Re: Buildkernel failure (error: declaration of 'struct socket' will not be visible outside of this function) Mark Johnston
• HEADS UP: IPv6 SLAAC default algorithm changed (RFC 7217) Guido Falsi
• FreeBSD Git Weekly 2026-02-02 to 2026-02-08 Graham Percival
• git-clone(1) after base 3e8619e535b6 for /usr/ports subdirectories Graham Perrin
  • Re: git-clone(1) after base 3e8619e535b6 for /usr/ports subdirectories Warner Losh
  • Re: git-clone(1) after base 3e8619e535b6 for /usr/ports subdirectories Graham Perrin
  • Re: git-clone(1) after base 3e8619e535b6 for /usr/ports subdirectories ruby R53
  • Re: git-clone(1) after base 3e8619e535b6 for /usr/ports subdirectories Enji Cooper (yaneurabeya)
  • Re: git-clone(1) after base 3e8619e535b6 for /usr/ports subdirectories Graham Perrin
  • Re: git-clone(1) after base 3e8619e535b6 for /usr/ports subdirectories Michael Gmelin
  • Re: git-clone(1) after base 3e8619e535b6 for /usr/ports subdirectories ruby R53
  • Re: git-clone(1) after base 3e8619e535b6 for /usr/ports subdirectories Marek Zarychta
  • Re: git-clone(1) after base 3e8619e535b6 for /usr/ports subdirectories Marek Zarychta
  • Re: git-clone(1) after base 3e8619e535b6 for /usr/ports subdirectories Warner Losh
  • Pull request 2006 (was: git-clone(1) after base 3e8619e535b6 for /usr/ports subdirectories) Graham Perrin
  • Re: Pull request 2006 (was: git-clone(1) after base 3e8619e535b6 for /usr/ports subdirectories) Warner Losh
• FreeBSD Git Weekly 2026-01-26 to 2026-02-01 Graham Percival
• Re: cam_da too noisy about SYNCHRONIZE CACHE Warner Losh
• we should enable RFC7217 by default Pouria Mousavizadeh Tehrani
  • Re: we should enable RFC7217 by default Olivier Cochard-Labbé
  • Re: we should enable RFC7217 by default Pouria Mousavizadeh Tehrani
  • Re: we should enable RFC7217 by default Guido Falsi
  • Re: we should enable RFC7217 by default Guido Falsi
  • Re: we should enable RFC7217 by default Shawn Webb
  • Re: we should enable RFC7217 by default Guido Falsi
  • Re: we should enable RFC7217 by default Shawn Webb
  • Re: we should enable RFC7217 by default Guido Falsi
  • Re: we should enable RFC7217 by default Shawn Webb
  • Re: we should enable RFC7217 by default Guido Falsi
  • Re: we should enable RFC7217 by default Marek Zarychta
  • Re: we should enable RFC7217 by default Patrick M. Hausen
  • Re: we should enable RFC7217 by default Patrick M. Hausen
  • Re: we should enable RFC7217 by default Marek Zarychta
  • Re: we should enable RFC7217 by default Guido Falsi
  • Re: we should enable RFC7217 by default Marek Zarychta
  • Re: we should enable RFC7217 by default Pouria Mousavizadeh Tehrani
  • Re: we should enable RFC7217 by default Brooks Davis
  • Re: we should enable RFC7217 by default Marek Zarychta
  • Re: we should enable RFC7217 by default Guido Falsi
  • Re: we should enable RFC7217 by default Guido Falsi
  • Re: we should enable RFC7217 by default Brooks Davis
  • Re: we should enable RFC7217 by default Tomoaki AOKI
  • Re: we should enable RFC7217 by default Ronald Klop
• Heads up: New WITNESS output Jonathan T. Looney
  • Re: Heads up: New WITNESS output Zhenlei Huang
• FreeBSD Git Weekly 2026-01-19 to 2026-01-25 Graham Percival

• Earlier messages