Kernel panic after buster upgrade

Help with issues regarding installation of Debian

Kernel panic after buster upgrade

Postby harritapio » 2019-10-04 05:30

I have an old HPCompaq dc5800 Microtower (4GB ram, 240GB ssd) which was working correctly with debian stretch (stable) with Mate desktop (latest kernel 4.9.0-11-686-pae).

After upgrading from stretch to buster it won't start anymore, kernel panic message is on screen and everything is freezed. But if I select kernel 4.9 from boot menu, debian buster starts normally and the pc is working properly.
I have also tried to do a clean install of buster with no success - kernel panic.

I have no clue how to fix it, 4.19 kernel is now purged and debian buster is running with previous stable kernel 4.9.

Any advise is welcome!
Harri
harritapio
 
Posts: 24
Joined: 2012-06-05 06:05
Location: Pori, Finland

Re: Kernel panic after buster upgrade

Postby Head_on_a_Stick » 2019-10-05 15:29

Does the 64-bit system work?

Enable persistent logging by creating the /var/log/journal/ directory so you can retrieve the error message. A bug report may be called for here.
Don't break DebianHow to report bugs

SharpBang GNU/Linux — a pre-configured Openbox/Tint2 desktop running on Debian stable
User avatar
Head_on_a_Stick
 
Posts: 10599
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Kernel panic after buster upgrade

Postby harritapio » 2019-10-06 05:55

I tested also the 64-bit version but unfortunately with same result - kernel panic.

These are the last rows on boot screen before freeze (from phone picture)
Code: Select all
Modules linked in:
CR2: 00000000f782b000
---[ end trace 53cf4a01479c5b58 ]---
EIP: acpi_ex_system_memory_space_handler+0x1ab/0x207
Code: 26 83 7d 08 40 75 73 8b 01 8b 51 04 8b 7d 0c 89 07 89 57 04 eb 66 0f b7 01 8b 5d 0c 89 03 c7 43 04 00 00 00 00 eb 55 8b 45 0c <8b> 19 c7 4004 00 00 00 00 89 18 eb 45 83 7d 08 10 74 2c 77 0f 83
EAX: f691fb68 EBX: f6a8ff80 ECX: f782affe EDX: 00000000
ESI: 00000000 EDI: 00000002 EBP: f691fa7c ESP: c5a4fdfc
DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00010246
CR0: 80050033 CR2: f782b000 CR3: 05a48000 CR4: 000006f0
Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009
---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009
---


Thanks for the advise from persistent logging - I tested it but there were nothing in the syslog file in case of system freeze (kernel panic).

