freebsd-current  

Messages by Thread

• • Re: bridge: no traffic with vnet (epair) beyond bridge device Alexander Leidinger
  • Re: bridge: no traffic with vnet (epair) beyond bridge device FreeBSD User
• Call for 2024Q2 status reports Lorenzo Salvadore
• mesa-dri-24.0.8 failing to build on d1bd097d52cb Nuno Teixeira
  • Re: mesa-dri-24.0.8 failing to build on d1bd097d52cb Nuno Teixeira
  • Re: mesa-dri-24.0.8 failing to build on d1bd097d52cb Cy Schubert
  • Re: mesa-dri-24.0.8 failing to build on d1bd097d52cb Cy Schubert
• CURRENT: exec_machdep.c:80:2: error: KDB must be enabled in order for DDB FreeBSD User
  • Re: CURRENT: exec_machdep.c:80:2: error: KDB must be enabled in order for DDB Gary Jennejohn
• Re: [Bug 269133] bnxt(4): BCM57416 - HWRM_CFA_L2_SET_RX_MASK command returned RESOURCE_ALLOC_ERROR error Santiago Martinez
  • Re: [Bug 269133] bnxt(4): BCM57416 - HWRM_CFA_L2_SET_RX_MASK command returned RESOURCE_ALLOC_ERROR error Warner Losh
  • Re: [Bug 269133] bnxt(4): BCM57416 - HWRM_CFA_L2_SET_RX_MASK command returned RESOURCE_ALLOC_ERROR error Warner Losh
  • Re: [Bug 269133] bnxt(4): BCM57416 - HWRM_CFA_L2_SET_RX_MASK command returned RESOURCE_ALLOC_ERROR error Gerrit Kühn
  • Re: [Bug 269133] bnxt(4): BCM57416 - HWRM_CFA_L2_SET_RX_MASK command returned RESOURCE_ALLOC_ERROR error Santiago Martinez
  • Re: [Bug 269133] bnxt(4): BCM57416 - HWRM_CFA_L2_SET_RX_MASK command returned RESOURCE_ALLOC_ERROR error Gerrit Kühn
  • Re: [Bug 269133] bnxt(4): BCM57416 - HWRM_CFA_L2_SET_RX_MASK command returned RESOURCE_ALLOC_ERROR error Santiago Martinez
  • Re: [Bug 269133] bnxt(4): BCM57416 - HWRM_CFA_L2_SET_RX_MASK command returned RESOURCE_ALLOC_ERROR error Gerrit Kühn
  • Re: [Bug 269133] bnxt(4): BCM57416 - HWRM_CFA_L2_SET_RX_MASK command returned RESOURCE_ALLOC_ERROR error Santiago Martinez
  • Re: [Bug 269133] bnxt(4): BCM57416 - HWRM_CFA_L2_SET_RX_MASK command returned RESOURCE_ALLOC_ERROR error Gerrit Kühn
  • Re: [Bug 269133] bnxt(4): BCM57416 - HWRM_CFA_L2_SET_RX_MASK command returned RESOURCE_ALLOC_ERROR error Warner Losh
• [HEADSUP] broken kernels for head this week for pkgbase Baptiste Daroussin
• May 2024 stabilization week Gleb Smirnoff
  • Re: May 2024 stabilization week Gleb Smirnoff
  • Re: May 2024 stabilization week Alexander Leidinger
  • Re: May 2024 stabilization week void
  • Re: May 2024 stabilization week Gleb Smirnoff
  • Re: May 2024 stabilization week void
  • Re: May 2024 stabilization week Mike Karels
  • Re: May 2024 stabilization week Service Aktionheizung
  • Re: May 2024 stabilization week void
  • Re: May 2024 stabilization week Mike Karels
  • Re: May 2024 stabilization week void
• Re: CURRENT kernel crash beyond git: 02d15215cef2 Herbert J. Skuhra
  • Re: CURRENT kernel crash beyond git: 02d15215cef2 FreeBSD User
  • Re: CURRENT kernel crash beyond git: 02d15215cef2 Graham Perrin
