freebsd-stable@FreeBSD.org

Production branch of FreeBSD source code

Go to: [ monthly archives ] [ by author ] [ by date ]

January 2024 Archives by thread

sysutils/screen compilation oddities on stable-14: Jonathan Chen (Mon, 01 Jan 2024 06:06:35 UTC)

Re: sysutils/screen compilation oddities on stable-14: Cy Schubert (Tue, 02 Jan 2024 21:15:24 UTC)
Re: sysutils/screen compilation oddities on stable-14: Jonathan Chen (Tue, 02 Jan 2024 22:56:58 UTC)

Re: sysutils/screen compilation oddities on stable-14: Cy Schubert (Tue, 02 Jan 2024 23:16:36 UTC)

Re: SIGILL when CPUTYPE set to anyting witjh avx and CFLAGS -O2: Jamie Landeg-Jones (Tue, 02 Jan 2024 19:50:56 UTC)
RELENG_13 kernel breakage: mike tancsa (Wed, 03 Jan 2024 13:47:31 UTC)
deleted (X-No-Archive): deleted (Wed, 03 Jan 2024 13:55:49 UTC)

Re: RELENG_13 kernel breakage: Rick Macklem (Wed, 03 Jan 2024 15:46:40 UTC)

deleted (X-No-Archive): deleted (Wed, 03 Jan 2024 16:23:52 UTC)
ports-mgmt/portconfig surprize: Peter (Thu, 04 Jan 2024 23:35:43 UTC)

Re: ports-mgmt/portconfig surprize: Kyle Evans (Fri, 05 Jan 2024 00:03:41 UTC)
Re: ports-mgmt/portconfig surprize: Cy Schubert (Fri, 05 Jan 2024 15:56:16 UTC)

Re: ports-mgmt/portconfig surprize: Peter (Fri, 05 Jan 2024 23:05:17 UTC)

Re: ports-mgmt/portconfig surprize: Cy Schubert (Fri, 05 Jan 2024 23:21:01 UTC)

Re: ports-mgmt/portconfig surprize: Alfonso Sabato Siciliano (Fri, 05 Jan 2024 23:00:13 UTC)

Re: ports-mgmt/portconfig surprize: Peter (Fri, 05 Jan 2024 23:40:03 UTC)

FreeBSD 13.2-STABLE can not boot from damaged mirror AND pool stuck in "resilver" state even without new devices.: Lev Serebryakov (Fri, 05 Jan 2024 17:28:55 UTC)

Re: FreeBSD 13.2-STABLE can not boot from damaged mirror AND pool stuck in "resilver" state even without new devices.: Lev Serebryakov (Sun, 07 Jan 2024 14:49:56 UTC)

Re: FreeBSD 13.2-STABLE can not boot from damaged mirror AND pool stuck in "resilver" state even without new devices.: Karl Denninger (Sun, 07 Jan 2024 14:51:35 UTC)

Re: FreeBSD 13.2-STABLE can not boot from damaged mirror AND pool stuck in "resilver" state even without new devices.: Lev Serebryakov (Sun, 07 Jan 2024 15:04:36 UTC)

Re: FreeBSD 13.2-STABLE can not boot from damaged mirror AND pool stuck in "resilver" state even without new devices.: Miroslav Lachman (Sun, 07 Jan 2024 15:38:04 UTC)

Re: FreeBSD 13.2-STABLE can not boot from damaged mirror AND pool stuck in "resilver" state even without new devices.: Karl Denninger (Sun, 07 Jan 2024 15:50:19 UTC)
Re: FreeBSD 13.2-STABLE can not boot from damaged mirror AND pool stuck in "resilver" state even without new devices.: Lev Serebryakov (Sun, 07 Jan 2024 17:56:58 UTC)

Re: FreeBSD 13.2-STABLE can not boot from damaged mirror AND pool stuck in "resilver" state even without new devices.: Warner Losh (Sun, 07 Jan 2024 18:34:06 UTC)

