[SOLVED] Computer hangs during reboot

[ohad]

When I try to issue a reboot command

Code: Select all

ohad@fit-pc:~$ sudo reboot

the system starts shutting down everything but doesn't actually reboot no matter how long I wait, so I have to physically cut and reconnect the power (the computer has an external power supply and no power button).

The journal from the reboot attempt:

Code: Select all

ohad@fit-pc:~$ sudo journalctl -b -1 -n100   
-- Logs begin at Mon 2020-04-13 22:14:25 IDT, end at Thu 2020-04-16 21:47:38 IDT. --
Apr 16 21:35:17 fit-pc systemd[1]: Started Show Plymouth Reboot Screen.
Apr 16 21:35:17 fit-pc systemd[1]: Removed slice User Slice of UID 1000.
Apr 16 21:35:17 fit-pc systemd[1]: Stopping Permit User Sessions...
Apr 16 21:35:17 fit-pc systemd[1]: systemd-user-sessions.service: Succeeded.
Apr 16 21:35:17 fit-pc systemd[1]: Stopped Permit User Sessions.
Apr 16 21:35:17 fit-pc systemd[1]: xrdp.service: Succeeded.
Apr 16 21:35:17 fit-pc systemd[1]: Stopped xrdp daemon.
Apr 16 21:35:17 fit-pc systemd[1]: Stopping xrdp session manager...
Apr 16 21:35:17 fit-pc systemd[1]: xrdp-sesman.service: Control process exited, code=exited, status=1/FAILURE
Apr 16 21:35:17 fit-pc systemd[1]: exim4.service: Succeeded.
Apr 16 21:35:17 fit-pc systemd[1]: Stopped LSB: exim Mail Transport Agent.
Apr 16 21:35:27 fit-pc systemd-shutdown[1]: Syncing filesystems and block devices.
Apr 16 21:35:17 fit-pc systemd[1]: Stopped target System Time Synchronized.
Apr 16 21:35:17 fit-pc systemd[1]: Stopped target Network is Online.
Apr 16 21:35:18 fit-pc systemd[1]: xrdp-sesman.service: Failed with result 'exit-code'.
Apr 16 21:35:18 fit-pc systemd[1]: Stopped xrdp session manager.
Apr 16 21:35:19 fit-pc systemd[1]: alsa-restore.service: Succeeded.
Apr 16 21:35:19 fit-pc systemd[1]: Stopped Save/Restore Sound Card State.
Apr 16 21:35:19 fit-pc systemd[1]: Stopping Manage Sound Card State (restore and store)...
Apr 16 21:35:19 fit-pc systemd[1]: apache2.service: Succeeded.
Apr 16 21:35:19 fit-pc systemd[1]: Stopped The Apache HTTP Server.
Apr 16 21:35:19 fit-pc systemd[1]: Stopped target Remote File Systems.
Apr 16 21:35:19 fit-pc systemd[1]: Stopped target Network.
Apr 16 21:35:19 fit-pc systemd[1]: Stopping WPA supplicant...
Apr 16 21:35:19 fit-pc systemd[1]: Stopping Raise network interfaces...
Apr 16 21:35:19 fit-pc systemd[1]: Stopping ifup for wlx48022a322063...
Apr 16 21:35:20 fit-pc systemd[1]: wpa_supplicant.service: Succeeded.
Apr 16 21:35:20 fit-pc systemd[1]: Stopped WPA supplicant.
Apr 16 21:35:20 fit-pc systemd[1]: Stopping D-Bus System Message Bus...
Apr 16 21:35:20 fit-pc systemd[1]: dbus.service: Succeeded.
Apr 16 21:35:20 fit-pc systemd[1]: Stopped D-Bus System Message Bus.
Apr 16 21:35:20 fit-pc systemd[1]: alsa-state.service: Succeeded.
Apr 16 21:35:20 fit-pc systemd[1]: Stopped Manage Sound Card State (restore and store).
Apr 16 21:35:20 fit-pc systemd[1]: Stopped target Basic System.
Apr 16 21:35:20 fit-pc systemd[1]: systemd-ask-password-plymouth.path: Succeeded.
Apr 16 21:35:20 fit-pc systemd[1]: Stopped Forward Password Requests to Plymouth Directory Watch.
Apr 16 21:35:20 fit-pc systemd[1]: Stopped target Slices.
Apr 16 21:35:20 fit-pc systemd[1]: Removed slice User and Session Slice.
Apr 16 21:35:20 fit-pc systemd[1]: Stopped target Paths.
Apr 16 21:35:20 fit-pc systemd[1]: Stopped target Sockets.
Apr 16 21:35:20 fit-pc systemd[1]: dbus.socket: Succeeded.
Apr 16 21:35:20 fit-pc systemd[1]: Closed D-Bus System Message Bus Socket.
Apr 16 21:35:20 fit-pc systemd[1]: avahi-daemon.socket: Succeeded.
Apr 16 21:35:20 fit-pc systemd[1]: Closed Avahi mDNS/DNS-SD Stack Activation Socket.
Apr 16 21:35:20 fit-pc systemd[1]: syslog.socket: Succeeded.
Apr 16 21:35:20 fit-pc systemd[1]: Closed Syslog Socket.
Apr 16 21:35:20 fit-pc systemd[1]: Stopped target System Initialization.
Apr 16 21:35:20 fit-pc systemd[1]: Stopping Load/Save Random Seed...
Apr 16 21:35:20 fit-pc systemd[1]: Stopping Network Time Synchronization...
Apr 16 21:35:20 fit-pc systemd[1]: Stopped target Swap.
Apr 16 21:35:20 fit-pc systemd[1]: Deactivating swap /dev/disk/by-partuuid/ff77ec60-02...
Apr 16 21:35:20 fit-pc systemd[1]: Stopping Update UTMP about System Boot/Shutdown...
Apr 16 21:35:20 fit-pc systemd[1]: Stopped target Local Encrypted Volumes.
Apr 16 21:35:20 fit-pc systemd[1]: systemd-ask-password-wall.path: Succeeded.
Apr 16 21:35:20 fit-pc systemd[1]: Stopped Forward Password Requests to Wall Directory Watch.
Apr 16 21:35:21 fit-pc systemd[1]: systemd-timesyncd.service: Succeeded.
Apr 16 21:35:21 fit-pc systemd[1]: Stopped Network Time Synchronization.
Apr 16 21:35:21 fit-pc systemd[1]: systemd-random-seed.service: Succeeded.
Apr 16 21:35:21 fit-pc systemd[1]: Stopped Load/Save Random Seed.
Apr 16 21:35:21 fit-pc systemd[1]: systemd-update-utmp.service: Succeeded.
Apr 16 21:35:21 fit-pc systemd[1]: Stopped Update UTMP about System Boot/Shutdown.
Apr 16 21:35:21 fit-pc systemd[1]: systemd-tmpfiles-setup.service: Succeeded.
Apr 16 21:35:21 fit-pc systemd[1]: Stopped Create Volatile Files and Directories.
Apr 16 21:35:23 fit-pc systemd[1]: dev-disk-by\x2dpath-pci\x2d0000:00:0f.2\x2data\x2d1\x2dpart2.swap: Succeeded.
Apr 16 21:35:23 fit-pc systemd[1]: Deactivated swap /dev/disk/by-path/pci-0000:00:0f.2-ata-1-part2.
Apr 16 21:35:23 fit-pc systemd[1]: dev-disk-by\x2dpartuuid-ff77ec60\x2d02.swap: Succeeded.
Apr 16 21:35:23 fit-pc systemd[1]: Deactivated swap /dev/disk/by-partuuid/ff77ec60-02.
Apr 16 21:35:23 fit-pc systemd[1]: dev-disk-by\x2did-ata\x2dHitachi_HTS541660J9AT00_SB0B4DSLCHPV8H\x2dpart2.swap: Succeeded.
Apr 16 21:35:23 fit-pc systemd[1]: Deactivated swap /dev/disk/by-id/ata-Hitachi_HTS541660J9AT00_SB0B4DSLCHPV8H-part2.
Apr 16 21:35:23 fit-pc systemd[1]: dev-disk-by\x2did-wwn\x2d0x5000cca521c72394\x2dpart2.swap: Succeeded.
Apr 16 21:35:23 fit-pc systemd[1]: Deactivated swap /dev/disk/by-id/wwn-0x5000cca521c72394-part2.
Apr 16 21:35:23 fit-pc systemd[1]: dev-sda2.swap: Succeeded.
Apr 16 21:35:23 fit-pc systemd[1]: Deactivated swap /dev/sda2.
Apr 16 21:35:23 fit-pc systemd[1]: dev-disk-by\x2duuid-0b5c5288\x2d0e39\x2d44e2\x2db0cb\x2d49cc6f439f9b.swap: Succeeded.
Apr 16 21:35:23 fit-pc systemd[1]: Deactivated swap /dev/disk/by-uuid/0b5c5288-0e39-44e2-b0cb-49cc6f439f9b.
Apr 16 21:35:23 fit-pc systemd[1]: Reached target Unmount All Filesystems.
Apr 16 21:35:24 fit-pc systemd[1]: networking.service: Succeeded.
Apr 16 21:35:24 fit-pc systemd[1]: Stopped Raise network interfaces.
Apr 16 21:35:24 fit-pc systemd[1]: ifup@wlx48022a322063.service: Succeeded.
Apr 16 21:35:24 fit-pc systemd[1]: Stopped ifup for wlx48022a322063.
Apr 16 21:35:24 fit-pc systemd[1]: Stopped target Local File Systems.
Apr 16 21:35:24 fit-pc systemd[1]: Stopped target Local File Systems (Pre).
Apr 16 21:35:24 fit-pc systemd[1]: systemd-tmpfiles-setup-dev.service: Succeeded.
Apr 16 21:35:24 fit-pc systemd[1]: Stopped Create Static Device Nodes in /dev.
Apr 16 21:35:24 fit-pc systemd[1]: systemd-sysusers.service: Succeeded.
Apr 16 21:35:24 fit-pc systemd[1]: Stopped Create System Users.
Apr 16 21:35:24 fit-pc systemd[1]: systemd-remount-fs.service: Succeeded.
Apr 16 21:35:24 fit-pc systemd[1]: Stopped Remount Root and Kernel File Systems.
Apr 16 21:35:24 fit-pc systemd[1]: systemd-sysctl.service: Succeeded.
Apr 16 21:35:24 fit-pc systemd[1]: Stopped Apply Kernel Variables.
Apr 16 21:35:24 fit-pc systemd[1]: systemd-modules-load.service: Succeeded.
Apr 16 21:35:24 fit-pc systemd[1]: Stopped Load Kernel Modules.
Apr 16 21:35:24 fit-pc systemd[1]: Reached target Shutdown.
Apr 16 21:35:24 fit-pc systemd[1]: Reached target Final Step.
Apr 16 21:35:24 fit-pc systemd[1]: systemd-reboot.service: Succeeded.
Apr 16 21:35:24 fit-pc systemd[1]: Started Reboot.
Apr 16 21:35:24 fit-pc systemd[1]: Reached target Reboot.
Apr 16 21:35:24 fit-pc systemd[1]: Shutting down.
Apr 16 21:35:30 fit-pc systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Apr 16 21:35:30 fit-pc systemd-journald[198]: Journal stopped