• main cadd2ca217 doesn't boot Nuno Teixeira
  • Re: main cadd2ca217 doesn't boot Tomoaki AOKI
  • Re: main cadd2ca217 doesn't boot Ryan Libby
  • Re: main cadd2ca217 doesn't boot Bojan Novković
  • Re: main cadd2ca217 doesn't boot tuexen
  • Re: main cadd2ca217 doesn't boot Oleg Nauman
  • Re: main cadd2ca217 doesn't boot David Wolfskill
  • Re: main cadd2ca217 doesn't boot FreeBSD User
• panic: lock "tmpfsni" 0xfffff80721307090 already initialized Alexander Leidinger
  • Re: panic: lock "tmpfsni" 0xfffff80721307090 already initialized Ryan Libby
• build of main broken? (ld: error: version script assignment of 'FBSD_1.0' to symbol 'xdr_...' failed: symbol not defined) Matteo Riondato
  • Re: build of main broken? (ld: error: version script assignment of 'FBSD_1.0' to symbol 'xdr_...' failed: symbol not defined) Dimitry Andric
  • Re: build of main broken? (ld: error: version script assignment of 'FBSD_1.0' to symbol 'xdr_...' failed: symbol not defined) Matteo Riondato
  • Re: build of main broken? (ld: error: version script assignment of 'FBSD_1.0' to symbol 'xdr_...' failed: symbol not defined) Ed Maste
• Chromium with Widevine: kernel panic: condition vp->v_type == VDIR || VN_IS_DOOMED(vp) not met ⋯vfs_cache.c:3452 (vn_fullpath_dir) Graham Perrin
• _mtx_lock_sleep: recursed on non-recursive mutex CAM device lock @ /..../sys/cam/nvme/nvme_da.c:469 Alexander Leidinger
  • Re: _mtx_lock_sleep: recursed on non-recursive mutex CAM device lock @ /..../sys/cam/nvme/nvme_da.c:469 Warner Losh
  • Re: _mtx_lock_sleep: recursed on non-recursive mutex CAM device lock @ /..../sys/cam/nvme/nvme_da.c:469 Alexander Leidinger
  • Re: _mtx_lock_sleep: recursed on non-recursive mutex CAM device lock @ /..../sys/cam/nvme/nvme_da.c:469 Alexander Leidinger
• devd nomatch does not load uslcom anymore Ronald Klop
  • Re: devd nomatch does not load uslcom anymore Warner Losh
• __memcpy_chk family of functions Marcin Cieslak
  • Re: __memcpy_chk family of functions Dag-Erling Smørgrav
  • Re: __memcpy_chk family of functions Warner Losh
  • Re: __memcpy_chk family of functions Marcin Cieslak
  • Re: __memcpy_chk family of functions Dag-Erling Smørgrav
  • Re: __memcpy_chk family of functions Marcin Cieslak
  • Re: __memcpy_chk family of functions Dag-Erling Smørgrav
• usb mouse not work on boot Oleksandr Kryvulia
  • Re: usb mouse not work on boot Gary Jennejohn
  • Re: usb mouse not work on boot Oleksandr Kryvulia
  • Re: usb mouse not work on boot Nuno Teixeira
  • Re: usb mouse not work on boot Dag-Erling Smørgrav
  • Re: usb mouse not work on boot Oleksandr Kryvulia
  • Re: usb mouse not work on boot Oleksandr Kryvulia
  • Re: usb mouse not work on boot Warner Losh
  • Re: usb mouse not work on boot Oleksandr Kryvulia
  • Re: usb mouse not work on boot Warner Losh
  • RES: usb mouse not work on boot Ivan Quitschal
  • Re: RES: usb mouse not work on boot Oleksandr Kryvulia
  • RES: RES: usb mouse not work on boot Ivan Quitschal
  • Re: RES: RES: usb mouse not work on boot Oleksandr Kryvulia
  • Re: RES: usb mouse not work on boot Dag-Erling Smørgrav
  • RES: RES: usb mouse not work on boot Ivan Quitschal
  • RES: RES: usb mouse not work on boot Ivan Quitschal
  • Re: RES: RES: usb mouse not work on boot Dag-Erling Smørgrav
  • RES: RES: RES: usb mouse not work on boot Ivan Quitschal
  • Re: usb mouse not work on boot Chris
  • Re: usb mouse not work on boot Warner Losh
  • Re: usb mouse not work on boot Oleksandr Kryvulia
