Reboot command powers off the system

Status changed to 'Confirmed' because the bug affects multiple users.

This bug is awaiting verification that the linux/6.2.0-30.30 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux' to 'verification-done-lunar-linux'. If the problem still exists, change the tag 'verification-needed-lunar-linux' to 'verification-failed-lunar-linux'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

Installed the kernel packages from -proposed (6.2.0-30.30) on a DL380 Gen10 Plus which is affected by this bug and verified that the machine properly reboots when running the -proposed kernel.

Tried to the install from jammy-proposed & was unable to update kernel to 6.2.0-30.30

Here are the steps followed:

1) added the following to /etc/apt/sources.list

deb http://archive.ubuntu.com/ubuntu/ jammy-proposed restricted main multiverse universe

2) sudo apt-get update

3) sudo apt-get upgrade

Installation went fine but upon reboot the kernel version remained 5.19.0-051900-generic

As such the reboot issue still exists.

The kernel is in lunar-proposed. Which just made me realize that we need this in the current jammy HWE kernel. Sigh.

This bug is awaiting verification that the linux-nvidia-6.2/6.2.0-1010.10 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-6.2' to 'verification-done-jammy-linux-nvidia-6.2'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-6.2' to 'verification-failed-jammy-linux-nvidia-6.2'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

This bug was fixed in the package linux-hwe-6.2 - 6.2.0-32.32~22.04.1

---------------
linux-hwe-6.2 (6.2.0-32.32~22.04.1) jammy; urgency=medium

  * jammy/linux-hwe-6.2: 6.2.0-32.32~22.04.1 -proposed tracker (LP: #2030380)

  [ Ubuntu: 6.2.0-32.32 ]

  * lunar/linux: 6.2.0-32.32 -proposed tracker (LP: #2031134)
  * libgnutls report "trap invalid opcode" when trying to install packages over
    https (LP: #2031093)
    - [Config]: disable CONFIG_GDS_FORCE_MITIGATION

  [ Ubuntu: 6.2.0-30.30 ]

  * lunar/linux: 6.2.0-30.30 -proposed tracker (LP: #2030381)
  * CVE-2022-40982
    - init: Provide arch_cpu_finalize_init()
    - x86/cpu: Switch to arch_cpu_finalize_init()
    - ARM: cpu: Switch to arch_cpu_finalize_init()
    - ia64/cpu: Switch to arch_cpu_finalize_init()
    - m68k/cpu: Switch to arch_cpu_finalize_init()
    - mips/cpu: Switch to arch_cpu_finalize_init()
    - sh/cpu: Switch to arch_cpu_finalize_init()
    - sparc/cpu: Switch to arch_cpu_finalize_init()
    - um/cpu: Switch to arch_cpu_finalize_init()
    - init: Remove check_bugs() leftovers
    - init: Invoke arch_cpu_finalize_init() earlier
    - init, x86: Move mem_encrypt_init() into arch_cpu_finalize_init()
    - x86/init: Initialize signal frame size late
    - x86/fpu: Remove cpuinfo argument from init functions
    - x86/fpu: Mark init functions __init
    - x86/fpu: Move FPU initialization into arch_cpu_finalize_init()
    - x86/mem_encrypt: Unbreak the AMD_MEM_ENCRYPT=n build
    - x86/xen: Fix secondary processors' FPU initialization
    - x86/speculation: Add Gather Data Sampling mitigation
    - x86/speculation: Add force option to GDS mitigation
    - x86/speculation: Add Kconfig option for GDS
    - KVM: Add GDS_NO support to KVM
    - Documentation/x86: Fix backwards on/off logic about YMM support
    - [Config]: Enable CONFIG_ARCH_HAS_CPU_FINALIZE_INIT and
      CONFIG_GDS_FORCE_MITIGATION
  * CVE-2023-4015
    - netfilter: nf_tables: add NFT_TRANS_PREPARE_ERROR to deal with bound
      set/chain
    - netfilter: nf_tables: unbind non-anonymous set if rule construction fails
    - netfilter: nf_tables: skip immediate deactivate in _PREPARE_ERROR
  * CVE-2023-3995
    - netfilter: nf_tables: disallow rule addition to bound chain via
      NFTA_RULE_CHAIN_ID
  * CVE-2023-3777
    - netfilter: nf_tables: skip bound chain on rule flush
  * CVE-2023-3609
    - net/sched: cls_u32: Fix reference counter leak leading to overflow
  * NULL pointer dereference on CS35L41 HDA AMP (LP: #2029199)
    - ASoC: cs35l41: Refactor error release code
    - ALSA: cs35l41: Add shared boost feature
    - ASoC: dt-bindings: cirrus, cs35l41: Document CS35l41 shared boost
    - ALSA: hda: cs35l41: Ensure firmware/tuning pairs are always loaded
    - ALSA: hda: cs35l41: Enable Amp High Pass Filter
    - ALSA: cs35l41: Use mbox command to enable speaker output for external boost
    - ALSA: cs35l41: Poll for Power Up/Down rather than waiting a fixed delay
    - ALSA: hda: cs35l41: Check mailbox status of pause command after firmware
      load
    - ALSA: hda: cs35l41: Ensure we correctly re-sync regmap before system
      suspending.
    - ALSA: hda: cs35l41: Ensure we pass up any errors d...

This bug is awaiting verification that the linux-starfive/6.2.0-1004.5 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-starfive' to 'verification-done-lunar-linux-starfive'. If the problem still exists, change the tag 'verification-needed-lunar-linux-starfive' to 'verification-failed-lunar-linux-starfive'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

This bug is awaiting verification that the linux-aws-6.2/6.2.0-1013.13~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-aws-6.2' to 'verification-done-jammy-linux-aws-6.2'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-6.2' to 'verification-failed-jammy-linux-aws-6.2'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

not solved

On Sat, 9 Sept 2023 at 14:26, Ubuntu Kernel Bot <email address hidden>
wrote:

> This bug is awaiting verification that the linux-
> aws-6.2/6.2.0-1013.13~22.04.1 kernel in -proposed solves the problem.
> Please test the kernel and update this bug with the results. If the
> problem is solved, change the tag 'verification-needed-jammy-linux-
> aws-6.2' to 'verification-done-jammy-linux-aws-6.2'. If the problem
> still exists, change the tag 'verification-needed-jammy-linux-aws-6.2'
> to 'verification-failed-jammy-linux-aws-6.2'.
>
> If verification is not done by 5 working days from today, this fix will
> be dropped from the source code, and this bug will be closed.
>
> See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
> to enable and use -proposed. Thank you!
>
>
> ** Tags added: kernel-spammed-jammy-linux-aws-6.2-v2
> verification-needed-jammy-linux-aws-6.2
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (2032786).
> https://bugs.launchpad.net/bugs/2029332
>
> Title:
> Reboot command powers off the system
>
> Status in linux package in Ubuntu:
> Confirmed
> Status in linux-hwe-6.2 package in Ubuntu:
> Confirmed
> Status in linux-hwe-6.2 source package in Jammy:
> Fix Released
> Status in linux source package in Lunar:
> Fix Committed
>
> Bug description:
> [Impact]
>
> Issue: When a reboot (or init 6) command is issued the server shuts
> down instead.
>
> Expected behaviour: To reboot and NOT shutdown
>
> Impacted HW: HPE DL 380 OR Synergy 480 Gen 10 Plus Server 2P core
> count greater than 16 (like 24,28 or 32)
>
> Impacted OS: Ubuntu 22.04.2 kernel higher than 15.17.15
>
> When the CPU count is 1, issue is not observed. When core count is
> less than 24 (like 16) issue not observed.
>
> [Fix]
>
> Problem introduced in v5.18 with commit:
> 08f253ec3767 x86/cpu: Clear SME feature flag when not in use
>
> Fixes for the above:0
> 9b040453d444 x86/smp: Dont access non-existing CPUID leaf
> 1f5e7eb7868e x86/smp: Make stop_other_cpus() more robust
>
> [Test Case]
>
> $ sudo reboot
> Server should reboot and not power off.
>
> [Where Problems Could Occur]
>
> The fixes modify x86 stop-CPU code so reboot/poweroff of x86 machines
> could be affected.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2029332/+subscriptions
>
>

That is not a very helpful comment. Can you please provide some more data that makes you believe the problem is not fixed?

This bug is awaiting verification that the linux-azure/6.2.0-1013.13 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-azure' to 'verification-done-lunar-linux-azure'. If the problem still exists, change the tag 'verification-needed-lunar-linux-azure' to 'verification-failed-lunar-linux-azure'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

I have used the steps outlined in https://wiki.ubuntu.com/Testing/EnableProposed documentation how to enable and use -proposed however, the kernel is not getting updated and still see the reboot issue.

Steps followed:

1) Took an HPE DL360 Gen 10 Plus system running 5.19 kernel (5.19.0-051900) where the issue is observed & confirmed the reboot issue.

2) Followed the instructions to enable the Jammy-proposed

a) Verified using the GUI 'Software updater' in 'Developer Options' tab to ensure "Pre-released updates (jammy-proposed)" is checked.
b) Made sure the /etc/opt/sources.list has "deb http://us.archive.ubuntu.com/ubuntu jammy-proposed main restricted universe multiverse" is added to the file

3) Performed an update using the following commands:
sudo apt-get update
sudo apt-get upgrade