Normal operation can be found from the log file - journal log file appears to be operational.
Code: Select all
Oct 06 12:30:40 deb-cr2d systemd[916]: Starting D-Bus User Message Bus Socket.
Oct 06 12:30:40 deb-cr2d systemd[916]: Reached target Timers.
Oct 06 12:30:40 deb-cr2d systemd[916]: Listening on GnuPG cryptographic agent an
Oct 06 12:30:40 deb-cr2d systemd[916]: Listening on GnuPG cryptographic agent an
Oct 06 12:30:40 deb-cr2d systemd[916]: Listening on GnuPG cryptographic agent (s
Oct 06 12:30:40 deb-cr2d systemd[916]: Reached target Paths.
Oct 06 12:30:40 deb-cr2d systemd[916]: Listening on GnuPG cryptographic agent (a
Oct 06 12:30:40 deb-cr2d systemd[916]: Listening on D-Bus User Message Bus Socke
Oct 06 12:30:40 deb-cr2d systemd[916]: Reached target Sockets.
Oct 06 12:30:40 deb-cr2d systemd[916]: Reached target Basic System.
Oct 06 12:30:40 deb-cr2d systemd[916]: Reached target Default.
Oct 06 12:30:40 deb-cr2d systemd[916]: Startup finished in 40ms.
Oct 06 12:30:40 deb-cr2d systemd[916]: Started D-Bus User Message Bus.
Oct 06 12:30:40 deb-cr2d dbus-daemon[937]: Activating via systemd: service name=
Oct 06 12:30:40 deb-cr2d systemd[916]: Starting Accessibility services bus...
Oct 06 12:30:40 deb-cr2d dbus-daemon[937]: Successfully activated service 'org.a
Oct 06 12:30:40 deb-cr2d systemd[916]: Started Accessibility services bus.
Oct 06 12:30:40 deb-cr2d at-spi-bus-launcher[959]: Activating service name='org.
Oct 06 12:30:40 deb-cr2d dbus-daemon[937]: Activating service name='ca.desrt.dco
Oct 06 12:30:40 deb-cr2d at-spi-bus-launcher[959]: Successfully activated servic
Oct 06 12:30:40 deb-cr2d org.a11y.atspi.Registry[964]: SpiRegistry daemon is run
Oct 06 12:30:40 deb-cr2d dbus-daemon[937]: Successfully activated service 'ca.de
Oct 06 12:30:40 deb-cr2d x-session-manager[929]: WARNING: Unable to find provide
Oct 06 12:30:40 deb-cr2d dbus-daemon[937]: Activating via systemd: service name=
Oct 06 12:30:40 deb-cr2d systemd[916]: Starting Virtual filesystem service...
Oct 06 12:30:40 deb-cr2d dbus-daemon[937]: Successfully activated service 'org.g
Oct 06 12:30:40 deb-cr2d systemd[916]: Started Virtual filesystem service.
Oct 06 12:30:41 deb-cr2d dbus-daemon[937]: Activating service name='org.mate.pan
Oct 06 12:30:41 deb-cr2d dbus-daemon[937]: Activating via systemd: service name=
Oct 06 12:30:41 deb-cr2d systemd[916]: Starting Virtual filesystem service - dis
Oct 06 12:30:41 deb-cr2d dbus-daemon[937]: Successfully activated service 'org.m
Oct 06 12:30:41 deb-cr2d gnome-keyring-daemon[927]: The SSH agent was already in
Oct 06 12:30:41 deb-cr2d gnome-keyring-daemon[927]: The Secret Service was alrea
Oct 06 12:30:41 deb-cr2d gnome-keyring-daemon[927]: The PKCS#11 component was al
Oct 06 12:30:41 deb-cr2d dbus-daemon[937]: Successfully activated service 'org.g
Oct 06 12:30:41 deb-cr2d systemd[916]: Started Virtual filesystem service - disk
Oct 06 12:30:41 deb-cr2d dbus-daemon[937]: Activating via systemd: service name=
Oct 06 12:30:41 deb-cr2d systemd[916]: Starting Virtual filesystem service - dig
Oct 06 12:30:41 deb-cr2d dbus-daemon[937]: Successfully activated service 'org.g
Oct 06 12:30:41 deb-cr2d systemd[916]: Started Virtual filesystem service - digi
Oct 06 12:30:41 deb-cr2d dbus-daemon[937]: Activating via systemd: service name=
Oct 06 12:30:41 deb-cr2d systemd[916]: Starting Virtual filesystem service - GNO
Oct 06 12:30:41 deb-cr2d dbus-daemon[937]: Successfully activated service 'org.g
Oct 06 12:30:41 deb-cr2d systemd[916]: Started Virtual filesystem service - GNOM
Oct 06 12:30:41 deb-cr2d dbus-daemon[937]: Activating via systemd: service name=
Oct 06 12:30:41 deb-cr2d systemd[916]: Starting Virtual filesystem service - App
Oct 06 12:30:41 deb-cr2d gvfs-afc-volume-monitor[1090]: Volume monitor alive
Oct 06 12:30:41 deb-cr2d dbus-daemon[937]: Successfully activated service 'org.g
Oct 06 12:30:41 deb-cr2d systemd[916]: Started Virtual filesystem service - Appl
Oct 06 12:30:41 deb-cr2d dbus-daemon[937]: Activating via systemd: service name=
Oct 06 12:30:41 deb-cr2d systemd[916]: Starting Virtual filesystem service - Med
Oct 06 12:30:41 deb-cr2d dbus-daemon[937]: Successfully activated service 'org.g
Oct 06 12:30:41 deb-cr2d systemd[916]: Started Virtual filesystem service - Medi
Oct 06 12:30:42 deb-cr2d dbus-daemon[937]: Activating service name='org.mate.pan
Oct 06 12:30:42 deb-cr2d dbus-daemon[937]: Activating service name='org.mate.pan
Oct 06 12:30:42 deb-cr2d dbus-daemon[937]: Successfully activated service 'org.m
Oct 06 12:30:42 deb-cr2d dbus-daemon[937]: Successfully activated service 'org.m
Oct 06 12:30:42 deb-cr2d notification-ar[1109]: Negative content width -2 (alloc
Oct 06 12:30:42 deb-cr2d notification-ar[1109]: Negative content height -1 (allo
lines 340-362/362 (END)

Harri
harritapio
 
Posts: 24
Joined: 2012-06-05 06:05
Location: Pori, Finland


Return to Installation

Who is online

Users browsing this forum: No registered users and 7 guests

fashionable