• usb devices discovery delay Nuno Teixeira
• kldload tpm: Fail to load: "link_elf_obj: symbol tpm_bus_driver undefined" Nuno Teixeira
  • Re: kldload tpm: Fail to load: "link_elf_obj: symbol tpm_bus_driver undefined" Justin Hibbits
  • Re: kldload tpm: Fail to load: "link_elf_obj: symbol tpm_bus_driver undefined" Nuno Teixeira
• bsdinstall wifi setup is broken on CURRENT Renato Botelho
  • Re: bsdinstall wifi setup is broken on CURRENT Jessica Clarke
  • Re: bsdinstall wifi setup is broken on CURRENT Renato Botelho
  • Re: bsdinstall wifi setup is broken on CURRENT Nuno Teixeira
  • Re: bsdinstall wifi setup is broken on CURRENT Dag-Erling Smørgrav
  • Re: bsdinstall wifi setup is broken on CURRENT Alfonso S. Siciliano
  • Re: bsdinstall wifi setup is broken on CURRENT Renato Botelho
  • Re: bsdinstall wifi setup is broken on CURRENT Renato Botelho
  • bsdinstall wifi setup is broken on CURRENT SAH
• Panic: lock "lnxspin" 0xfffff800176c0730 already initialized David Wolfskill
  • Re: Panic: lock "lnxspin" 0xfffff800176c0730 already initialized Ryan Libby
  • Re: Panic: lock "lnxspin" 0xfffff800176c0730 already initialized Emmanuel Vadot
  • Re: Panic: lock "lnxspin" 0xfffff800176c0730 already initialized Ryan Libby
  • Re: Panic: lock "lnxspin" 0xfffff800176c0730 already initialized Emmanuel Vadot
  • Re: Panic: lock "lnxspin" 0xfffff800176c0730 already initialized David Wolfskill
• gcc behavior of init priority of .ctors and .dtors section Zhenlei Huang
  • Re: gcc behavior of init priority of .ctors and .dtors section Konstantin Belousov
  • Re: gcc behavior of init priority of .ctors and .dtors section Lorenzo Salvadore
  • Re: gcc behavior of init priority of .ctors and .dtors section Konstantin Belousov
  • Re: gcc behavior of init priority of .ctors and .dtors section John Baldwin
  • Re: gcc behavior of init priority of .ctors and .dtors section Zhenlei Huang
• pkg scripts need updating Michael Butler
  • Re: pkg scripts need updating Enji Cooper
  • Re: pkg scripts need updating Stefan Esser
• termcap.db unused? Jamie Landeg-Jones
• Graph of the FreeBSD memory fragmentation Alexander Leidinger
  • Re: Graph of the FreeBSD memory fragmentation Bojan Novković
  • Re: Graph of the FreeBSD memory fragmentation Alexander Leidinger
  • Re: Graph of the FreeBSD memory fragmentation Ryan Libby
  • Re: Graph of the FreeBSD memory fragmentation Alexander Leidinger
  • Re: Graph of the FreeBSD memory fragmentation Ryan Libby
  • Re: Graph of the FreeBSD memory fragmentation Ryan Libby
  • Re: Graph of the FreeBSD memory fragmentation Mike Jakubik
• FreeBSD Status Report - First Quarter 2024 Lorenzo Salvadore
• Kenny Wayne Shepherd - Voodoo Child (Slight Return) Bakul Shah
• main [so: 15] amd64: Rare poudriere bulk builder "stuck in umtxq_sleep" condition (race failure?) during high-load-average "poudriere bulk -c -a" runs Mark Millard
  • Re: main [so: 15] amd64: Rare poudriere bulk builder "stuck in umtxq_sleep" condition (race failure?) during high-load-average "poudriere bulk -c -a" runs Mark Millard
