Re: panic after a97f683fe3c425

2024-11-07 Thread Oleksandr Kryvulia
07.11.24 22:03, Mark Johnston: On Thu, Nov 07, 2024 at 09:43:50PM +0200, Oleksandr Kryvulia wrote: Hi, @current My laptop now panics while boot with [1]. git bisect shows a97f683fe3c425b425cf8cc466319f54ea957c20 as offending commit. [1] https://imgur.com/a/Pb6eakW I believe the patch below wi

Re: BRT copying feature

2024-11-07 Thread Craig Leres
(Forgot to include screen grabs)

Re: No valid device tree blob found!

2024-11-07 Thread Alexander Leidinger
Am 2024-11-07 20:59, schrieb Warner Losh: On Wed, Nov 6, 2024 at 3:41 AM Alexander Leidinger wrote: Am 2024-11-02 17:08, schrieb Warner Losh: On Sat, Nov 2, 2024, 10:03 AM Alexander Leidinger wrote: Am 2024-10-30 22:11, schrieb Alexander Leidinger: WARNING! Trying to fire up the kernel

Re: No valid device tree blob found!

2024-11-07 Thread Warner Losh
On Wed, Nov 6, 2024 at 3:41 AM Alexander Leidinger wrote: > Am 2024-11-02 17:08, schrieb Warner Losh: > > > > On Sat, Nov 2, 2024, 10:03 AM Alexander Leidinger > wrote: > > Am 2024-10-30 22:11, schrieb Alexander Leidinger: > > > WARNING! Trying to fire up the kernel, but no device tree blob foun

panic after a97f683fe3c425

2024-11-07 Thread Oleksandr Kryvulia
Hi, @current My laptop now panics while boot with [1]. git bisect shows a97f683fe3c425b425cf8cc466319f54ea957c20 as offending commit. [1] https://imgur.com/a/Pb6eakW

Re: panic after a97f683fe3c425

2024-11-07 Thread Mark Johnston
On Thu, Nov 07, 2024 at 09:43:50PM +0200, Oleksandr Kryvulia wrote: > Hi, @current > > My laptop now panics while boot with [1]. > git bisect shows a97f683fe3c425b425cf8cc466319f54ea957c20 as offending > commit. > > [1] https://imgur.com/a/Pb6eakW I believe the patch below will fix the problem.

Re: BRT copying feature

2024-11-07 Thread Craig Leres
On 11/7/24 07:31, Ronald Klop wrote: Another option is this. The installer /usr/sbin/bsdinstall uses a script called /usr/libexec/ bsdinstall/zfsboot. Zfsboot defines this: # # Default options to use when creating zroot pool # : ${ZFSBOOT_POOL_CREATE_OPTIONS:=-O compress=lz4 -O atime=off} Yo

Official armv7 PkgBase kernel-NODEBUG installation's USB2 boot gets "Fatal kernel mode data abort: 'Alignment Fault' on write" very early, at least on an OrangePi+ 2ed

2024-11-07 Thread Mark Millard
Note: Unfortunately, the panics here are too early for a dump device to be available. Context started PkgBase upgrade from: # uname -apKU FreeBSD OPiP2E-RPi2v1p1 15.0-CURRENT FreeBSD 15.0-CURRENT main-n272821-37798b1d5dd1 GENERIC-NODEBUG arm armv7 1500025 1500025 Installed packages to be UPGRAD

Re: BRT copying feature

2024-11-07 Thread Ronald Klop
Hi, Another option is this. The installer /usr/sbin/bsdinstall uses a script called /usr/libexec/bsdinstall/zfsboot. Zfsboot defines this: # # Default options to use when creating zroot pool # : ${ZFSBOOT_POOL_CREATE_OPTIONS:=-O compress=lz4 -O atime=off} You can set this environment variabel

FreeBSD Status Report - Third Quarter 2024

2024-11-07 Thread Lorenzo Salvadore
FreeBSD Status Report Third Quarter 2024 Here is the third 2024 status report, with 32 entries. Unfortunately we are late this quarter, just like last quarter. As our readers know, many FreeBSD contributors are volunteers, so it is natural that less important deadlines like the status reports one

Re: BRT copying feature

2024-11-07 Thread Ronald Klop
Van: Johan Hendriks Datum: donderdag, 7 november 2024 11:43 Aan: Ronald Klop CC: FreeBSD Current Onderwerp: Re: BRT copying feature On 06/11/2024 13:15, Ronald Klop wrote: Hi, When you create a new pool you can use something like this: zpool create -o feature@block_cloning=disabled ...

Re: BRT copying feature

2024-11-07 Thread Johan Hendriks
On 06/11/2024 13:15, Ronald Klop wrote: Hi, When you create a new pool you can use something like this: zpool create -o feature@block_cloning=disabled ... I tried setting this on an existing pool. That gave me an error. # zpool set feature@block_cloning=disabled zdata4 cannot set property for

Re: No valid device tree blob found!

2024-11-07 Thread Warner Losh
OK. I'm confused... but no matter. Three more things to help... (1) kenv after boot with a fixed kernel (2) sudo efivar --device-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConIn (3) sudo efivar --device-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut Warner On Thu, Nov 7, 2024 at 2:41 PM Alexand

Re: Official armv7 PkgBase kernel-NODEBUG installation's USB2 boot gets "Fatal kernel mode data abort: 'Alignment Fault' on write" very early, at least on an OrangePi+ 2ed

2024-11-07 Thread Mark Millard
[I narrowed the artifact kernel range for the change in the type of failure that happens.] On Nov 7, 2024, at 17:43, Mark Millard wrote: > [The change to LLVM 19 is what leads to the Alignment > Fault' on write failure. Details later below.] > > On Nov 7, 2024, at 01:42, Mark Millard wrote: >

Re: Official armv7 PkgBase kernel-NODEBUG installation's USB2 boot gets "Fatal kernel mode data abort: 'Alignment Fault' on write" very early, at least on an OrangePi+ 2ed

2024-11-07 Thread Mark Millard
[The change to LLVM 19 is what leads to the Alignment Fault' on write failure. Details later below.] On Nov 7, 2024, at 01:42, Mark Millard wrote: > Note: Unfortunately, the panics here are too early for a > dump device to be available. > > Context started PkgBase upgrade from: > > # uname -ap