Re: FreeBSD 13.2-STABLE can not boot from damaged mirror AND pool stuck in "resilver" state even without new devices.: Miroslav Lachman (Sun, 07 Jan 2024 19:01:18 UTC)

Re: FreeBSD 13.2-STABLE can not boot from damaged mirror AND pool stuck in "resilver" state even without new devices.: Warner Losh (Sun, 07 Jan 2024 21:06:26 UTC)

Re: FreeBSD 13.2-STABLE can not boot from damaged mirror AND pool stuck in "resilver" state even without new devices.: Lev Serebryakov (Sun, 07 Jan 2024 20:49:24 UTC)

Re: FreeBSD 13.2-STABLE can not boot from damaged mirror AND pool stuck in "resilver" state even without new devices.: Lev Serebryakov (Sun, 07 Jan 2024 20:56:59 UTC)

Re: FreeBSD 13.2-STABLE can not boot from damaged mirror AND pool stuck in "resilver" state even without new devices.: Warner Losh (Sun, 07 Jan 2024 21:15:14 UTC)

Re: FreeBSD 13.2-STABLE can not boot from damaged mirror AND pool stuck in "resilver" state even without new devices.: Lev Serebryakov (Sun, 07 Jan 2024 21:19:33 UTC)
Re: FreeBSD 13.2-STABLE can not boot from damaged mirror AND pool stuck in "resilver" state even without new devices.: Larry Rosenman (Mon, 08 Jan 2024 00:15:47 UTC)
Re: FreeBSD 13.2-STABLE can not boot from damaged mirror AND pool stuck in "resilver" state even without new devices.: Lev Serebryakov (Mon, 08 Jan 2024 11:15:21 UTC)
Re: FreeBSD 13.2-STABLE can not boot from damaged mirror AND pool stuck in "resilver" state even without new devices.: Larry Rosenman (Mon, 08 Jan 2024 15:44:12 UTC)
Re: FreeBSD 13.2-STABLE can not boot from damaged mirror AND pool stuck in "resilver" state even without new devices.: Lev Serebryakov (Mon, 08 Jan 2024 17:27:03 UTC)

deleted (X-No-Archive): deleted (Sat, 06 Jan 2024 07:06:41 UTC)
Re: Odd values for various memory metrics via SNMP: Patrick M. Hausen (Sat, 06 Jan 2024 12:02:26 UTC)

Re: Odd values for various memory metrics via SNMP: Garrett Wollman (Thu, 11 Jan 2024 03:04:51 UTC)

devfs_set_rulesets="path=devfsrules_hide_all path=devfsrules_unhide_basic" doesn't work after upgrade from 12-STABLE to 13-STABLE: Lev Serebryakov (Sun, 07 Jan 2024 14:56:27 UTC)
Crash on adding L2ARC to raidz1 pool: Lev Serebryakov (Mon, 08 Jan 2024 17:34:24 UTC)

vfs.zfs.compressed_arc_enabled=0 is INCOMPATIBLE with L2ARC at least in FreeBSD 13 (Was: Crash on adding L2ARC to raidz1 pool): Lev Serebryakov (Sat, 13 Jan 2024 11:26:36 UTC)

Re: vfs.zfs.compressed_arc_enabled=0 is INCOMPATIBLE with L2ARC at least in FreeBSD 13 (Was: Crash on adding L2ARC to raidz1 pool): Alexander Burke (Sat, 13 Jan 2024 17:11:18 UTC)

Re: vfs.zfs.compressed_arc_enabled=0 is INCOMPATIBLE with L2ARC at least in FreeBSD 13 (Was: Crash on adding L2ARC to raidz1 pool): Lev Serebryakov (Sat, 13 Jan 2024 17:35:46 UTC)
Re: vfs.zfs.compressed_arc_enabled=0 is INCOMPATIBLE with L2ARC at least in FreeBSD 13 (Was: Crash on adding L2ARC to raidz1 pool): Peter 'PMc' Much (Sat, 13 Jan 2024 22:16:38 UTC)

clang 17 and ports fallout: mike tancsa (Mon, 08 Jan 2024 20:40:31 UTC)