• 14.1-PRERELEASE boot stuck on feeding entropy cglogic
• build failure affecting port: "error: reference to 'filesystem' is ambiguous" Nuno Teixeira
  • Re: build failure affecting port: "error: reference to 'filesystem' is ambiguous" Dimitry Andric
  • Re: build failure affecting port: "error: reference to 'filesystem' is ambiguous" Nuno Teixeira
  • Re: build failure affecting port: "error: reference to 'filesystem' is ambiguous" Dimitry Andric
• Request for non-GENERIC kernel diff Vladislav V. Prodan
• mysterious setting of B_DIRECT? Rick Macklem
  • Re: mysterious setting of B_DIRECT? Konstantin Belousov
  • Re: mysterious setting of B_DIRECT? Rick Macklem
  • Re: mysterious setting of B_DIRECT? Rick Macklem
• serial/ulscom: response timeout using pySerial/esptool.py FreeBSD User
  • Re: serial/ulscom: response timeout using pySerial/esptool.py Tomek CEDRO
  • Re: serial/ulscom: response timeout using pySerial/esptool.py FreeBSD User
  • Re: serial/ulscom: response timeout using pySerial/esptool.py FreeBSD User
  • Re: serial/ulscom: response timeout using pySerial/esptool.py Tom Jones
• TXT Kernel linking failed on -CURRENT BSD USER
  • Re: TXT Kernel linking failed on -CURRENT Konstantin Belousov
  • Re: TXT Kernel linking failed on -CURRENT BSD USER
• Kernel linking error on -CURRENT USER BSD
• April 2024 stabilization week Gleb Smirnoff
  • Re: April 2024 stabilization week Gleb Smirnoff
  • Re: April 2024 stabilization week Gleb Smirnoff
• Strange network/socket anomalies since about a month Alexander Leidinger
  • Re: Strange network/socket anomalies since about a month Paul Mather
  • Re: Strange network/socket anomalies since about a month Gleb Smirnoff
  • Re: Strange network/socket anomalies since about a month Alexander Leidinger
  • Re: Strange network/socket anomalies since about a month Dag-Erling Smørgrav
• etc/rc.d/nuageinit sometimes missing Mark Millard
• libclang_rt.asan_static-aarch64.a and libclang_rt.fuzzer_interceptors-aarch64.a in .../tmp/lib/clang/17/lib/freebsd/ not cleaned out Mark Millard
• Unfamiliar console message: in prompt_tty(): caught signal 2 bob prohaska
  • Re: Unfamiliar console message: in prompt_tty(): caught signal 2 Dag-Erling Smørgrav
  • Re: Unfamiliar console message: in prompt_tty(): caught signal 2 bob prohaska
  • Re: Unfamiliar console message: in prompt_tty(): caught signal 2 Enji Cooper
• pkg server for current/arm64 stopped ? [main-armv7 on ampere2, elapsed so far: 651:21:56] Mark Millard
  • Re: pkg server for current/arm64 stopped ? [main-armv7 on ampere2, elapsed so far: 651:21:56] Mark Millard
  • Re: pkg server for current/arm64 stopped ? [main-armv7 on ampere2, elapsed so far: 651:21:56] Philip Paeps
  • Re: pkg server for current/arm64 stopped ? [main-armv7 on ampere2, elapsed so far: 651:21:56] Mark Millard
  • Re: pkg server for current/arm64 stopped ? [main-armv7 on ampere2, elapsed so far: 651:21:56] Mark Millard
  • Re: pkg server for current/arm64 stopped ? [main-armv7 on ampere2, elapsed so far: 651:21:56] Mark Millard
  • Re: pkg server for current/arm64 stopped ? [main-armv7 on ampere2, . . .] [Update to Host OSVERSION 1500018 did not help] Mark Millard
  • Re: pkg server for current/arm64 stopped ? [main-armv7 on ampere2, . . .] [Update to Host OSVERSION 1500018 did not help] Philip Paeps
  • Re: pkg server for current/arm64 stopped ? [main-armv7 on ampere2, elapsed so far: 651:21:56] void
  • Re: pkg server for current/arm64 stopped ? [main-armv7 on ampere2, elapsed so far: 651:21:56] Philip Paeps
  • Re: pkg server for current/arm64 stopped ? [main-armv7 on ampere2, elapsed so far: 651:21:56] Mark Millard
  • Re: pkg server for current/arm64 stopped ? [main-armv7 on ampere2, elapsed so far: 651:21:56] Philip Paeps
  • Re: pkg server for current/arm64 stopped ? [main-armv7 on ampere2, elapsed so far: 651:21:56] Philip Paeps
  • Re: pkg server for current/arm64 stopped ? [main-armv7 on ampere2, elapsed so far: 651:21:56] Mark Millard