4) Rebooted the system & tried to verify:
a) the reboot problem still exists
b) the kernel version is 5.19.0-051900-generic

FYI - Normally the following steps are taken to update the kernel:

Open Terminal

cd ~/Downloads

wget -c https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.19/amd64/linux-headers-5.19.0-051900_5.19.0-051900.202207312230_all.deb

wget -c https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.19/amd64/linux-headers-5.19.0-051900-generic_5.19.0-051900.202207312230_amd64.deb

wget -c https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.19/amd64/linux-image-unsigned-5.19.0-051900-generic_5.19.0-051900.202207312230_amd64.deb

wget -c https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.19/amd64/linux-modules-5.19.0-051900-generic_5.19.0-051900.202207312230_amd64.deb

sudo apt install ./linux-headers-5.19.0*.deb ./linux-image-unsigned-5.19.0*.deb ./linux-modules-5.19.0*.deb

sudo apt-cache search linux-generic-hwe
linux-generic-hwe-20.04 - Complete Generic Linux kernel and headers (dummy transitional package)
linux-generic-hwe-20.04-edge - Complete Generic Linux kernel and headers (dummy transitional package)
linux-generic-hwe-22.04 - Complete Generic Linux kernel and headers
linux-generic-hwe-22.04-edge - Complete Generic Linux kernel and headers

Try installing the latest 6.2
sudo apt install linux-generic-hwe-22.04-edge

uname -a
Linux 6.2.0-34-generic #34~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 7 13:12:03 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

@masoodraoofi Mainline kernels from https://kernel.ubuntu.com/~kernel-ppa/mainline are unsupported. Why are you using them?

@mreeed8855 - that worked & I was able to install & confirm the fix supported in kernel 6.2.0-34-generic

@juergh - Can you please share the new supported links?