Re: clang 17 and ports fallout: mike tancsa (Mon, 08 Jan 2024 20:57:10 UTC)

Re: clang 17 and ports fallout: Dimitry Andric (Mon, 08 Jan 2024 22:50:31 UTC)

Re: clang 17 and ports fallout: mike tancsa (Tue, 09 Jan 2024 13:18:46 UTC)

Re: clang 17 and ports fallout: Antoine Brodin (Wed, 10 Jan 2024 07:53:38 UTC)

Re: clang 17 and ports fallout: mike tancsa (Wed, 10 Jan 2024 12:16:51 UTC)

Re: clang 17 and ports fallout: Dimitry Andric (Wed, 10 Jan 2024 16:22:10 UTC)

Re: clang 17 and ports fallout: Dimitry Andric (Wed, 10 Jan 2024 17:59:05 UTC)

kern.version and uname -v: Eugene Grosbein (Mon, 08 Jan 2024 20:57:28 UTC)

Re: kern.version and uname -v: Warner Losh (Mon, 08 Jan 2024 21:16:43 UTC)

Re: kern.version and uname -v: Juraj Lutter (Mon, 08 Jan 2024 21:26:00 UTC)
Re: kern.version and uname -v: Eugene Grosbein (Tue, 09 Jan 2024 02:17:27 UTC)

Re: kern.version and uname -v: Warner Losh (Tue, 09 Jan 2024 03:29:23 UTC)

Re: kern.version and uname -v: henrichhartzer_at_tuta.io (Tue, 09 Jan 2024 20:23:36 UTC)

LinuxKPI fix for 13.3: Greg Balfour (Tue, 09 Jan 2024 17:29:35 UTC)

Re: LinuxKPI fix for 13.3: Mark Johnston (Tue, 09 Jan 2024 18:00:18 UTC)

Re: 15 & 14: ram_attach vs. its using regions_to_avail vs. "bus_alloc_resource" can lead to: panic("ram_attach: resource %d failed to attach", rid): Doug Rabson (Fri, 12 Jan 2024 17:57:30 UTC)

Re: 15 & 14: ram_attach vs. its using regions_to_avail vs. "bus_alloc_resource" can lead to: panic("ram_attach: resource %d failed to attach", rid): Mark Millard (Fri, 12 Jan 2024 21:53:15 UTC)

leap-second error in console: void (Mon, 15 Jan 2024 00:37:19 UTC)

Re: leap-second error in console: Warner Losh (Mon, 15 Jan 2024 01:45:39 UTC)

Re: leap-second error in console: Doug Hardie (Mon, 15 Jan 2024 02:39:59 UTC)

Re: leap-second error in console: Bakul Shah (Mon, 15 Jan 2024 02:46:15 UTC)

Re: leap-second error in console: Jonathan Adams (Mon, 15 Jan 2024 03:24:29 UTC)

Re: leap-second error in console: Doug Hardie (Mon, 15 Jan 2024 03:32:00 UTC)

Re: leap-second error in console: void (Mon, 15 Jan 2024 03:53:24 UTC)

hwpstate_intel epp performance oddities: Sean C. Farley (Mon, 15 Jan 2024 17:48:52 UTC)
Avoiding the wait for root mount: Sean C. Farley (Mon, 15 Jan 2024 18:02:14 UTC)
tracking down i386 mount issue between Aug 2023 and now-- RELENG_13: mike tancsa (Tue, 16 Jan 2024 14:48:43 UTC)

Re: tracking down i386 mount issue between Aug 2023 and now-- RELENG_13: mike tancsa (Wed, 17 Jan 2024 14:02:34 UTC)
Re: tracking down i386 mount issue between Aug 2023 and now-- RELENG_13: mike tancsa (Mon, 29 Jan 2024 15:45:01 UTC)

Re: Repeatable nfs_readdir kernel panic after upgrade to stable/14: Konstantin Belousov (Wed, 17 Jan 2024 10:07:13 UTC)

