Kernel Panic when I reboot or Shutdown my computer

[Goro Daimon]

Hi folks. When I shutdown or reboot my machine Linux Mint 20.1 kernel shows kernel panic message. How I solve this? Look:
https://youtu.be/eZwSZnSWsh8


Error short time turned on:
https://www.youtube.com/watch?v=Ls9QcT3Gsco

[Kadaitcha Man]

How I solve this? Look:

Those are two separate problems. The second image complaining about about /oldroot is almost 99.9999999999999% certain to be an nViodia driver bug. If you have the nVidia driver installed then the only way to get rid of the message is to uninstall the nVidia driver and use the open source nouveau driver, otherwise you can ignore it on the grounds that although it looks serious, it doesn't do any harm.

For the problem described by the first picture, please post the output of inxi -Fxz from a terminal. You can copy the terminal text and paste it back here. Wrap the output in [code]output here[/code] tags so that it is readable.

[Goro Daimon]

How I solve this? Look:

Those are two separate problems. The second image complaining about about /oldroot is almost 99.9999999999999% certain to be an nViodia driver bug. If you have the nVidia driver installed then the only way to get rid of the message is to uninstall the nVidia driver and use the open source nouveau driver, otherwise you can ignore it on the grounds that although it looks serious, it doesn't do any harm.

For the problem described by the first picture, please post the output of inxi -Fxz from a terminal. You can copy the terminal text and paste it back here. Wrap the output in [code]output here[/code] tags so that it is readable.

Code: Select all

$ inxi -Fxz
System:
  Kernel: 5.4.0-65-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
  Desktop: Xfce 4.14.2 Distro: Linux Mint 20.1 Ulyssa 
  base: Ubuntu 20.04 focal 
Machine:
  Type: Desktop Mobo: ASRock model: FM2A68M-DG3+ serial: <filter> 
  UEFI: American Megatrends v: P2.60 date: 01/12/2016 
CPU:
  Topology: Dual Core model: AMD A4-4000 APU with Radeon HD Graphics 
  bits: 64 type: MCP arch: Piledriver rev: 1 L2 cache: 1024 KiB 
  flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 11977 
  Speed: 1397 MHz min/max: 1400/3000 MHz Core speeds (MHz): 1: 1396 2: 1396 
Graphics:
  Device-1: AMD Trinity 2 [Radeon HD 7480D] vendor: ASRock driver: radeon 
  v: kernel bus ID: 00:01.0 
  Display: x11 server: X.Org 1.20.9 driver: ati,radeon 
  unloaded: fbdev,modesetting,vesa resolution: 1600x900_60.00~60Hz 
  OpenGL: renderer: AMD ARUBA (DRM 2.50.0 / 5.4.0-65-generic LLVM 11.0.0) 
  v: 4.3 Mesa 20.2.6 direct render: Yes 
Audio:
  Device-1: AMD Trinity HDMI Audio vendor: ASRock driver: snd_hda_intel 
  v: kernel bus ID: 00:01.1 
  Device-2: AMD FCH Azalia vendor: ASRock driver: snd_hda_intel v: kernel 
  bus ID: 00:14.2 
  Sound Server: ALSA v: k5.4.0-65-generic 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: ASRock driver: r8169 v: kernel port: e000 bus ID: 01:00.0 
  IF: enp1s0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 931.51 GiB used: 227.93 GiB (24.5%) 
  ID-1: /dev/sda vendor: Seagate model: ST1000VM002-1ET162 size: 931.51 GiB 
  temp: 39 C 
Partition:
  ID-1: / size: 143.19 GiB used: 52.90 GiB (36.9%) fs: ext4 dev: /dev/sda1 
  ID-2: /home size: 763.52 GiB used: 174.91 GiB (22.9%) fs: ext4 
  dev: /dev/sda4 
  ID-3: swap-1 size: 7.81 GiB used: 111.5 MiB (1.4%) fs: swap dev: /dev/sda2 
Sensors:
  System Temperatures: cpu: 18.1 C mobo: N/A gpu: radeon temp: 18 C 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 236 Uptime: 27m Memory: 4.78 GiB used: 3.05 GiB (63.9%) 
  Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17 
  inxi: 3.0.38 

Code: Select all

goro@daimon-amd:~$ neofetch
             ...-:::::-...                 goro@daimon-amd 
          .-MMMMMMMMMMMMMMM-.              ----------------- 
      .-MMMM`..-:::::::-..`MMMM-.          OS: Linux Mint 20.1 x86_64 
    .:MMMM.:MMMMMMMMMMMMMMM:.MMMM:.        Kernel: 5.4.0-66-generic 
   -MMM-M---MMMMMMMMMMMMMMMMMMM.MMM-       Uptime: 1 min 
 `:MMM:MM`  :MMMM:....::-...-MMMM:MMM:`    Packages: 3250 (dpkg), 21 (flatpak) 
 :MMM:MMM`  :MM:`  ``    ``  `:MMM:MMM:    Shell: bash 5.0.17 
