Created attachment 299947 [details] System devices Using two different Intel Z690 boards my system fails to fully shutdown/restart when using Linux. I am no expert but it appears the ACPI signal isn't working correctly. Currently systemd finishes it shutdown procedure and I have to hold power button to get the system to poweroff. I have tried default distribution kernels and every RC of 5.16. To note Windows 10/11 doesn't have this problem on both motherboards. Perhaps I have gotten very unlucky and ended up with two different brand boards with buggy ACPI implementations.
I've got the same issue with Gigabyte Z690m. It looks to me that it's somwhow connected to that one - https://lore.kernel.org/netdev/227af6b0692a0a57f5fb349d4d9c914301753209.camel@gmx.de/t/#u Machine reboots fine if ethernet disabled in BIOS. And (when etehernet enabled) bringing down ethernet interface hangs the system.
(In reply to Dmitri Sosnik from comment #1) > I've got the same issue with Gigabyte Z690m. It looks to me that it's > somwhow connected to that one - > https://lore.kernel.org/netdev/227af6b0692a0a57f5fb349d4d9c914301753209. > camel@gmx.de/t/#u > > Machine reboots fine if ethernet disabled in BIOS. And (when etehernet > enabled) bringing down ethernet interface hangs the system. After going back to <= 5.14 PC can reboot, shutdown and sleep. When I have some time I'll go back to 5.15 kernel and test disabling Ethernet too if I can get the same behaviour.
(In reply to Darren from comment #2) > (In reply to Dmitri Sosnik from comment #1) > > I've got the same issue with Gigabyte Z690m. It looks to me that it's > > somwhow connected to that one - > > https://lore.kernel.org/netdev/227af6b0692a0a57f5fb349d4d9c914301753209. > > camel@gmx.de/t/#u > > > > Machine reboots fine if ethernet disabled in BIOS. And (when etehernet > > enabled) bringing down ethernet interface hangs the system. > > After going back to <= 5.14 PC can reboot, shutdown and sleep. When I have > some time I'll go back to 5.15 kernel and test disabling Ethernet too if I > can get the same behaviour. Although on the surface I don't think the NIC issue is the problem I'm facing. My systems get to the point of unmounting all disks.
(In reply to Darren from comment #3) > Although on the surface I don't think the NIC issue is the problem I'm > facing. My systems get to the point of unmounting all disks. I've same issue on Z690. In my case it's caused by Intel Eth driver (igc). You can easily check it by disabling ethernet in BIOS. Thorsten Leemhuis already pinged the devs regarding merging the patch: https://lore.kernel.org/netdev/4d1aad6b-8470-c834-6b4c-df6490cf7ab6@leemhuis.info/
(In reply to Mikhail Kondrashov from comment #4) > (In reply to Darren from comment #3) > > Although on the surface I don't think the NIC issue is the problem I'm > > facing. My systems get to the point of unmounting all disks. > > I've same issue on Z690. In my case it's caused by Intel Eth driver (igc). > You can easily check it by disabling ethernet in BIOS. > > Thorsten Leemhuis already pinged the devs regarding merging the patch: > https://lore.kernel.org/netdev/4d1aad6b-8470-c834-6b4c-df6490cf7ab6@leemhuis. > info/ Your right, just tried kernel 5.15> and disabling eth fixes problem.
Hi, is this bug already resolved in 5.17rc1 kernel ? Thanks.
I have Ubuntu 21.10 and Kernel 5.6.10 and it's shutting and rebooting correctly. Maybe you close this bug ?
sorry 5.16.10
Now I have this error with ACPI. [ 1.459001] ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20210930/psparse-529) [ 1.459235] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20210930/dsfield-184) [ 1.459338] ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20210930/dswload2-477)
Great, Bug close as the problem has been fixed in latest kernel. For the ACPI errors, it is likely to be caused by broken BIOS AML code, if you want to debugger further, please create a new bug report for it, together with the acpidump file and full dmesg output after boot.