[CommandLine_Warrior]

[quote="ohad"]When I try to issue a reboot command

Code: Select all

ohad@fit-pc:~$ sudo reboot

the system starts shutting down everything but doesn't actually reboot no matter how long I wait, so I have to physically cut and reconnect the power (the computer has an external power supply and no power button).

Look at the following source:
http://forum.debian.org.tr/index.php?topic=10862.0

[CommandLine_Warrior]

When I try to issue a reboot command

Code: Select all

ohad@fit-pc:~$ sudo reboot

the system starts shutting down everything but doesn't actually reboot no matter how long I wait, so I have to physically cut and reconnect the power (the computer has an external power supply and no power button).

Look at the following source:
http://forum.debian.org.tr/index.php?topic=10862.0

If not, try this command;

Code: Select all

$ sudo -s reboot -pf

[ohad]

Sorry, I don't know Turkish and had to use Google to translate, so maybe there are some things that I didn't get. Essentially the post seems to say that I should use restart instead of reboot.
This doesn't seem to apply in my case, as there is no restart command in my system.

The command

Code: Select all

sudo -s reboot -pf

doesn't work either: I get a print saying

Code: Select all

Rebooting.

and the terminal in which I ran the command stops interacting. But the rest of the system isn't affected at all, and I can open another terminal and keep running stuff as if nothing happened at all.