Re: Repeatable nfs_readdir kernel panic after upgrade to stable/14: Ulrich_Spörlein (Fri, 19 Jan 2024 15:42:53 UTC)

git log - how to find out latest stable/14 breakage: Harry Schmalzbauer (Sat, 20 Jan 2024 12:47:05 UTC)

Re: git log - how to find out latest stable/14 breakage: Mike Karels (Sat, 20 Jan 2024 14:10:33 UTC)

Re: git log - how to find out latest stable/14 breakage: Harry Schmalzbauer (Sat, 20 Jan 2024 15:13:59 UTC)

Re: git log - how to find out latest stable/14 breakage: Christian Weisgerber (Sat, 20 Jan 2024 14:58:21 UTC)

Re: git log - how to find out latest stable/14 breakage: Harry Schmalzbauer (Sat, 20 Jan 2024 15:35:55 UTC)

Re: git log - how to find out latest stable/14 breakage: Peter 'PMc' Much (Sat, 20 Jan 2024 15:12:12 UTC)

mounting NFS share from the jail: Marek Zarychta (Sat, 20 Jan 2024 14:47:54 UTC)

Re: mounting NFS share from the jail: Rick Macklem (Sat, 20 Jan 2024 15:09:40 UTC)

Re: mounting NFS share from the jail: Marek Zarychta (Sat, 20 Jan 2024 15:47:47 UTC)
Re: mounting NFS share from the jail: Charles Sprickman (Sat, 20 Jan 2024 18:54:51 UTC)

Re: mounting NFS share from the jail: Rick Macklem (Sat, 20 Jan 2024 22:06:04 UTC)

Should changes in src/usr.sbin/bhyve/ trigger an llvm rebuild?: David Wolfskill (Sun, 28 Jan 2024 11:50:44 UTC)
RE: Should changes in src/usr.sbin/bhyve/ trigger an llvm rebuild?: Mark Millard (Sun, 28 Jan 2024 15:30:53 UTC)

Re: Should changes in src/usr.sbin/bhyve/ trigger an llvm rebuild?: David Wolfskill (Sun, 28 Jan 2024 15:46:03 UTC)

Re: Should changes in src/usr.sbin/bhyve/ trigger an llvm rebuild?: Mark Millard (Sun, 28 Jan 2024 18:20:30 UTC)

Re: Should changes in src/usr.sbin/bhyve/ trigger an llvm rebuild?: David Wolfskill (Sun, 28 Jan 2024 22:06:01 UTC)

Re: Should changes in src/usr.sbin/bhyve/ trigger an llvm rebuild?: Mark Millard (Sun, 28 Jan 2024 22:34:21 UTC)

Re: Should changes in src/usr.sbin/bhyve/ trigger an llvm rebuild?: Mark Millard (Sun, 28 Jan 2024 23:00:59 UTC)

Re: Should changes in src/usr.sbin/bhyve/ trigger an llvm rebuild?: David Wolfskill (Mon, 29 Jan 2024 00:05:03 UTC)

Re: Should changes in src/usr.sbin/bhyve/ trigger an llvm rebuild?: Mark Millard (Mon, 29 Jan 2024 01:13:24 UTC)

Re: Should changes in src/usr.sbin/bhyve/ trigger an llvm rebuild?: David Wolfskill (Mon, 29 Jan 2024 01:33:49 UTC)
Re: Should changes in src/usr.sbin/bhyve/ trigger an llvm rebuild?: Mark Millard (Mon, 29 Jan 2024 04:55:43 UTC)

Re: Should changes in src/usr.sbin/bhyve/ trigger an llvm rebuild?: Alexander Leidinger (Mon, 29 Jan 2024 09:50:18 UTC)

Re: Should changes in src/usr.sbin/bhyve/ trigger an llvm rebuild?: Mark Millard (Mon, 29 Jan 2024 18:07:18 UTC)

Re: Should changes in src/usr.sbin/bhyve/ trigger an llvm rebuild?: Alexander Leidinger (Tue, 30 Jan 2024 06:56:19 UTC)

Go to: [ monthly archives ] [ by author ] [ by date ]