On Tue, 12 Nov 2024, Alessandro Vesely via Dng wrote:

>>Just to be sure, you do have a monitor plugged in right? In case of kernel
>>panic, you'd want to see what it is panicking about.
>
>
>Yes, the monitor is plugged in..
>

Good, we can exclude panics then. :)

>
>>>Perhaps I should have started in single-user mode and then
>>>manually run the scripts in /etc/rc2.d, in lexicographical order,
>>>with some checks between one and the next.  Would that work?
>>
>>I don't know. Have you tried?
>
>
>No, I never tried. It should work, methinks. Once I tried to enable
>the network after booting in single user mode and it didn't work, but
>that was Ubuntu with Systemd.
>

So there's a clue. You noted in another email that the issue occurs after a
custom script to enable the network would launch. If your Ethernet cable is
broken, or not plugged in, or if the endpoint your system is trying to talk to
doesn't answer, you'll get a hang. Your system will wait for an answer until a
predefined amount of time has elapsed, then give up and continue normally.

You could initialize the network asynchronously, but wouldn't work for services
that depends on it.

The best course of actions, when those hangs do occurs, is to verify your
internet connection, or LAN. Make sure that your machine can actually talks to
the network.

>
>>You said it's a new problem. Did you take a look at the kernel mailing list for
>>possible regression? A quick search turned a regression linked to servers
>>equipped with AMD ES1000:
>>
>>       https://gitlab.freedesktop.org/drm/amd/-/issues/2826
>
>
>Thanks, I googled a bit but didn't find that page.
>

This isn't from google, or any search engine. Search engines have been subpar
for the past few years, and you'd probably not find it there. I went to the
linux kernel mailing list (https://lore.kernel.org/lkml/) and did some quick
searchs with a few different keywords.

Cheers,
                 Ludovic