[CommandLine_Warrior]

Look at these:

https://www.linuxquestions.org/question ... 175563419/
https://www.lifewire.com/reboot-linux-u ... ne-4032621
https://bbs.archlinux.org/viewtopic.php?id=143113
https://www.binarytides.com/linux-comma ... rt-system/
https://www.computerhope.com/unix/uhalt.htm
https://www.recitalsoftware.com/blogs/1 ... ux-machine

actually the equivalent of the reboot command

Code: Select all

$ sudo -s shutdown -hr now

[ohad]

Hey. I appreciate your trying to help, but please don't just bury me in a bunch of other documents. It takes a lot of time to go through them, especially if they're long or refer to other sources themselves. Also, if I run into trouble following them I can't ask for help from the original writers who gave those suggestions.

Anyway, I did try following the advices in the links you gave, and here are the results in order of the link appearances:
1. The first suggestion is to install another distribution, namely Xubuntu, which I prefer not to do for several reasons, among which is that Ubuntu no longer officially supports my hardware, so I can expect more problems in the future. The second suggestion was to add "reboot=bios" to the grub. I modified /etc/default/grub, ran update-grub, and restarted the computer for the new settings to take effect. Further reboots still hang in the same manner as before.
2. This link only explains the expected behaviour of the reboot command, and doesn't have any advice on what to do when something goes wrong.
3. The suggestions include randomly downgrading stuff, which is not a practical solution. What eventually worked there was removing the file /etc/udev/rules.d/11-mnt-auto-mount.rules, which I don't have, and using UUIDs in /etc/fstab, which I already do. I do have a couple of udev rule files under /usr/lib/udev/rules.d/:

Code: Select all

01-md-raid-creating.rules
39-usbmuxd.rules
50-firmware.rules
50-udev-default.rules
55-dm.rules
60-block.rules
60-cdrom_id.rules
60-crda.rules
60-drm.rules
60-evdev.rules
60-input-id.rules
60-persistent-alsa.rules
60-persistent-input.rules
60-persistent-storage-dm.rules
60-persistent-storage-tape.rules
60-persistent-storage.rules
60-persistent-v4l.rules
60-sensor.rules
60-serial.rules
63-md-raid-arrays.rules
64-btrfs.rules
64-md-raid-assembly.rules
64-xorg-xkb.rules
65-libwacom.rules
69-md-clustered-confirm-device.rules
69-wacom.rules
70-joystick.rules
70-mouse.rules
70-power-switch.rules
70-touchpad.rules
70-u2f.rules
70-uaccess.rules
71-seat.rules
73-seat-late.rules
73-special-net-names.rules
73-usb-net-by-mac.rules
75-net-description.rules
75-probe_mtd.rules
78-sound-card.rules
80-debian-compat.rules
80-drivers.rules
80-ifupdown.rules
80-libinput-device-groups.rules
80-net-setup-link.rules
80-udisks2.rules
85-hdparm.rules
85-hwclock.rules
85-regulatory.rules
89-alsa-ucm.rules
90-alsa-restore.rules
90-console-setup.rules
90-libinput-model-quirks.rules
90-pulseaudio.rules
95-dm-notify.rules
95-upower-csr.rules
95-upower-hid.rules
95-upower-wup.rules
99-systemd.rules

but it is unclear to me which ones might be relevant to my case, and I don't want to just arbitrarily start removing configuration files.
4. Suggests issuing a reboot system request directly. This actually does work, but has two critical problems: first is that it's a dangerous procedure that can leave the system in an unclean state. The second problem is that it requires direct access to the machine, so I can't use it in headless mode.
5. As with link #2, there is no troubleshooting section.
6. This explains how to issue the system request from a remote computer. This sort-of solves the headlessness problem in #4, but at the price of increasing the probability of damaging the system, because to do that I need at least a few services (e.g. SSH, and probably also writeable filesystems) still running which I can't shut down before forcing the reboot.

