You are not logged in.
Hi All,
After running for several hours, my computer cannot shut down completely. The details are as follows:
1. The display turns off.
2. The fan keeps spinning, and the fan's LED remains lit.
3. Pressing the power button on the computer case has no effect. I have to press and hold it (long press), after which the computer can be started again by pressing the button.
4. If I don’t perform a long press, cutting off the power and then restoring it causes the computer to restart automatically.
5. I’ve been dealing with this issue for quite a long time. I’ve tried many methods without success. I’ve also read all the related posts in this forum, but still no luck.
Basic information:
A desktop computer
CPU: Intel(R) Core(TM) i7-10700
Mother board: http://0x0.st/XFo8.txt
journalctl: http://0x0.st/XF-D.txt
I've tried linux and linux-lts kerners, The former seems more likely to encounter this problem.
Can anyone help me to find out what is wrong? Thanks a lot
Last edited by YangJun (2024-12-12 14:26:46)
Offline
Does the issue also happen with the latest release candidate?
sudo pacman -U https://pkgbuild.com/\~gromit/linux-bisection-kernels/linux-mainline-6.13rc2-1-x86_64.pkg.tar.zstOffline
sanity check: does this also happen from a live environment like an arch install media calling systemctl poweroff or shutdown?
Offline
Does the issue also happen with the latest release candidate?
sudo pacman -U https://pkgbuild.com/\~gromit/linux-bisection-kernels/linux-mainline-6.13rc2-1-x86_64.pkg.tar.zst
Yes, it happens. I installed this kernel, restarted, and shut it down immediately. The power was cut off as expected. However, after running this kernel overnight and then shutting it down, the issue occurred.
Offline
check: does this also happen from a live environment like an arch install media calling systemctl poweroff or shutdown?
I have a gparted live cd, it works well. I have used the Deepin system before and did not encounter this issue.
Offline
Dec 08 11:53:27 archlinux kernel: DMI: ASUS System Product Name/TUF GAMING B460M-PLUS (WI-FI), BIOS 1601 02/11/2022Is there a newer BIOS version available?
Dec 08 12:01:03 archlinux kernel: pcieport 0000:00:1d.0: AER: Correctable error message received from 0000:00:1d.0
Dec 08 12:01:03 archlinux kernel: pcieport 0000:00:1d.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Dec 08 12:01:03 archlinux kernel: pcieport 0000:00:1d.0: device [8086:a398] error status/mask=00000001/00002000lspci -tvnnThere's also some noise on
Dec 08 22:28:30 archlinux kernel: usb 1-3.3: device not accepting address 9, error -71
Dec 08 22:28:31 archlinux kernel: usb 1-3.3: new high-speed USB device number 10 using xhci_hcd
Dec 08 22:28:31 archlinux kernel: usb 1-3.3: device descriptor read/64, error -71
Dec 08 22:28:31 archlinux kernel: usb 1-3.3: New USB device found, idVendor=1f3a, idProduct=1001, bcdDevice= 4.40
Dec 08 22:28:31 archlinux kernel: usb 1-3.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dec 08 22:28:31 archlinux kernel: usb 1-3.3: Product: EPD106
Dec 08 22:28:31 archlinux kernel: usb 1-3.3: Manufacturer: Allwinner
Dec 08 22:28:31 archlinux kernel: usb 1-3.3: SerialNumber: 26011/00035244Is attaching that tablet (it seems) a precondition to cause this?
Online
Dec 08 11:53:27 archlinux kernel: DMI: ASUS System Product Name/TUF GAMING B460M-PLUS (WI-FI), BIOS 1601 02/11/2022Is there a newer BIOS version available?
Dec 08 12:01:03 archlinux kernel: pcieport 0000:00:1d.0: AER: Correctable error message received from 0000:00:1d.0 Dec 08 12:01:03 archlinux kernel: pcieport 0000:00:1d.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Dec 08 12:01:03 archlinux kernel: pcieport 0000:00:1d.0: device [8086:a398] error status/mask=00000001/00002000lspci -tvnnThere's also some noise on
Dec 08 22:28:30 archlinux kernel: usb 1-3.3: device not accepting address 9, error -71 Dec 08 22:28:31 archlinux kernel: usb 1-3.3: new high-speed USB device number 10 using xhci_hcd Dec 08 22:28:31 archlinux kernel: usb 1-3.3: device descriptor read/64, error -71 Dec 08 22:28:31 archlinux kernel: usb 1-3.3: New USB device found, idVendor=1f3a, idProduct=1001, bcdDevice= 4.40 Dec 08 22:28:31 archlinux kernel: usb 1-3.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Dec 08 22:28:31 archlinux kernel: usb 1-3.3: Product: EPD106 Dec 08 22:28:31 archlinux kernel: usb 1-3.3: Manufacturer: Allwinner Dec 08 22:28:31 archlinux kernel: usb 1-3.3: SerialNumber: 26011/00035244Is attaching that tablet (it seems) a precondition to cause this?
No newer BISO version available.
The output of lspci -tvnn
-[0000:00]-+-00.0 Intel Corporation 10th Gen Core Processor Host Bridge/DRAM Registers [8086:9b43]
+-02.0 Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:9bc5]
+-14.0 Intel Corporation Comet Lake PCH-V USB Controller [8086:a3af]
+-16.0 Intel Corporation Comet Lake PCH-V HECI Controller [8086:a3ba]
+-17.0 Intel Corporation 400 Series Chipset Family SATA AHCI Controller [8086:a382]
+-1b.0-[01]--
+-1b.4-[02]----00.0 Kingston Technology Company, Inc. A2000 NVMe SSD [SM2263EN] [2646:2263]
+-1c.0-[03]----00.0 Intel Corporation Wi-Fi 6 AX200 [8086:2723]
+-1d.0-[04]----00.0 MAXIO Technology (Hangzhou) Ltd. NVMe SSD Controller MAP1202 (DRAM-less) [1e4b:1202]
+-1f.0 Intel Corporation B460 Chipset LPC/eSPI Controller [8086:a3c8]
+-1f.2 Intel Corporation Cannon Lake PCH Power Management Controller [8086:a3a1]
+-1f.3 Intel Corporation Comet Lake PCH-V cAVS [8086:a3f0]
+-1f.4 Intel Corporation Comet Lake PCH-V SMBus Host Controller [8086:a3a3]
\-1f.6 Intel Corporation Ethernet Connection (12) I219-V [8086:0d55]I have the log of recently successfull shutdown: https://0x0.st/XFtr.txt. that indicate you probably right.
Offline
Please avoid bloating the thread with pointless full quotes, thanks.
Your nvme is on that bus, see https://wiki.archlinux.org/title/Solid_ … leshooting and test the impact of "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off" (start w/ only nvme_core.default_ps_max_latency_us=0)
But the allwinner android device might still be the shutdown impediment - was it attached during (all) the failing shutdown/poweroff?
Online
I adjusted the kernel parameters according to the wiki and updated the SSD firmware, but the issue still persists.
allwinner android device is not always connected.
the last time log: https://0x0.st/XCjS.txt
Sorry about quotes.
Thanks a lot
Offline