.MMM.MMMM`  :MM.  -MM.  .MM-  `MMMM.MMM.   Resolution: 1600x900 
:MMM:MMMM`  :MM.  -MM-  .MM:  `MMMM-MMM:   DE: Xfce 
:MMM:MMMM`  :MM.  -MM-  .MM:  `MMMM:MMM:   WM: Xfwm4 
:MMM:MMMM`  :MM.  -MM-  .MM:  `MMMM-MMM:   WM Theme: Mint-Y 
.MMM.MMMM`  :MM:--:MM:--:MM:  `MMMM.MMM.   Theme: Mint-Y [GTK2], Arc [GTK3] 
 :MMM:MMM-  `-MMMMMMMMMMMM-`  -MMM-MMM:    Icons: Mint-Y [GTK2], deepin [GTK3] 
  :MMM:MMM:`                `:MMM:MMM:     Terminal: xfce4-terminal 
   .MMM.MMMM:--------------:MMMM.MMM.      Terminal Font: Monospace 10 
     '-MMMM.-MMMMMMMMMMMMMMM-.MMMM-'       CPU: AMD A4-4000 APU (2) @ 3.000GHz 
       '.-MMMM``--:::::--``MMMM-.'         GPU: AMD ATI Radeon HD 7480D 
            '-MMMMMMMMMMMMM-'              Memory: 850MiB / 4891MiB 
               ``-:::::-``
                                                                   
                                                                   

[sleeper12]

I just got a kernel update to 5.4.0-66, if that's of any help.

[Kadaitcha Man]

How I solve this? Look:

Those are two separate problems. The second image complaining about about /oldroot is almost 99.9999999999999% certain to be an nViodia driver bug.

Code: Select all

Graphics:
  Device-1: AMD Trinity 2 [Radeon HD 7480D] vendor: ASRock driver: radeon                           

Well, there goes that theory.

Have you been playing with encryption or security hardening your system?

[RickyRaccoon]

Have you been playing with encryption or security hardening your system?

It'll catch up with you. I updated the kernel in my laptop other day, and got Kernel Panic- the whole disc is encrypted, and I'd run out of space for kernels so it botched the update then wouldn't boot- I just had to boot up in recovery mode and choose a kernel that wasn't corrupted- then I went into the Update manager and deleted a bunch of old ones, reran my update. Done, and done! And it only took me... 30 or 40 minutes to figure it all out... It helps that I've run into 'out of space for kernels' before- so I had a feelin' it might be that- but it never botched the boot before, it just errored out on the upgrade. This time, it bloody well messed it up. I'll keep tabs on how many old kernels I have installed, from here on out.

[Kadaitcha Man]

Have you been playing with encryption or security hardening your system?

It'll catch up with you. I updated the kernel in my laptop other day, and got Kernel Panic- the whole disc is encrypted, and I'd run out of space for kernels so it botched the update then wouldn't boot- I just had to boot up in recovery mode and choose a kernel that wasn't corrupted- then I went into the Update manager and deleted a bunch of old ones, reran my update. Done, and done!

The question is for the OP though your suggestion is what the OP might have to try.

[RickyRaccoon]

The question is for the OP though your suggestion is what the OP might have to try.

Well when you asked if they'd been messing with security- that's why I mentioned it. It was.. a lot easier fix than I thought it'd be. I literally did that to my lappy over the weekend, with the kernel panic- first time I'd ever ran into that.

[Goro Daimon]

Those are two separate problems. The second image complaining about about /oldroot is almost 99.9999999999999% certain to be an nViodia driver bug.

Code: Select all

Graphics:
  Device-1: AMD Trinity 2 [Radeon HD 7480D] vendor: ASRock driver: radeon                           

Well, there goes that theory.

Have you been playing with encryption or security hardening your system?

As far as I remember, no. I don't remember doing that. Using Google I thought the problem would be in the SystemD.

[Kadaitcha Man]

As far as I remember, no. I don't remember doing that. Using Google I thought the problem would be in the SystemD.

You might have to trawl through the logs in /var/log to nut it out. All I can suggest for now is that you try selecting an older kernel from the grub boot menu. If that works then we can can work out how to get around the problem.

[Goro Daimon]

As far as I remember, no. I don't remember doing that. Using Google I thought the problem would be in the SystemD.

You might have to trawl through the logs in /var/log to nut it out. All I can suggest for now is that you try selecting an older kernel from the grub boot menu. If that works then we can can work out how to get around the problem.

I cleaned /var/log sometimes. I changed to a bit older kernel and the problem persists. My hard drive I bought in October or November 2020.

I shut down my computer today and aparentelly no kernel panic.

I installed the latest update for my kernel.