The other command you gave as an equivalent to reboot behaves exactly like reboot itself, and hangs after shutting down the system without actually restarting.

On the whole I would say there is some progress: because the system request approach works, at least I know that there is no hardware limitation preventing rebooting. It only remains to find some way to get it to happen in a clean way.

[Head_on_a_Stick]

Try the acpi=force kernel parameter. You may have to also add reboot=acpi.

[ohad]

The acpi=force parameter didn't affect the reboot process, either with or without reboot=acpi.
I found the list of possible reboot kernel parameters here, so I'll try different combinations one by one to see if something sticks. Probably always with the force option enabled and also acpi=force to reduce the number of variations.

[ohad]

I tried setting the reboot parameter to all the combinations with the mode either warm or cold and the type being one of the six options bios, acpi, kbd, triple, efi, or pci. In addition, I always specified reboot force and acpi=force. I.e. twelve possible combinations, including for instance

Code: Select all

reboot=warm,acpi,force acpi=force

and

Code: Select all

reboot=cold,triple,force acpi=force

I did not try the soft and hard modes, which from the documentation I understand to be aliases of warm and cold, and I did not try the gpio mode which doesn't seem relevant.

For each combination I double-checked /proc/cmdline (to see which option I'm trying and avoid typos) before executing "sudo reboot". All of them behaved exactly the same as the original case, not actually rebooting the computer.

[Head_on_a_Stick]

Which version of Debian is this? What is your hardware?

[ohad]

I'm running the recent version of Debian:

Code: Select all

ohad@fit-pc:~$ lsb_release -a
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux 10 (buster)
Release:	10
Codename:	buster

Code: Select all

ohad@fit-pc:~$ uname -a
Linux fit-pc 4.19.0-8-686 #1 SMP Debian 4.19.98-1 (2020-01-26) i586 GNU/Linux

on a fit-PC1. The hardware overview is available here, and from within the system it shows as:

Code: Select all

ohad@fit-pc:~$ lspci
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] CS5536 [Geode companion] Host Bridge (rev 33)
00:01.1 VGA compatible controller: Advanced Micro Devices, Inc. [AMD] Geode LX Video
00:01.2 Entertainment encryption device: Advanced Micro Devices, Inc. [AMD] Geode LX AES Security Block
00:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter (rev 10)
00:0e.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter (rev 10)
00:0f.0 ISA bridge: Advanced Micro Devices, Inc. [AMD] CS5536 [Geode companion] ISA (rev 03)
00:0f.2 IDE interface: Advanced Micro Devices, Inc. [AMD] CS5536 [Geode companion] IDE (rev 01)
00:0f.3 Multimedia audio controller: Advanced Micro Devices, Inc. [AMD] CS5536 [Geode companion] Audio (rev 01)
00:0f.4 USB controller: Advanced Micro Devices, Inc. [AMD] CS5536 [Geode companion] OHC (rev 02)
00:0f.5 USB controller: Advanced Micro Devices, Inc. [AMD] CS5536 [Geode companion] EHC (rev 02)
00:0f.6 USB controller: Advanced Micro Devices, Inc. [AMD] CS5536 [Geode companion] UDC (rev 02)

[Head_on_a_Stick]

That hardware is really old so this may be a regression. Happens a lot with Linux, unfortunately.

https://wiki.debian.org/DebianKernel/GitBisect

[ohad]

Oh, that sucks then. I'll try to devote time to doing the bisection, but currently for me it'll probably be faster to just set up a newer computer.
I guess I should mark this as solved? Also, if I do manage to narrow down a regression, do you have any idea who should be notified? The Debian team? Someone on the kernel development? Someone else?

[Head_on_a_Stick]

if I do manage to narrow down a regression, do you have any idea who should be notified? The Debian team? Someone on the kernel development?

You should report it to the kernel developers. But be aware that they will request you try the latest stable kernel version first just in case the problem is fixed there.