kernel panic on shutdown Mint 19.3

[solar1951]

For the last week or so when I have been shutting down the system I get the message regarding "kernel panic - not syncing"
I am using the default kernel 4.15.0.76 - generic and before last week there was no problem.
System boots and runs fine.
What update could have caused this ? Or is it something else ?

[1NEWLINUXUSER]

Hi. The senior members, the one who are best likely to help, are very likely going to want more system info so probably best to go ahead and open a terminal, expand the window a bit so every thing is not so jumbled up and run the command inxi -Fxz, then post the results back here. Sorry, that's all I got.

[solar1951]

Code: Select all

System:    Host: Main Kernel: 4.15.0-76-generic x86_64 bits: 64 compiler: gcc v: 7.4.0 Desktop: Cinnamon 4.4.8 
           Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic 
Machine:   Type: Desktop System: Gigabyte product: N/A v: N/A serial: <filter> 
           Mobo: Gigabyte model: H61M-DS2 v: x.x serial: <filter> BIOS: American Megatrends v: F7 date: 03/23/2012 
CPU:       Topology: Quad Core model: Intel Core i5-2400 bits: 64 type: MCP arch: Sandy Bridge rev: 7 L2 cache: 6144 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 24743 
           Speed: 1596 MHz min/max: 1600/3400 MHz Core speeds (MHz): 1: 1707 2: 1890 3: 1696 4: 1629 
Graphics:  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics vendor: Gigabyte driver: i915 v: kernel 
           bus ID: 00:02.0 
           Display: x11 server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa DRI Intel Sandybridge Desktop v: 3.3 Mesa 19.2.8 direct render: Yes 
Audio:     Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: Gigabyte driver: snd_hda_intel v: kernel 
           bus ID: 00:1b.0 
           Sound Server: ALSA v: k4.15.0-76-generic 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte driver: r8169 v: 2.3LK-NAPI 
           port: e000 bus ID: 02:00.0 
           IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 614.81 GiB used: 367.47 GiB (59.8%) 
           ID-1: /dev/sda vendor: Western Digital model: WD5000AADS-00S9B0 size: 465.76 GiB 
           ID-2: /dev/sdb vendor: Maxtor model: STM3160215AS size: 149.05 GiB 
Partition: ID-1: / size: 13.69 GiB used: 9.26 GiB (67.7%) fs: ext4 dev: /dev/sda1 
           ID-2: /home size: 440.91 GiB used: 268.88 GiB (61.0%) fs: ext4 dev: /dev/sda6 
           ID-3: swap-1 size: 3.72 GiB used: 36.0 MiB (0.9%) fs: swap dev: /dev/sda5 
Sensors:   System Temperatures: cpu: 29.8 C mobo: 27.8 C 
           Fan Speeds (RPM): N/A 
Info:      Processes: 197 Uptime: 4h 21m Memory: 3.75 GiB used: 2.09 GiB (55.8%) Init: systemd runlevel: 5 Compilers: 
           gcc: 7.4.0 Shell: bash v: 4.4.20 inxi: 3.0.32

Results of inxi -Fxz

[codz]

I have the same problem, though it's not occurring on every shutdown.
It would be appreciated if someone can give some feedback on this.

[rosiegamgee]

I experienced the same thing with default kernel 4.15.0.76 - generic. I went back to 4.18.0-25 following the directions from Update Manager > View > Linux Kernels WARNING! screen.

I know I can't stay there, but it has given me reliable shutdowns. Now, I'm watching for a resolution here or elsewhere in the forums.

[Racer-X-]

For the last week or so when I have been shutting down the system I get the message regarding "kernel panic - not syncing"
I am using the default kernel 4.15.0.76 - generic and before last week there was no problem.
System boots and runs fine.
What update could have caused this ? Or is it something else ?

Is there anything in the logs? try posting results from sudo grep -i err /var/log/kern.log|tail -n 30 and put that between "code" and "/code" tags like you did for the inxi output.

