Control: tag -1 moreinfo
[...]

Please test again with the current version (6.12.33-1~bpo12+1).  I think
this may have been fixed upstream by:

commit 3c44d31cb34ce4eb8311a2e73634d57702948230
Author: Herbert Xu <herbert@gondor.apana.org.au>
Date:   Sat Aug 17 14:58:35 2024 +0800

    crypto: simd - Do not call crypto_alloc_tfm during registration

Ben.

I did test with 6.12.35+deb12-armmp, the bug is still there, even a bit nastier. Kind of assumed that, as the commit you mentioned went into 6.1.113 and my last known working version is 6.6.13+bpo-armmp.

With 6.12.35+deb12-armmp, the kernel does not panic immediately during a boot attempt, but errors begin to appear soon. During my testing, I got many different messages mainly around the SATA subsystem (resetting the controller, ...). Some of them even indicated possible data corruption. I've got more errors (and they appeared earlier) when two SATA drives were attached, compared to having only a single drive. However, with either configuration, the system would hang sooner or later.

With 6.6.13+bpo-armmp, everything is running fine and stable with the same hardware.

I did save some logfiles, so I can send them if you wish. However, there is a ton of it with only small portions being relevant, so I would need some time to process them.

Phil

Here are the relevant portions of some boot transcripts as promised. I
apologise for the delay.

Several logs are attached. System behaviour during the attempts was as
follows:

boot1.log - despite the errors, the system comes up, displaying a login
            prompt; however, after entering the username, the system
            freezes(the expected password prompt is not shown)

boot2part[12].log - errors very similar to the first attempt (at first
                    glance); however, after entering the username, different
                    error messages appear (instead of a password prompt),
                    this time indicating much more serious problems, even
                    suggesting a filesystem corruption (which fortunately
                    did not happen here, as the system was able to start up
                    just fine after a reboot with 6.6.13)

boot3.log - without any changes that I'd be aware of, the system started
            without any error messages whatsoever; however, after entering
            the login name, different errors appeared instead of a password
            prompt

The first version I found failing was 6.7.12-1~bpo12, so I think the issue was caused sometime between those two (6.6.13 and 6.7.12-1~bpo12).

Best regards,

Phil