Source: linux Followup-For: Bug #989010 X-Debbugs-Cc: pitsiorisj@gmail.com It happened again today, and twice, although I am still on 5.10.28, so here are my thoughts. First of all, I noticed that linux-kbuild and linux-compiler-gcc were updated for 5.10.40 that reached unstable yesterday, so they were upgraded on my system too... because I forgot to downgrade them to their 5.10.28 versions from testing or because I tried but apt does not let me as seen below. # apt-get install -t testing linux-compiler-gcc-10-x86 linux-kbuild-5.10 Reading package lists... Done Building dependency tree... Done Reading state information... Done linux-compiler-gcc-10-x86 is already the newest version (5.10.40-1). linux-compiler-gcc-10-x86 set to manually installed. linux-kbuild-5.10 is already the newest version (5.10.40-1). linux-kbuild-5.10 set to manually installed. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Here is what happened since I first booted up my pc earlier today. First boot of the day (4+ hours ago), mandatory apt upgrade that got the forementioned packages installed in their new versions, 2-3 hours of work with no reboot so as to test anything and then a complete shutdown. New, cold boot, ~30 minutes ago. No post, no grub, no boot messages, no desktop, just the led on my monitor switching from orange (standby) to blue (on). Instead of reisub, I logged in via ssh from my phone and issued a reboot. It rebooted, but still nothing on screen, so I ssh'd again from the phone and, instead of rebooting straight away, I ran apt-get update etc. And this weird kernel message showed up (attached image)! It is the first time I have ever seen such a message. Ssh output did not continue past that point, so I went with reisub this time. And when it booted, everything (post, grub, boot messages and desktop) showed up as usual. And again, I lost ~100MB more from my drive's space after that. Two more observations I have made these past days are a) The nic's leds turn off completely after shutdown, which is weird because I have wake on lan enabled and the green one (= the "power" led) is supposed to be on so as to indicate it is on standby. It does stay on if I shut down the system from windows (I dual boot). b) At boot, the nic's other led, the orange (= the "activity" one) blinks for 3 times, then pauses for some seconds, then blinks for 3 times again, then pauses again. This happens from the moment the post is on until the boot messages show up, because then the green one comes up and the nic is fully operational. I use the stock r8169 module for my nic since ever, although someone once told me that r8198 might be better.
Attachment:
Screenshot_20210529-103027.png
Description: PNG image