Also dmesg|grep -i err|tail -n 30 results would help.

There was an update for 4.15 kernels yesterday. It wouldn't hurt to apply that update. 4.15.0-88 is the current version.

EDIT: Additional information:
I would not install an unsupported kernel, and there are still more potential issues with 5.3.0-* kernel than with the LTS 4.15.0-* kernel.

[missmoondog]

I experienced the same thing with default kernel 4.15.0.76 - generic. I went back to 4.18.0-25 following the directions from Update Manager > View > Linux Kernels WARNING! screen.

I know I can't stay there, but it has given me reliable shutdowns. Now, I'm watching for a resolution here or elsewhere in the forums.

so, to solve your shut down issue, you'd rather use a totally unsupported kernel? would've been better off at least trying one of the 5.3 kernels. at least they are still supported for a bit.

the 4.15 kernel was just updated. try that one out even.

[rosiegamgee]

I experienced the same thing with default kernel 4.15.0.76 - generic. I went back to 4.18.0-25 following the directions from Update Manager > View > Linux Kernels WARNING! screen.

I know I can't stay there, but it has given me reliable shutdowns. Now, I'm watching for a resolution here or elsewhere in the forums.

so, to solve your shut down issue, you'd rather use a totally unsupported kernel? would've been better off at least trying one of the 5.3 kernels. at least they are still supported for a bit.

the 4.15 kernel was just updated. try that one out even.

Thank you. <3

[solar1951]

As the person who started this post I can report that the problem resolved itself with no intervention from me. Just one day it started to shutdown fine and has continued to do so
I wont mark it solved as others seem to be having the same problem.

[rosiegamgee]

I experienced the same thing with default kernel 4.15.0.76 - generic. I went back to 4.18.0-25 following the directions from Update Manager > View > Linux Kernels WARNING! screen.

I know I can't stay there, but it has given me reliable shutdowns. Now, I'm watching for a resolution here or elsewhere in the forums.

so, to solve your shut down issue, you'd rather use a totally unsupported kernel? would've been better off at least trying one of the 5.3 kernels. at least they are still supported for a bit.

the 4.15 kernel was just updated. try that one out even.

Thank you. <3

Came back to report I tried all the above suggestions. The one that gave the longest relief was the most recent update of 4.15. As with the OP my shutdowns became normal until today's which was back to the similar panic on shut down. I'll continue researching and return if there is a lasting solution for me.

[rosiegamgee]

so, to solve your shut down issue, you'd rather use a totally unsupported kernel? would've been better off at least trying one of the 5.3 kernels. at least they are still supported for a bit.

the 4.15 kernel was just updated. try that one out even.

Thank you. <3

Came back to report I tried all the above suggestions. The one that gave the longest relief was the most recent update of 4.15. As with the OP my shutdowns became normal until today's which was back to the similar panic on shut down. I'll continue researching and return if there is a lasting solution for me.

The recently available 5.3.0-40-generic has worked for me with Linux Mint 19.3 "Tricia".

Thanks to everyone who participated in this topic, I learned much.

[codz]

Just to report back. Still happening for me with kernel 4.15.0.88-generic.
It was ok for few days until recent Linux firmware update, when the problem reoccurred.
It's really strange, hopefully this mystery will be resolved soon.

[ZakGordon]

Just to report back. Still happening for me with kernel 4.15.0.88-generic.
It was ok for few days until recent Linux firmware update, when the problem reoccurred.
It's really strange, hopefully this mystery will be resolved soon.

Yeah i had my first hard crash after installing that 1.173.15 Linux Firmware update.

I'm wondering if many of the people that are posting recent issues (CTD etc) had installed that firmware update also? I had to revert mine back to 1.173.12 (.13 and.14 are not offered). Thread here about that:

viewtopic.php?f=46&t=313338

You could try that and see if the issue goes away, you can simply re-install that firmware update if it does nothing.