Hello Alessandro.

Several quick observations

1. You can attach a file to your email instead of pasting text. That helps with
    readability.
2. When there is a failure in the kernel, there is a neat "[ cut here ]" mark.
    That means that the content under that mark is what is relevant to the
    problem.
3. tomoyo is a LSM (linux security module), from Japan. It's in the same style
    as AppArmor and SELinux.

With that out of the way, about the hang. To me, it seems pretty clear...
There's an issue with the graphics driver:

> [ 2075.240903] ------------[ cut here ]------------
> [ 2075.240912] Can't enable IRQ/MSI because no handler is installed
> [ 2075.240972] WARNING: CPU: 5 PID: 3136 at drivers/gpu/drm/radeon/r100.c:727 r100_irq_set+0x93/0xb0 [radeon]

Can't make head or tail of whatever else from the partial logs you pasted.

It hangs, yet you can use your keyboard? Can't you access your ttys? If you have
access to your ttys, then you can do live troubleshooting. You can look at what
is running and what should be running. You can try to start/restart the X
server. All that stuff.

Seems like the kernel loads properly, but the rest of the boot process isn't. A
point to look into.

Cheers,
                 Ludovic

On Sun, 10 Nov 2024, Alessandro Vesely via Dng wrote:

>Hi all,
>
>today the new Linux version (6.1.0-27-amd64) froze twice. The following are three snippets from kern.log. Two failed, the third one succeeded. The line with "tomoyo" seems to mark the beginning of the shutdown , issued via ctrl-alt-del.
>
>The "random key value" thing is coming from the wifi access point, and doesn't happen on the second boot.
>
>hpasmxld is an obsolete module by HP. It allows me to access some data (using hpasmcli).
>
>How can I find what is going wrong? I have a crashkernel= directive on the grub command line. Actually two of them, an ancient one on /etc/default/grub (now removed) and another one added by /etc/default/grub.d/kdump-tools.cfg. However, I'm not clear what data could be retrieved from it.
>
>Other logs have data related to the time interval before the freeze, but they are successful loading or shutting down notices.
>
>The only not-so-good stuff I see are the iptables blocked packets. I don't think incoming packets can hang the boot, albeit at early stages. Yet, the boot hangs there...?
>
>I also found an exception, which didn't interrupt the boot process, which I paste after the three snippet. Where should I send it?
>
>Best
>Ale
>