Hibernate Manjaro -> NetworkManager doesn't start anymore - Gerhard - 01-11-2020
Hi,
today I pushed the button to hibernate the system but it didn' t wake up again. So I pushed the power button to restart the notebook.
Now sytemd can't start NetworkManager.service. There is a core-dump.
Is ist possible to make NetworkManager work again?
Code: [~]> systemctl status NetworkManager.service
● NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service>
Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
└─NetworkManager-ovs.conf
Active: failed (Result: core-dump) since Sat 2020-01-11 18:15:>
Docs: man:NetworkManager(8)
Process: 835 ExecStart=/usr/bin/NetworkManager --no-daemon (cod>
Main PID: 835 (code=dumped, signal=ILL)
Jän 11 18:15:05 b00k systemd[1]: NetworkManager.service: Scheduled >
Jän 11 18:15:05 b00k systemd[1]: Stopped Network Manager.
Jän 11 18:15:05 b00k systemd[1]: NetworkManager.service: Start requ>
Jän 11 18:15:05 b00k systemd[1]: NetworkManager.service: Failed wit>
Jän 11 18:15:05 b00k systemd[1]: Failed to start Network Manager.
#################
[~]> systemd-analyze critical-chain
The time when unit became active or started is printed after the "@>
The time the unit took to start is printed after the "+" character.
graphical.target @3min 32.222s
└─multi-user.target @3min 32.221s
└─smb.service @3min 31.895s +324ms
└─network-online.target @2min 1.625s
└─network.target @2.906s
└─NetworkManager.service @6.023s +352ms
└─dbus.service @2.598s
└─basic.target @2.588s
└─sockets.target @2.588s
└─dbus.socket @2.588s
└─sysinit.target @2.586s
└─systemd-timesyncd.service @2.222s +363ms
└─systemd-tmpfiles-setup.service @2.165s +51ms
└─local-fs.target @2.156s
└─run-user-1000-gvfs.mount @26.539s
└─run-user-1000.mount @22.150s
└─local-fs-pre.target @2.156s
└─lvm2-monitor.service @637ms +1.14>
└─lvm2-lvmetad.service @717ms
└─systemd-journald.socket @606ms
└─system.slice @328ms
└─-.slice @328ms
##################################
[~]> systemd-analyze blame
2min 57ms systemd-networkd-wait-online.service
1min 30.246s nmb.service
30.062s NetworkManager-wait-online.service
3.036s bootsplash-hide-when-booted.service
1.143s lvm2-monitor.service
898ms dev-mmcblk2p1.device
779ms systemd-logind.service
618ms systemd-random-seed.service
441ms systemd-udevd.service
389ms tlp.service
363ms systemd-timesyncd.service
353ms systemd-networkd.service
352ms NetworkManager.service
324ms smb.service
297ms systemd-journald.service
240ms user@1000.service
239ms polkit.service
184ms systemd-udev-trigger.service
138ms systemd-journal-flush.service
51ms systemd-tmpfiles-setup.service
39ms dev-hugepages.mount
39ms systemd-tmpfiles-setup-dev.service
35ms dev-mqueue.mount
34ms systemd-modules-load.service
33ms systemd-remount-fs.service
32ms sys-kernel-debug.mount
30ms systemd-sysctl.service
30ms systemd-rfkill.service
30ms tmp.mount
29ms systemd-backlight@backlight:edp-backlight.service
28ms user-runtime-dir@1000.service
27ms sys-fs-fuse-connections.mount
27ms systemd-update-utmp.service
27ms kmod-static-nodes.service
26ms systemd-user-sessions.service
##################################################
Jän 11 18:15:05 b00k systemd[1]: NetworkManager-wait-online.service: Job NetworkManager-wait-online.service/start failed with result 'dependency'.
Jän 11 18:15:05 b00k systemd[1]: Dependency failed for Network Manager Wait Online.
Jän 11 18:15:05 b00k systemd[1]: Failed to start Network Manager.
Jän 11 18:15:05 b00k systemd[1]: NetworkManager.service: Failed with result 'core-dump'.
Jän 11 18:15:05 b00k systemd[1]: NetworkManager.service: Start request repeated too quickly.
Jän 11 18:15:05 b00k systemd[1]: Stopped Network Manager.
Jän 11 18:15:05 b00k systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 5.
Jän 11 18:15:04 b00k systemd[1]: systemd-coredump@4-838-0.service: Succeeded.
Jän 11 18:15:04 b00k systemd-coredump[839]: Process 835 (NetworkManager) of user 0 dumped core.
Stack trace of thread 835:
#0 0x0000aaaae4aa8120 n/a (NetworkManager + 0x64120)
#1 0x0000ffffa21674bc g_type_class_ref (libgobject-2.0.so.0 + 0x3d4bc)
#2 0x0000ffffa219e000 n/a (libgobject-2.0.so.0 + 0x74000)
Jän 11 18:15:04 b00k systemd[1]: NetworkManager.service: Failed with result 'core-dump'.
Jän 11 18:15:04 b00k systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=4/ILL
Jän 11 18:15:04 b00k systemd[1]: Started Process Core Dump (PID 838/UID 0).
Jän 11 18:15:04 b00k systemd[1]: Started Network Manager.
Jän 11 18:15:04 b00k NetworkManager[835]: <info> [1578762904.4775] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Jän 11 18:15:04 b00k NetworkManager[835]: <info> [1578762904.4726] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf) (etc: dhcp-client.conf)
Jän 11 18:15:04 b00k NetworkManager[835]: <info> [1578762904.4725] NetworkManager (version 1.22.4-1) is starting... (after a restart)
Jän 11 18:15:04 b00k systemd[1]: Started Hide bootsplash after starting the system.
Jän 11 18:15:04 b00k systemd[1]: bootsplash-hide-when-booted.service: Succeeded.
Jän 11 18:15:04 b00k systemd[1]: Starting Network Manager...
Jän 11 18:15:04 b00k systemd[1]: Stopped Network Manager.
Jän 11 18:15:04 b00k systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 4.
Jän 11 18:15:04 b00k systemd[1]: systemd-coredump@3-828-0.service: Succeeded.
Jän 11 18:15:04 b00k systemd-coredump[829]: Process 825 (NetworkManager) of user 0 dumped core.
Stack trace of thread 825:
#0 0x0000aaaab078a120 n/a (NetworkManager + 0x64120)
#1 0x0000ffffbdd794bc g_type_class_ref (libgobject-2.0.so.0 + 0x3d4bc)
#2 0x0000ffffbddb0000 n/a (libgobject-2.0.so.0 + 0x74000)
Jän 11 18:15:04 b00k systemd[1]: NetworkManager.service: Failed with result 'core-dump'.
Jän 11 18:15:04 b00k systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=4/ILL
Jän 11 18:15:03 b00k systemd[1]: Started Process Core Dump (PID 828/UID 0).
Jän 11 18:15:03 b00k NetworkManager[825]: <info> [1578762903.8540] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Jän 11 18:15:03 b00k systemd[1]: Started Network Manager.
Jän 11 18:15:03 b00k NetworkManager[825]: <info> [1578762903.8492] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf) (etc: dhcp-client.conf)
Jän 11 18:15:03 b00k NetworkManager[825]: <info> [1578762903.8490] NetworkManager (version 1.22.4-1) is starting... (after a restart)
Jän 11 18:15:03 b00k systemd[1]: Starting Network Manager...
Jän 11 18:15:03 b00k systemd[1]: Stopped Network Manager.
Jän 11 18:15:03 b00k systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 3.
Jän 11 18:15:03 b00k systemd[1]: systemd-coredump@2-819-0.service: Succeeded.
Jän 11 18:15:03 b00k systemd-coredump[820]: Process 816 (NetworkManager) of user 0 dumped core.
Stack trace of thread 816:
#0 0x0000aaaab3dbf120 n/a (NetworkManager + 0x64120)
#1 0x0000ffffb61844bc g_type_class_ref (libgobject-2.0.so.0 + 0x3d4bc)
#2 0x0000ffffb61bb000 n/a (libgobject-2.0.so.0 + 0x74000)
Jän 11 18:15:03 b00k systemd[1]: NetworkManager.service: Failed with result 'core-dump'.
Jän 11 18:15:03 b00k systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=4/ILL
Jän 11 18:15:03 b00k systemd[1]: Started Process Core Dump (PID 819/UID 0).
Jän 11 18:15:03 b00k NetworkManager[816]: <info> [1578762903.0382] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Jän 11 18:15:03 b00k systemd[1]: Started Network Manager.
Jän 11 18:15:03 b00k NetworkManager[816]: <info> [1578762903.0315] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf) (etc: dhcp-client.conf)
Jän 11 18:15:03 b00k NetworkManager[816]: <info> [1578762903.0313] NetworkManager (version 1.22.4-1) is starting... (after a restart)
Jän 11 18:15:02 b00k systemd[1]: Starting Network Manager...
Jän 11 18:15:02 b00k systemd-logind[778]: Watching system buttons on /dev/input/event3 (HAILUCK CO.,LTD USB KEYBOARD System Control)
Jän 11 18:15:02 b00k systemd[1]: Stopped Network Manager.
Jän 11 18:15:02 b00k systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 2.
Jän 11 18:15:02 b00k systemd-udevd[477]: event1: Failed to call EVIOCSKEYCODE with scan code 0x700a6, and key code 225: Invalid argument
Jän 11 18:15:02 b00k systemd-udevd[477]: event1: Failed to call EVIOCSKEYCODE with scan code 0x700a5, and key code 224: Invalid argument
Jän 11 18:15:02 b00k systemd-udevd[477]: event1: Failed to call EVIOCSKEYCODE with scan code 0x70066, and key code 142: Invalid argument
Jän 11 18:15:02 b00k systemd-udevd[472]: event5: Failed to call EVIOCSKEYCODE with scan code 0x700a6, and key code 225: Invalid argument
Jän 11 18:15:02 b00k systemd-udevd[472]: event5: Failed to call EVIOCSKEYCODE with scan code 0x700a5, and key code 224: Invalid argument
Jän 11 18:15:02 b00k systemd-udevd[472]: event5: Failed to call EVIOCSKEYCODE with scan code 0x70066, and key code 142: Invalid argument
Jän 11 18:15:02 b00k systemd[1]: systemd-coredump@1-799-0.service: Succeeded.
Jän 11 18:15:02 b00k systemd-udevd[467]: event3: Failed to call EVIOCSKEYCODE with scan code 0x700a6, and key code 225: Invalid argument
Jän 11 18:15:02 b00k systemd-udevd[467]: event3: Failed to call EVIOCSKEYCODE with scan code 0x700a5, and key code 224: Invalid argument
Jän 11 18:15:02 b00k systemd-udevd[467]: event3: Failed to call EVIOCSKEYCODE with scan code 0x70066, and key code 142: Invalid argument
Jän 11 18:15:02 b00k systemd-coredump[801]: Process 796 (NetworkManager) of user 0 dumped core.
Stack trace of thread 796:
#0 0x0000aaaadbd66120 n/a (NetworkManager + 0x64120)
#1 0x0000ffffa0e654bc g_type_class_ref (libgobject-2.0.so.0 + 0x3d4bc)
#2 0x0000ffffa0e9c000 n/a (libgobject-2.0.so.0 + 0x74000)
Jän 11 18:15:02 b00k systemd-udevd[473]: event4: Failed to call EVIOCSKEYCODE with scan code 0x700a6, and key code 225: Invalid argument
Jän 11 18:15:02 b00k systemd-udevd[473]: event4: Failed to call EVIOCSKEYCODE with scan code 0x700a5, and key code 224: Invalid argument
Jän 11 18:15:02 b00k systemd-udevd[473]: event4: Failed to call EVIOCSKEYCODE with scan code 0x70066, and key code 142: Invalid argument
Jän 11 18:15:02 b00k systemd[1]: NetworkManager.service: Failed with result 'core-dump'.
Jän 11 18:15:02 b00k systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=4/ILL
Jän 11 18:15:02 b00k systemd-udevd[464]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jän 11 18:15:02 b00k systemd-udevd[464]: Using default interface naming scheme 'v243'.
RE: Hibernate Manjaro -> NetworkManager doesn't start anymore - tophneal - 01-11-2020
Was this install updated in the last few days, or fresh?
If you had it going before and updated it recently (there was a problem with a NetworkManager update recently,) you could try getting into tty2 and using downgrade networkmanager and selecting 1.22.2-1
Resuming from sleep is a known issue with mainline kernel. Best to avoid putting the PBP to sleep on a mainline image for the time being. I'm sure it'll be well known once it's resolved. I imagine many of us will be quite excited about it.
RE: Hibernate Manjaro -> NetworkManager doesn't start anymore - Gerhard - 01-11-2020
(01-11-2020, 12:25 PM)tophneal Wrote: Was this install updated in the last few days, or fresh?
If you had it going before and updated it recently (there was a problem with a NetworkManager update recently,) you could try getting into tty2 and using downgrade networkmanager and selecting 1.22.2-1
Resuming from sleep is a known issue with mainline kernel. Best to avoid putting the PBP to sleep on a mainline image for the time being. I'm sure it'll be well known once it's resolved. I imagine many of us will be quite excited about it.
I updated the system yesterday, about 24 hours ago. Now I have tried to bring up wlan0 again but nothing helps so far.
I thought maybe I can bring sleepmode to work somehow. ;D
RE: Hibernate Manjaro -> NetworkManager doesn't start anymore - tophneal - 01-11-2020
Run 'downgrade networkmanager' and go back to the previous version. you should get wlan0 back.
If you figure out getting the PBP to wake from sleep, don't forget to share it with us!
RE: Hibernate Manjaro -> NetworkManager doesn't start anymore - Gerhard - 01-11-2020
(01-11-2020, 12:38 PM)tophneal Wrote: Run 'downgrade networkmanager' and go back to the previous version. you should get wlan0 back.
If you figure out getting the PBP to wake from sleep, don't forget to share it with us!
thank you! I would share it. Do you know a way to downgrade a package without having "downgrade" installed?
Hibernate Manjaro -> NetworkManager doesn't start anymore - tophneal - 01-11-2020
Did you remove downgrade? When this happened to me, it was already installed.
I can't recall exactly how but I remember finding the method used for downgrading with pamac, but if I find it I'll post it.
RE: Hibernate Manjaro -> NetworkManager doesn't start anymore - Gerhard - 01-11-2020
(01-11-2020, 12:55 PM)tophneal Wrote: Did you remove downgrade? When this happened to me, it was already installed.
I can't recall exactly how but I remember finding the method used for downgrading with pamac, but if I find it I'll post it.
Maybe I did it accidently if it was there because I deinstalled the xfce and its dependencies and a lot of other packages during switching to i3w. Thank you, I will search in the pamac-manpage.
The package "downgrade" wasn't installed per default, I didn't remove it. I searched the history. I can' t find a option in pamac to downgrade. I think maybe it is possible to write the package on an Usb-stick and install it with a command from there?
RE: Hibernate Manjaro -> NetworkManager doesn't start anymore - Gerhard - 01-11-2020
@tophneal
Thank you for helping!
I managed to get it downgraded.
I found the old Version in /var/cache/pacman/pkg/
then
Code: pamac install networkmanager-1.22.2-1-aarch64.pkg.tar.xz
simple did it.
RE: Hibernate Manjaro -> NetworkManager doesn't start anymore - tophneal - 01-11-2020
Great! Now that your back on your wifi, don't forget to reinstall downgrade. Makes this kinda thing a lot easier!
|