Hi guys,
I have a bit of an unusual problem. My kernel updated recently, from 6.2.0-31 to 6.2.0-32 (I think), and the system will not fully boot up from the grub menu with the most recent kernel.
If I go to advanced options from the grub menu, then select the previous kernel, (6.2.0-31), it seems to work fine.
I cannot copy and paste, or take a screen shot, during the bootup process, but I do remember seeing something about kernel null pointer.
There was also something about processes involving userspace out-of-memory process killer, timy syncronization, and network name resolution not being completed.
After booting with the older kernel, I did perform the following commands:
Code:
systemctl status systemd-timesyncd.service
systemctl status systemd-oomd.service
systemctl status systemd-resolved.service
which gave the following output:
Code:
● systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2023-09-08 23:43:31 EDT; 5min ago
Docs: man:systemd-timesyncd.service(8)
Main PID: 505 (systemd-timesyn)
Status: "Initial synchronization to time server [2620:2d:4000:1::41]:123 (ntp.ubuntu.com)."
Tasks: 2 (limit: 18809)
Memory: 1.4M
CPU: 89ms
CGroup: /system.slice/systemd-timesyncd.service
└─505 /lib/systemd/systemd-timesyncd
Sep 08 23:43:31 dynabook-TECRA-A50-F systemd[1]: Starting Network Time Synchronization...
Sep 08 23:43:31 dynabook-TECRA-A50-F systemd[1]: Started Network Time Synchronization.
Sep 08 23:44:02 dynabook-TECRA-A50-F systemd-timesyncd[505]: Initial synchronization to time server [2620:2d:4000:1::41]:123 (ntp.ubuntu.com).
● systemd-oomd.service - Userspace Out-Of-Memory (OOM) Killer
Loaded: loaded (/lib/systemd/system/systemd-oomd.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2023-09-08 23:43:31 EDT; 5min ago
Docs: man:systemd-oomd.service(8)
Main PID: 499 (systemd-oomd)
Status: "Processing requests..."
Tasks: 1 (limit: 18809)
Memory: 1.4M (min: 64.0M low: 64.0M)
CPU: 532ms
CGroup: /system.slice/systemd-oomd.service
└─499 /lib/systemd/systemd-oomd
Sep 08 23:43:31 dynabook-TECRA-A50-F systemd[1]: Starting Userspace Out-Of-Memory (OOM) Killer...
Sep 08 23:43:31 dynabook-TECRA-A50-F systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
● systemd-resolved.service - Network Name Resolution
Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2023-09-08 23:43:32 EDT; 6min ago
Docs: man:systemd-resolved.service(8)
man:org.freedesktop.resolve1(5)
https://www.freedesktop.org/wiki/Sof...ation-managers
https://www.freedesktop.org/wiki/Sof...solver-clients
Main PID: 501 (systemd-resolve)
Status: "Processing requests..."
Tasks: 1 (limit: 18809)
Memory: 9.5M
CPU: 177ms
CGroup: /system.slice/systemd-resolved.service
└─501 /lib/systemd/systemd-resolved
Sep 08 23:43:31 dynabook-TECRA-A50-F systemd[1]: Starting Network Name Resolution...
Sep 08 23:43:31 dynabook-TECRA-A50-F systemd-resolved[501]: Positive Trust Anchors:
Sep 08 23:43:31 dynabook-TECRA-A50-F systemd-resolved[501]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Sep 08 23:43:31 dynabook-TECRA-A50-F systemd-resolved[501]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa corp home internal intranet lan local private test
Sep 08 23:43:31 dynabook-TECRA-A50-F systemd-resolved[501]: Using system hostname 'dynabook-TECRA-A50-F'.
Sep 08 23:43:32 dynabook-TECRA-A50-F systemd[1]: Started Network Name Resolution.
Sep 08 23:43:37 dynabook-TECRA-A50-F systemd-resolved[501]: wlp1s0: Bus client set search domain list to: hsd1.mi.comcast.net
Sep 08 23:43:37 dynabook-TECRA-A50-F systemd-resolved[501]: wlp1s0: Bus client set default route setting: yes
Sep 08 23:43:37 dynabook-TECRA-A50-F systemd-resolved[501]: wlp1s0: Bus client set DNS server list to: 75.75.75.75, 75.75.76.76
Sep 08 23:43:39 dynabook-TECRA-A50-F systemd-resolved[501]: wlp1s0: Bus client set DNS server list to: 75.75.75.75, 75.75.76.76, 2001:558:feed::1, 2001:558:feed
Also, here is the output of the command
Code:
vdir /boot
Code:
total 261436
-rw-r--r-- 1 root root 262053 Aug 14 05:05 config-5.15.0-83-generic
-rw-r--r-- 1 root root 275587 Aug 16 05:42 config-6.2.0-31-generic
-rw-r--r-- 1 root root 275587 Aug 18 05:38 config-6.2.0-32-generic
drwx------ 4 root root 4096 Dec 31 1969 efi
drwxr-xr-x 5 root root 4096 Sep 5 21:16 grub
lrwxrwxrwx 1 root root 28 Sep 5 21:15 initrd.img -> initrd.img-5.15.0-83-generic
-rw-r--r-- 1 root root 65684040 Sep 5 21:15 initrd.img-5.15.0-83-generic
-rw-r--r-- 1 root root 69602500 Sep 4 10:56 initrd.img-6.2.0-31-generic
-rw-r--r-- 1 root root 69599829 Sep 5 21:15 initrd.img-6.2.0-32-generic
lrwxrwxrwx 1 root root 27 Sep 5 21:16 initrd.img.old -> initrd.img-6.2.0-32-generic
-rw-r--r-- 1 root root 182800 Feb 6 2022 memtest86+.bin
-rw-r--r-- 1 root root 184476 Feb 6 2022 memtest86+.elf
-rw-r--r-- 1 root root 184980 Feb 6 2022 memtest86+_multiboot.bin
-rw------- 1 root root 6273612 Aug 14 05:05 System.map-5.15.0-83-generic
-rw------- 1 root root 7967590 Aug 16 05:42 System.map-6.2.0-31-generic
-rw------- 1 root root 7969006 Aug 18 05:38 System.map-6.2.0-32-generic
lrwxrwxrwx 1 root root 25 Sep 5 21:15 vmlinuz -> vmlinuz-5.15.0-83-generic
-rw------- 1 root root 11615656 Aug 14 05:07 vmlinuz-5.15.0-83-generic
-rw------- 1 root root 13796616 Aug 16 08:43 vmlinuz-6.2.0-31-generic
-rw------- 1 root root 13791304 Aug 18 05:40 vmlinuz-6.2.0-32-generic
lrwxrwxrwx 1 root root 24 Sep 5 21:15 vmlinuz.old -> vmlinuz-6.2.0-32-generic
I noticed that the sofltlink with the .old suffix is pointing to the most recent kernel.
Not sure if that information helps or not.
My hardware is a Tecra dynabook intel core i7.
Thanks for any insights,
Chopra