freebsd-current  

Messages by Thread

• Freezes with FreeBSD 15.0-CURRENT since 3 weeks Rodrigo Osorio
  • Re: Freezes with FreeBSD 15.0-CURRENT since 3 weeks Ronald Klop
  • Re: Freezes with FreeBSD 15.0-CURRENT since 3 weeks Rodrigo Osorio
• October 2024 stabilization week Gleb Smirnoff
  • Re: October 2024 stabilization week Gleb Smirnoff
  • Re: October 2024 stabilization week Dimitry Andric
• Build failure in share/examples/tests/tests/googletest/sample1_unittest.full David Wolfskill
  • Re: Build failure in share/examples/tests/tests/googletest/sample1_unittest.full Nuno Teixeira
  • Build/install failures at main-n273082-525a177c1657 David Wolfskill
  • Re: Build/install failures at main-n273082-525a177c1657 David Wolfskill
  • Re: Build failure in share/examples/tests/tests/googletest/sample1_unittest.full void
  • Re: Build failure in share/examples/tests/tests/googletest/sample1_unittest.full David Wolfskill
  • Re: Build failure in share/examples/tests/tests/googletest/sample1_unittest.full Nuno Teixeira
• loader.efi: "Malformed line (27)" error apparently due to recent splash config entry Rebecca Cran
  • Re: loader.efi: "Malformed line (27)" error apparently due to recent splash config entry Warner Losh
• Error message during a iozone test: "fsync: giving up on dirty . . ." Mark Millard
• NFS server credentials with cr_ngroups == 0 Rick Macklem
  • Re: NFS server credentials with cr_ngroups == 0 Olivier Certner
• Goings on in the Network Stack Tom Jones
• Buildworld stops build - undeclaired identifier Nathan Nasby
  • Re: Buildworld stops build - undeclaired identifier Konstantin Belousov
  • Re: Buildworld stops build - undeclaired identifier Nathan Nasby
  • Re: Buildworld stops build - undeclaired identifier Nathan Nasby
• Problems with FreeBSD-15.0-CURRENT-amd64-20241003 Paul Floyd
  • Re: Problems with FreeBSD-15.0-CURRENT-amd64-20241003 Konstantin Belousov
  • Re: Problems with FreeBSD-15.0-CURRENT-amd64-20241003 Paul Floyd
  • Re: Problems with FreeBSD-15.0-CURRENT-amd64-20241003 Paul Floyd
  • Re: Problems with FreeBSD-15.0-CURRENT-amd64-20241003 Konstantin Belousov
  • Re: Problems with FreeBSD-15.0-CURRENT-amd64-20241003 Paul Floyd
  • Re: Problems with FreeBSD-15.0-CURRENT-amd64-20241003 Konstantin Belousov
  • Re: Problems with FreeBSD-15.0-CURRENT-amd64-20241003 Paul Floyd
  • Re: Problems with FreeBSD-15.0-CURRENT-amd64-20241003 Graham Perrin
• RE: git: 2c1963d46335 - main - procfs rlimit: handle pipebuf [and related] :pipebuf . . . Invalid argument Mark Millard
  • Re: git: 2c1963d46335 - main - procfs rlimit: handle pipebuf [and related] :pipebuf . . . Invalid argument Konstantin Belousov
  • Re: git: 2c1963d46335 - main - procfs rlimit: handle pipebuf [and related] :pipebuf . . . Invalid argument Mark Millard
  • Re: git: 2c1963d46335 - main - procfs rlimit: handle pipebuf [and related] :pipebuf . . . Invalid argument Dag-Erling Smørgrav
  • Re: git: 2c1963d46335 - main - procfs rlimit: handle pipebuf [and related] :pipebuf . . . Invalid argument Konstantin Belousov
  • Re: git: 2c1963d46335 - main - procfs rlimit: handle pipebuf [and related] :pipebuf . . . Invalid argument Warner Losh
  • Re: git: 2c1963d46335 - main - procfs rlimit: handle pipebuf [and related] :pipebuf . . . Invalid argument Konstantin Belousov
  • Re: git: 2c1963d46335 - main - procfs rlimit: handle pipebuf [and related] :pipebuf . . . Invalid argument Mark Millard