• llvm and Undefined symbols: ___truncsfbf2 problem Hiroo Ono
  • Re: llvm and Undefined symbols: ___truncsfbf2 problem Dimitry Andric
  • Re: llvm and Undefined symbols: ___truncsfbf2 problem Hiroo Ono
• Re: Panic after update main-n269202-4e7aa03b7076 -> n269230-f6f67f58c19d Cy Schubert
• Panic after update main-n269202-4e7aa03b7076 -> n269230-f6f67f58c19d David Wolfskill
  • Re: Panic after update main-n269202-4e7aa03b7076 -> n269230-f6f67f58c19d Rick Macklem
  • Re: Panic after update main-n269202-4e7aa03b7076 -> n269230-f6f67f58c19d Rick Macklem
  • Re: Panic after update main-n269202-4e7aa03b7076 -> n269230-f6f67f58c19d Rick Macklem
  • Re: Panic after update main-n269202-4e7aa03b7076 -> n269230-f6f67f58c19d Gleb Smirnoff
  • Re: Panic after update main-n269202-4e7aa03b7076 -> n269230-f6f67f58c19d David Wolfskill
  • Re: Panic after update main-n269202-4e7aa03b7076 -> n269230-f6f67f58c19d FreeBSD User
  • Re: Panic after update main-n269202-4e7aa03b7076 -> n269230-f6f67f58c19d Gleb Smirnoff
  • Resolved: Panic after update main-n269202-4e7aa03b7076 -> n269230-f6f67f58c19d David Wolfskill
• RFC: Does anyone use the -public/-webnfs NFS exports? Rick Macklem
• pkg-1.21.0: after upgrade 1.20.9_1 -> 1.21.0: pkg core dumps on specific ports FreeBSD User
  • Re: pkg-1.21.0: after upgrade 1.20.9_1 -> 1.21.0: pkg core dumps on specific ports Rainer Hurling
  • Re: pkg-1.21.0: after upgrade 1.20.9_1 -> 1.21.0: pkg core dumps on specific ports Baptiste Daroussin
  • Re: pkg-1.21.0: after upgrade 1.20.9_1 -> 1.21.0: pkg core dumps on specific ports Rainer Hurling
  • Re: pkg-1.21.0: after upgrade 1.20.9_1 -> 1.21.0: pkg core dumps on specific ports FreeBSD User
  • Re: pkg-1.21.0: after upgrade 1.20.9_1 -> 1.21.0: pkg core dumps on specific ports Baptiste Daroussin
  • Re: pkg-1.21.0: after upgrade 1.20.9_1 -> 1.21.0: pkg core dumps on specific ports Rainer Hurling
  • Re: pkg-1.21.0: after upgrade 1.20.9_1 -> 1.21.0: pkg-static core dumps on some ports FreeBSD User
  • Re: pkg-1.21.0: after upgrade 1.20.9_1 -> 1.21.0: pkg core dumps on specific ports Baptiste Daroussin
• Re: CVE-2024-3094: malicious code in xz 5.6.0 and xz 5.6.1 Paul Floyd
  • Re: CVE-2024-3094: malicious code in xz 5.6.0 and xz 5.6.1 sthaug
  • Re: CVE-2024-3094: malicious code in xz 5.6.0 and xz 5.6.1 FreeBSD User
  • Re: CVE-2024-3094: malicious code in xz 5.6.0 and xz 5.6.1 Kyle Evans

• Earlier messages
• Later messages