Sorry for reusing the topic title, but my problem is exactly the same as in said threadMy-leap-15-4-system-restarts-on-shutdown but that topic was closed yesterday
I have done all the things mentioned in said thread: booted another distribution; run as root in a console; used ‘halt’, shutdown’, and ‘poweroff’.
The other distribution (in casu Debian 12) shuts beautifully down as it should but all the above mentioned commands resulted in a restart, effectively just rebooting the machine. The trouble started about a month ago, probably after an system update. Before that everything worked as expected.
The only effective way of shutting the thing down is this workaround: After having given the shutdown command wait with finger poised over the ‘c’ key until the Grub menu appears, hit ‘c’ and on the Grub command line enter ‘halt’. That command does work and shuts the machine down!
So in my opinion the problem is not hardware related but rather a software issue. I have a sneaking suspicion that it is related to systemd, because the three commands ‘halt’, ‘poweroff’, and ‘shutdown’ are all links to ‘/usr/bin/systemctl’.
I sincerely hope that some of you have either a solution to the problem or hints to what further investigations I should do.
1 Like
Note, you can split off reply into new topic with reference to the original post (click on the post timestamp, then + New Topic). I have not tried it for closed topics, but I expect it to work.
Shot in the dark:acpi=off ?
See The kernel’s command-line parameters — The Linux Kernel documentation , try playing with reboot= parameter, does some combination work for you?
1 Like
This parameter definitely has an effect on the process, but not the desired one. When the command is given the system shuts down, but the machine is not powered off. The only options now are either to manually push the power button or hit the reset button. But thanks for the shot.
Neither the page you link to or the man page ‘bootparam’ (which gives more in-depth info) are clear on when this parameter takes action. I have tried ‘reboot=soft’, but that had no effect.
Here you go:
System:
Kernel: 5.14.21-150500.55.52-default arch: x86_64 bits: 64 compiler: gcc v: 7.5.0
parameters: BOOT_IMAGE=/boot/vmlinuz-5.14.21-150500.55.52-default
root=/dev/mapper/System-Root splash=silent preempt=full mitigations=auto quiet
security=apparmor
Console: pty pts/1 DM: SDDM Distro: openSUSE Leap 15.5
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: N/A
Mobo: ASUSTeK model: PRIME B550M-K v: Rev X.0x serial: <filter>
UEFI: American Megatrends v: 2401 date: 05/26/2021
CPU:
Info: model: AMD Ryzen 5 5600X socket: AM4 bits: 64 type: MT MCP arch: Zen 3 gen: 4
level: v3 note: check built: 2021-22 process: TSMC n7 (7nm) family: 0x19 (25)
model-id: 0x21 (33) stepping: 0 microcode: 0xA201016
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache: L1: 384 KiB
desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB L3: 32 MiB desc: 1x32 MiB
Speed (MHz): avg: 2200 min/max: 2200/4650 boost: enabled base/boost: 3700/4650
scaling: driver: acpi-cpufreq governor: ondemand volts: 1.1 V ext-clock: 100 MHz cores:
1: 2200 2: 2200 3: 2200 4: 2200 5: 2200 6: 2200 7: 2200 8: 2200 9: 2200 10: 2200
11: 2200 12: 2200 bogomips: 88626
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: reg_file_data_sampling status: Not affected
Type: retbleed status: Not affected
Type: spec_rstack_overflow status: Vulnerable: Safe RET, no microcode
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and
seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW, STIBP:
always-on, RSB filling, PBRSB-eIBRS: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA GP108 [GeForce GT 1030] vendor: ASUSTeK driver: nvidia v: 550.54.14
alternate: nouveau,nvidia_drm non-free: 520.xx+ status: current (as of 2022-10)
arch: Pascal code: GP10x process: TSMC 16nm built: 2016-21 pcie: gen: 1
speed: 2.5 GT/s lanes: 4 link-max: gen: 3 speed: 8 GT/s ports: active: none
off: DVI-D-1 empty: HDMI-A-1 bus-ID: 0b:00.0 chip-ID: 10de:1d01 class-ID: 0300
Device-2: Logitech HD Webcam C910 type: USB driver: snd-usb-audio,uvcvideo
bus-ID: 3-2:3 chip-ID: 046d:0821 class-ID: 0e02 serial: <filter>
Display: x11 server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.5 compositor: kwin_x11
driver: X: loaded: nvidia unloaded: fbdev,modesetting,vesa alternate: nouveau,nv
gpu: nvidia,nvidia-nvswitch tty: 91x28
Monitor-1: DVI-D-1 model: Acer S222HQL serial: <filter> built: 2010 res: 1920x1080
dpi: 102 gamma: 1.2 size: 477x268mm (18.78x10.55") diag: 547mm (21.5") ratio: 16:9
modes: max: 1920x1080 min: 640x480
API: OpenGL Message: GL data unavailable in console for root.
Audio:
Device-1: NVIDIA GP108 High Definition Audio vendor: ASUSTeK driver: snd_hda_intel
bus-ID: 3-2:3 v: kernel chip-ID: 046d:0821 pcie: class-ID: 0e02 gen: 1 speed: 2.5 GT/s
serial: <filter> lanes: 4 link-max: gen: 3 speed: 8 GT/s bus-ID: 0b:00.1
chip-ID: 10de:0fb8 class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 0d:00.4 chip-ID: 1022:1487
class-ID: 0403
Device-3: Logitech HD Webcam C910 type: USB driver: snd-usb-audio,uvcvideo
Sound API: ALSA v: k5.14.21-150500.55.52-default running: yes
Sound Server-1: PulseAudio v: 15.0 running: yes
Sound Server-2: PipeWire v: 0.3.64 running: yes
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK PRIME B450M-A driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: f000 bus-ID: 0a:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB driver: btusb
v: 0.8 bus-ID: 1-3:2 chip-ID: 0a12:0001 class-ID: e001
Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block:
hardware: no software: yes address: see --recommends
RAID:
Supported mdraid levels: raid1
Device-1: md1 maj-min: 9:1 type: mdraid level: mirror status: active state: clean
size: 931.09 GiB
Info: report: 2/2 UU blocks: 976322240 chunk-size: N/A super-blocks: 1.2
Components: Online:
0: sda2 maj-min: 8:2 size: 931.22 GiB state: active sync
1: sdb2 maj-min: 8:18 size: 931.22 GiB state: active sync
Drives:
Local Storage: total: raw: 2.29 TiB usable: 1.38 TiB lvm-free: 300.54 GiB
used: 576.63 GiB (40.9%)
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Seagate model: XPG GAMMIX S11 Pro
size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4
type: SSD serial: <filter> rev: 42B2S7JA temp: 31.9 C scheme: GPT
SMART: yes health: PASSED on: 307d 15h cycles: 1,935 read-units: 11,235,156 [5.75 TB]
written-units: 7,915,730 [4.05 TB]
ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 1TB family: based SSDs
size: 931.51 GiB block-size: physical: 512 B logical: 512 B sata: 3.2 speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 4B6Q temp: 24 C scheme: GPT
SMART: yes state: enabled health: PASSED on: 337d 21h cycles: 2117 written: 3.66 TiB
ID-3: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 860 EVO 1TB
family: based SSDs size: 931.51 GiB block-size: physical: 512 B logical: 512 B
sata: 3.2 speed: 6.0 Gb/s type: SSD serial: <filter> rev: 4B6Q temp: 24 C scheme: GPT
SMART: yes state: enabled health: PASSED on: 337d 9h cycles: 2111 written: 4.7 TiB
Partition:
ID-1: / raw-size: 30 GiB size: 29.36 GiB (97.87%) used: 10.12 GiB (34.5%) fs: ext4
block-size: 4096 B dev: /dev/dm-0 maj-min: 254:0 mapped: System-Root
ID-2: /boot/efi raw-size: 500 MiB size: 499.7 MiB (99.95%) used: 5 MiB (1.0%)
fs: vfat block-size: 512 B dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 60 GiB size: 58.76 GiB (97.93%) used: 26.97 GiB (45.9%)
fs: ext4 block-size: 4096 B dev: /dev/dm-1 maj-min: 254:1 mapped: System-Home
ID-4: /tmp raw-size: 30 GiB size: 29.36 GiB (97.87%) used: 534 MiB (1.8%) fs: ext4
block-size: 4096 B dev: /dev/dm-3 maj-min: 254:3 mapped: System-Tmp
ID-5: /var raw-size: 20 GiB size: 19.52 GiB (97.59%) used: 6.67 GiB (34.2%) fs: ext4
block-size: 4096 B dev: /dev/dm-4 maj-min: 254:4 mapped: System-Var
Swap:
Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 2 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/nvme0n1p2 maj-min: 259:2
Sensors:
System Temperatures: cpu: 37.1 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 374 Uptime: 0h 4m wakeups: 390 Memory: 15.51 GiB used: 2.13 GiB (13.7%)
Init: systemd v: 249 target: graphical (5) default: graphical tool: systemctl
Compilers: gcc: 7.5.0 alt: 7 Packages: pm: rpm pkgs: N/A note: see --rpm
tools: yast,zypper pm: flatpak pkgs: 16 Shell: Bash (su) v: 4.4.23
running-in: pty pts/1 inxi: 3.3.23
Upgrade motherboard’s BIOS.
I have to close this thread because my computer has begun behaving correctly again. I have absolutely no idea of why but it will probably be a waste of time to try to find out.
system
April 3, 2024, 8:33pm
11
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