• FYI: make's "max_jobs" needs to be separated from -j (now?) David Wolfskill
  • Re: FYI: make's "max_jobs" needs to be separated from -j (now?) dsdqmzk
  • Re: FYI: make's "max_jobs" needs to be separated from -j (now?) Dan Mack
  • Re: FYI: make's "max_jobs" needs to be separated from -j (now?) dsdqmzk
  • Re: FYI: make's "max_jobs" needs to be separated from -j (now?) Dan Mack
  • Re: FYI: make's "max_jobs" needs to be separated from -j (now?) Warner Losh
  • Re: FYI: make's "max_jobs" needs to be separated from -j (now?) Dan Mack
  • Re: FYI: make's "max_jobs" needs to be separated from -j (now?) Dan Mack
  • Re: FYI: make's "max_jobs" needs to be separated from -j (now?) Simon J. Gerraty
  • Re: FYI: make's "max_jobs" needs to be separated from -j (now?) David Wolfskill
  • Re: FYI: make's "max_jobs" needs to be separated from -j (now?) Simon J. Gerraty
  • 1500024, libmd.so.6 and libmd.so.7 (was: FYI: make's "max_jobs" needs to be separated from -j (now?)) Graham Perrin
  • Re: 1500024, libmd.so.6 and libmd.so.7 (was: FYI: make's "max_jobs" needs to be separated from -j (now?)) David Wolfskill
  • Re: 1500024, libmd.so.6 and libmd.so.7 Kyle Evans
  • Re: FYI: make's "max_jobs" needs to be separated from -j (now?) Olivier Cochard-Labbé
• panic: curthread not pinned dsdqmzk
  • Re: panic: curthread not pinned Konstantin Belousov
  • Re: panic: curthread not pinned Konstantin Belousov
  • Re: panic: curthread not pinned dsdqmzk
• Wake (resume) regression? Graham Perrin
  • Re: Wake (resume) regression? Graham Perrin
• Is INET6 a required option these days? (kernel build failure) Ian FREISLICH
  • Re: Is INET6 a required option these days? (kernel build failure) Gary Jennejohn
  • Re: Is INET6 a required option these days? (kernel build failure) Zhenlei Huang
  • Re: Is INET6 a required option these days? (kernel build failure) Kristof Provost
  • Re: Is INET6 a required option these days? (kernel build failure) Gary Jennejohn
  • Re: Is INET6 a required option these days? (kernel build failure) void
  • Re: Is INET6 a required option these days? (kernel build failure) Rodney W. Grimes
  • Re: Is INET6 a required option these days? (kernel build failure) Dennis Clarke
  • Re: Is INET6 a required option these days? (kernel build failure) Andrea Venturoli
• install error during installworld Gordon Bergling
  • Re: install error during installworld Dimitry Andric
  • Re: install error during installworld Gordon Bergling
• [LAST OFFICIAL REMINDER] Call for 2024Q3 status reports Lorenzo Salvadore
• UEFI + SOL / COM ports = boot hang Matt Simerson
  • Re: UEFI + SOL / COM ports = boot hang Matt Simerson
• September 2024 stabilization week Gleb Smirnoff
  • Re: September 2024 stabilization week Gleb Smirnoff
  • Re: September 2024 stabilization week void
  • Re: September 2024 stabilization week Michael Butler
  • Re: September 2024 stabilization week void
  • Re: September 2024 stabilization week Gary Jennejohn
  • Re: September 2024 stabilization week Simon J. Gerraty
  • Re: September 2024 stabilization week Gleb Smirnoff
  • weekly locate error Was: September 2024 stabilization week Gleb Smirnoff
  • Re: weekly locate error Was: September 2024 stabilization week Michael Butler
  • Re: weekly locate error Was: September 2024 stabilization week Gleb Smirnoff
  • Re: weekly locate error Was: September 2024 stabilization week void
  • Re: weekly locate error Was: September 2024 stabilization week Kyle Evans
  • Re: weekly locate error Was: September 2024 stabilization week Jamie Landeg-Jones
  • Re: weekly locate error Was: September 2024 stabilization week Kyle Evans
  • Re: weekly locate error Was: September 2024 stabilization week Olivier Certner
  • Re: weekly locate error Was: September 2024 stabilization week Rodney W. Grimes
  • Re: weekly locate error Was: September 2024 stabilization week Kyle Evans
  • Re: weekly locate error Was: September 2024 stabilization week Olivier Certner
  • Re: weekly locate error Was: September 2024 stabilization week Jamie Landeg-Jones
  • Re: weekly locate error Was: September 2024 stabilization week Jamie Landeg-Jones
  • Re: weekly locate error Was: September 2024 stabilization week void
• New console output at boot? Kevin Oberman
  • Re: New console output at boot? Warner Losh
  • Re: New console output at boot? Thomas Laus
  • Re: New console output at boot? Warner Losh
  • Re: New console output at boot? Thomas Laus
  • Re: New console output at boot? Thomas Laus
  • Re: New console output at boot? Warner Losh
  • Re: New console output at boot? Thomas Laus
  • Re: New console output at boot? Thomas Laus
  • Re: New console output at boot? Ronald Klop
  • Re: New console output at boot? Thomas Laus
  • Re: New console output at boot? Ronald Klop
  • Re: New console output at boot? Thomas Laus
  • Re: New console output at boot? Tomek CEDRO
  • Re: New console output at boot? Thomas Laus
  • Re: New console output at boot? Garance ELC Drosehn
• regarding that stack of newline chars expressed at boot Dennis Clarke
  • Re: regarding that stack of newline chars expressed at boot Warner Losh
  • Re: regarding that stack of newline chars expressed at boot Warner Losh
  • Re: regarding that stack of newline chars expressed at boot Dennis Clarke
  • Re: regarding that stack of newline chars expressed at boot Dennis Clarke
  • Re: regarding that stack of newline chars expressed at boot Warner Losh
• eval: Pipe call failed: Cannot allocate memory Yasuhiro Kimura
  • Re: eval: Pipe call failed: Cannot allocate memory Konstantin Belousov
  • Re: eval: Pipe call failed: Cannot allocate memory Dag-Erling Smørgrav
  • Re: eval: Pipe call failed: Cannot allocate memory Yasuhiro Kimura
  • Re: eval: Pipe call failed: Cannot allocate memory Konstantin Belousov
  • Re: eval: Pipe call failed: Cannot allocate memory Yasuhiro Kimura
• sccache-overlay and different major os versions void
• Re: git: 80eb861dc2a7 - main - pfctl: lex <=, >=, and != into a single token Herbert J. Skuhra
  • Re: git: 80eb861dc2a7 - main - pfctl: lex <=, >=, and != into a single token Herbert J. Skuhra
• RE: Chromium with Widevine: kernel panic: condition vp-> v_type == VDIR || VN_IS_DOOMED(vp) not met ⋯vfs_cache.c:34 52 (vn_fullpath_dir) Mark Millard
  • Kernel panics with Widevine and htop: VNPASS in sys/kern/vfs_cache.c Graham Perrin
• change in /usr/bin/bc with CTRL-d no longer exit Dan Mack
  • Re: change in /usr/bin/bc with CTRL-d no longer exit Herbert J. Skuhra
  • Re: change in /usr/bin/bc with CTRL-d no longer exit Dimitry Andric
  • Re: change in /usr/bin/bc with CTRL-d no longer exit Dan Mack
  • Re: change in /usr/bin/bc with CTRL-d no longer exit Stefan Eßer
  • Re: change in /usr/bin/bc with CTRL-d no longer exit void
  • Re: change in /usr/bin/bc with CTRL-d no longer exit void
  • Re: change in /usr/bin/bc with CTRL-d no longer exit Cy Schubert
  • Re: change in /usr/bin/bc with CTRL-d no longer exit Warner Losh
  • Re: change in /usr/bin/bc with CTRL-d no longer exit Cy Schubert
  • Re: change in /usr/bin/bc with CTRL-d no longer exit [fixed in -CURRENT] Stefan Esser
  • Re: change in /usr/bin/bc with CTRL-d no longer exit Dennis Clarke
  • Re: change in /usr/bin/bc with CTRL-d no longer exit Dan Mack
• [2 WEEKS LEFT REMINDER] Call for 2024Q3 status reports Lorenzo Salvadore
• Failing to boot in bhyve Pat Maddox
  • Re: Failing to boot in bhyve Zhenlei Huang
  • Re: Failing to boot in bhyve Pat Maddox
• freebsd-15-0-snap image in gcloud likely broken for Cirrus-CI usage Roger Pau Monné
• How to fix a broken package ? Dennis Clarke
  • Re: How to fix a broken package ? Dennis Clarke
• Loader needs to be updated message void
  • Re: Loader needs to be updated message Warner Losh
  • Re: Loader needs to be updated message void
  • Re: Loader needs to be updated message Warner Losh
  • Re: Loader needs to be updated message Tomoaki AOKI
  • Re: Loader needs to be updated message void
  • Re: Loader needs to be updated message void
  • Re: Loader needs to be updated message Mark Millard
  • Re: Loader needs to be updated message void
  • Re: Loader needs to be updated message void
  • Re: Loader needs to be updated message Mark Millard
  • Re: Loader needs to be updated message void
  • Re: Loader needs to be updated message Warner Losh
  • Re: Loader needs to be updated message void
  • Re: Loader needs to be updated message Warner Losh
  • Re: Loader needs to be updated message Tomoaki AOKI
  • Re: Loader needs to be updated message void
  • Re: Loader needs to be updated message Tomoaki AOKI
  • Re: Loader needs to be updated message Mark Millard
  • Re: Loader needs to be updated message Warner Losh
  • Re: Loader needs to be updated message Tomoaki AOKI
  • Re: Loader needs to be updated message Warner Losh
  • Re: Loader needs to be updated message Tomoaki AOKI
  • Re: Loader needs to be updated message Mark Millard
  • Re: Loader needs to be updated message Tomoaki AOKI
  • Re: Loader needs to be updated message Warner Losh
  • Re: Loader needs to be updated message void
  • Re: Loader needs to be updated message Warner Losh
  • Re: Loader needs to be updated message void
  • Re: Loader needs to be updated message void
  • Re: Loader needs to be updated message Warner Losh
  • Re: Loader needs to be updated message void
• panic in zfs/nvlist Gleb Smirnoff
  • Re: panic in zfs/nvlist Alexander Motin
  • Re: panic in zfs/nvlist Gleb Smirnoff
• Anyone else seeing a stack of newline chars expressed at boot? Dennis Clarke
  • Re: Anyone else seeing a stack of newline chars expressed at boot? Warner Losh
  • Re: Anyone else seeing a stack of newline chars expressed at boot? Dennis Clarke
  • Re: Anyone else seeing a stack of newline chars expressed at boot? Warner Losh
  • Re: Anyone else seeing a stack of newline chars expressed at boot? Dennis Clarke
• Re: git: fc43a1b6842a - stable/14 - tzsetup: symlink /etc/localtime instead of copying Herbert J. Skuhra
• Call for 2024Q3 status reports Lorenzo Salvadore
• August 2024 stabilization week Gleb Smirnoff
  • Re: August 2024 stabilization week Gleb Smirnoff
  • Re: August 2024 stabilization week Olivier Cochard-Labbé
  • Re: August 2024 stabilization week Olivier Cochard-Labbé
  • Re: August 2024 stabilization week Alan Somers
• GENERIC boot hangs on `enabling pf` Alexander Ziaee
  • Re: GENERIC boot hangs on `enabling pf` Ronald Klop

• Earlier messages
• Later messages