Comment 14 for bug 1824893

      Well I've managed to screw up my machine massively and don't know how
to get it back to a sane state.

      I deleted what I thought were all traces of 5.0.9 that I had
compiled and re-ran update-grub2, then I installed:

rw-r--r-- 1 nanook rmtonly 10877978 Apr 22 23:20
linux-headers-4.15.18-041518_4.15.18-041518.201804190330_all.deb
-rw-r--r-- 1 nanook rmtonly 1056602 Apr 22 23:20
linux-headers-4.15.18-041518-generic_4.15.18-041518.201804190330_amd64.deb
-rw-r--r-- 1 nanook rmtonly 1059488 Apr 22 23:20
linux-headers-4.15.18-041518-lowlatency_4.15.18-041518.201804190330_amd64.deb
-rw-r--r-- 1 nanook rmtonly 52634544 Apr 22 23:21
linux-image-4.15.18-041518-generic_4.15.18-041518.201804190330_amd64.deb
-rw-r--r-- 1 nanook rmtonly 52642100 Apr 22 23:21
linux-image-4.15.18-041518-lowlatency_4.15.18-041518.201804190330_amd64.deb

      And ran another update-grub2 with the following output:

ourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.0.0-13-lowlatency
Found initrd image: /boot/initrd.img-5.0.0-13-lowlatency
Found linux image: /boot/vmlinuz-5.0.0-13-lowlatency
Found initrd image: /boot/initrd.img-5.0.0-13-lowlatency
Found linux image: /boot/vmlinuz-4.15.18-041518-lowlatency
Found initrd image: /boot/initrd.img-4.15.18-041518-lowlatency
Found linux image: /boot/vmlinuz-4.15.18-041518-generic
Found initrd image: /boot/initrd.img-4.15.18-041518-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
Found Mac OS X on /dev/sda2
done

      So I expected to see 4.15 generic and low latency in addition to
5.0.0-13-lowlatency in my boot menu, but instead I see 5.0.9 (which even though
I've removed vmlinux-5.0.9 starts to boot) and 5.0.13, 4.15.18 doesn't show
up.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
  Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
    Knowledgeable human assistance, not telephone trees or script readers.
  See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Tue, 23 Apr 2019, Kai-Heng Feng wrote:

> Date: Tue, 23 Apr 2019 05:12:05 -0000
> From: Kai-Heng Feng <email address hidden>
> Reply-To: Bug 1824893 <email address hidden>
> To: <email address hidden>
> Subject: [Bug 1824893] Re: When I type systemctl reboot system reaches Target
> Reboot but then does not reboot
>
> Prebuilt binaries can be found here:
> https://kernel.ubuntu.com/~kernel-ppa/mainline/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1824893
>
> Title:
> When I type systemctl reboot system reaches Target Reboot but then
> does not reboot
>
> Status in systemd package in Ubuntu:
> New
>
> Bug description:
> This is similar to the bug where systemd used to get stuck in target
> Shutdown except that bug affected all my hardware, now it gets stuck
> at target Reboot but this only affects my elderly Mac Pro 1,1 and does
> not affect my laptop or i7-6700k and i7-6850k based servers.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 19.04
> Package: systemd 240-6ubuntu5
> ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1
> Uname: Linux 5.0.0-8-lowlatency x86_64
> ApportVersion: 2.20.10-0ubuntu27
> Architecture: amd64
> CurrentDesktop: MATE
> Date: Mon Apr 15 16:30:34 2019
> InstallationDate: Installed on 2018-12-06 (130 days ago)
> InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2)
> MachineType: Apple Computer, Inc. MacPro2,1
> ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1
> SourcePackage: systemd
> SystemdDelta:
> [EXTENDED] /lib/systemd/system/ondemand.service ÿÿ /lib/systemd/system/ondemand.service.d/ubuntustudio.conf
> [EXTENDED] /lib/systemd/system/rc-local.service ÿÿ /lib/systemd/system/rc-local.service.d/debian.conf
> [EXTENDED] /lib/systemd/system/user@.service ÿÿ /lib/systemd/system/user@.service.d/timeout.conf
>
> 3 overridden configuration files found.
> UpgradeStatus: Upgraded to disco on 2019-03-08 (38 days ago)
> dmi.bios.date: 07/02/07
> dmi.bios.vendor: Apple Computer, Inc.
> dmi.bios.version: MP21.88Z.007F.B06.0707021348
> dmi.board.asset.tag: Base Board Asset Tag#
> dmi.board.name: Mac-F4208DC8
> dmi.board.vendor: Apple Inc.
> dmi.board.version: PVT
> dmi.chassis.asset.tag: Asset Tag#
> dmi.chassis.type: 2
> dmi.chassis.vendor: Apple Computer, Inc.
> dmi.chassis.version: Mac-F4208DC8
> dmi.modalias: dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8:
> dmi.product.family: MacPro
> dmi.product.name: MacPro2,1
> dmi.product.sku: System SKU#
> dmi.product.version: 1.0
> dmi.sys.vendor: Apple Computer, Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824893/+subscriptions
>