Root cause has been found, the next snap, whenever it will be out, will have the fixes!
Sorry it took so long, reverting wasn‘t a solution as that would have broken another machine, and it took some time too find out what was wrong. Cheers, Patrick > > On 20. Jun 2023, at 12:35, develo...@robert-palm.de wrote: > > > Quoting Mark Kettenis <mark.kette...@xs4all.nl>: > >>> Date: Tue, 20 Jun 2023 09:31:58 +0200 >>> From: develo...@robert-palm.de >>> >>> Hi, >>> >>> I noticed that an ARM64 installation with latest snapshots is not >>> possible any longer in hetzner cloud arm64 instances (ampere altra). >>> >>> Last snapshot working is >>> https://ftp.hostserver.de/archive/2023-06-18-0105/snapshots/arm64/miniroot73.img >>> >>> Later snapshots get stuck at "scsibus1 at softraid0: 256 targets". >>> >>> So it does not get to "root on rd0a swap on rd0b dump on rd0b" any more. >>> >>> Think there were 2 or 3 changes related to arm64 between (17-Jun-2023 >>> 06:36) and (18-Jun-2023 19:59) that might cause this. >>> >>> Please, can you have a look at it? >> >> The most likely candidate is: >> >> CVSROOT: /cvs >> Module name: src >> Changes by: kette...@cvs.openbsd.org 2023/06/18 10:25:21 >> >> Modified files: >> sys/arch/arm64/dev: agintc.c >> >> Log message: >> Remove spurious comment. >> >> ok patrick@ >> >> Can you try reverting that change and see of the resulting kernel boots? >> >> Also, I'd like to understand why you're hitting this case. Can you >> show a dmesg from the last working kernel? > > Thanks for your fast reply. > > Please find the dmesg_log.txt attached. > > Is it possible you revert the change and create a new miniroot.img file for > me ? > > Currently I am just using images. Need to figure out how to compile the > sources and create the image to try the installation again. > > > > > <dmesg_log.txt>
