Hi Alejandro, On Sun, Nov 17, 2024 at 09:12:36PM +0100, Alejandro Colomar wrote: > Hi Salvatore, > > On Sun, Nov 17, 2024 at 08:25:18PM GMT, Salvatore Bonaccorso wrote: > > Control: severity -1 serious > > Control: tags -1 + moreinfo > > > > I guess we have too litttle information here to get an idea about the > > issue. > > Here's the last three lines I see before it freezes: > > Please unlock disk nvme0n1p4_crypt: **...* > cryptsetup: nvme0n1p4_crypt: set up successfully > deb_root: clean, 5xxxxxx/3xxxxxxx files, 96xxxxxx/134xxxxxx blocks > > > After that it freezes. When I boot tomorrow, I'll try to note down the > lines before that, since I've noticed there are some lines that only > appear with the new kernel. > > > Is the system still repsonsive and accessible through SSH? > > It's the computer I'm using to send this email. I can boot it with an > old kernel. > > > Might you get more information out of it with configuring netconsole > > to get kernel logs out? > > I could, if you tell me how. I'm not an expert in these things.
Sorry for the late reply. There is documentation here: https://www.kernel.org/doc/html/latest/networking/netconsole.html#netconsole Since we need the messages as eaerly as possible, make sure that the source ip and target device is configured with the parameters. I assume you still have the behaviour with 6.11.9-1 uploaded earlier the week? Note there is as well 6.11.10-1 right now to be processed and available soon as well. >From a working version yet, can you access the apt log around the time you have updates, anything suspicious in apt logs? Regards, Salvatore
