Neither shutdown nor suspend works in this kernel version. Systemd seems
to indicate it is trying at least, but the system hangs either right
before shutdown (clean situation, requiring a poweroff with the power
button) or before sleep (hung system, can't do anything except also hard
powering off and rebooting later).

Syslog from a suspend action:

Jan 16 06:43:53 Nesbitt NetworkManager[749]: <info>  [1579153433.6342] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Jan 16 06:43:53 Nesbitt NetworkManager[749]: <info>  [1579153433.6343] device (p2p-dev-wlan0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 16 06:43:53 Nesbitt NetworkManager[749]: <info>  [1579153433.6345] manager: NetworkManager state is now ASLEEP
Jan 16 06:43:53 Nesbitt systemd[1]: Reached target Sleep.
Jan 16 06:43:53 Nesbitt systemd[1]: Starting Suspend...
Jan 16 06:43:53 Nesbitt kernel: [55203.294410] PM: suspend entry (s2idle)
Jan 16 06:43:53 Nesbitt systemd-sleep[19110]: Suspending system...

Control: found -1 5.5.13-2

I have the same problem with 5.5.13-2 on a Lenovo Thinkpad T460p, with
4.19 from buster there is no such problem. I didn't debug any further
yet.

Best regards
Uwe

Hello again,
from this problem, but linux-image-5.6.0-trunk-amd64-unsigned
5.6.4-1~exp1 has the same problem.

On thing I noticed: When I send my Laptop in suspend, the power LED
starts blinking slowly (as it does with 4.19), but the FnLk LED stays on
which on 4.19 goes off shortly after suspend is reached. So I think the
problem is in the going to sleep step, not only when (not) waking up.

Best regards
Uwe

hello,

I started bisecting (but didn't complete yet, the weather is too good to
sit inside :-). Currently I see

	bad: 5.2.17-1+b1
	good: 5.2.6-1

So this is either a regression (also) in stable or something
Debian-specific (or I did something wrong).

Best regards
Uwe

Hello,

I checked the remaining versions in between the two above and the bisect
result is that

	5.2.7-1 is the last good; and
	5.2.9-1 is the first bad

kernel image. The relevant change between these two is:

	  * [x86] iommu: Enable INTEL_IOMMU_DEFAULT_ON (Closes: #934309)

. At least 5.2.7-1 shows the problematic behaviour when I add
"intel_iommu=on" on the kernel command line. I suspect I can boot newer
kernels with "intel_iommu=off", but didn't try that yet.

Related:

https://bugzilla.kernel.org/show_bug.cgi?id=197029

@Lennert: I assume you can still reproduce the problem. Do you care to
test with intel_iommu=off and report about the result? Just to make sure
you and I see the same problems?

Best regards
Uwe

\-------- Original Message --------
On 19 Apr 2020, 00:42, Uwe Kleine-König < uwe@kleine-koenig.org> wrote:
@Lennert: I assume you can still reproduce the problem. Do you care to test with intel\_iommu=off and report about the result? Just to make sure you and I see the same problems? Best regards Uwe

I'm afraid I can't test this anymore - due to serious i915 issues I've been building and running my own kernel packages. Currently running 5.7.0-rc1 (which is still just as broken as 5.4, 5.5 and 5.6... sigh) . I haven't seen the poweroff/suspend problem in a good while.

Hello Lennert,

So the newer kernels don't fix your problems? In my experience the i915
guys are quite responsive and willing to help if you run a recent
kernel.

Do you have INTEL_IOMMU and INTEL_IOMMU_DEFAULT_ON included in your
custom kernel? (If only the former: Do you suffer from the reported
problem when you add intel_iommu=on to the kernel command line?)

Best regards
Uwe

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

They don't. I've reported a bug for it a good while back:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949021

https://gitlab.freedesktop.org/xorg/driver/xf86-video-intel/issues/183
https://gitlab.freedesktop.org/mesa/mesa/-/issues/2352

Awfully quiet there. There seem to be multiple similar bugs around; so far the only response I got upstream was the bug being closed and moved to "mesa" (which I don't really get either). Debian bug didn't get any acknowledgement or comment.

I started with the stock Debian 5.5-rc config, and just did make oldconfig from there on (don't like to stray too far from the official packages). So the option should be identical to the Debian kernels.

$ grep INTEL_IOMMU Build/kernel/linux-5.7-rc1/.config
CONFIG_INTEL_IOMMU=y
CONFIG_INTEL_IOMMU_SVM=y
# CONFIG_INTEL_IOMMU_DEFAULT_ON is not set
CONFIG_INTEL_IOMMU_FLOPPY_WA=y
CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON=y


I don't reboot often, but I'll very likely run into the i915 hang above again soon, so I'll try the intel_iommu=on then.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
Verified: my 5.7.0-rc1 system with intel_iommu=on can suspend/resume without issues.

Hello,

I brought this problem to the attention of the x86 guys; see above URL
for the conversation.

Up to now no breaking insights.

@Lennert: Did you change your BIOS settings since the problem occured to
you? Lenny Szubowicz hinted it might be related to the TPM chip and
indeed switching it in the BIOS settings from 2.0 to 1.2 mode makes the
problem go away for me.

Best regards
Uwe

Just confirming that this issue is still present, causing a terrible
user experience when upgrading from Buster to Bullseye on a Lenovo
laptop. Verified on a 4th Gen Thinkpad X1 Carbon.

Setting intel_iommu=off is confirmed as workaround.

I understand from the upstream discussion that this is mostly a
Lenovo firmware issue.  But I still believe something needs to be
done in Debian to avoid every Lenovo user having to discover this
bug report and implement the workaround manually.  After first
experiencing a complete system failure when trying to suspend
the system.  A feature which worked without a flaw on Debian
Buster.


- -- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (700, 'stable'), (600, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

Kernel: Linux 5.6.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
-----BEGIN PGP SIGNATURE-----

iIQEARYKACwWIQRoe+CASfFh7aZ6shIiBE7Lv6RhXQUCXvSVXQ4cYmpvcm5AbW9y
ay5ubwAKCRAiBE7Lv6RhXd/GAQCIsozUqKlBr9BkIXoOXp7lFk9WouEh0QSYMm1F
oqluMwEA34mOpMqJL7bZWRAydIEctD1rWSAg7r1kpPAel1IwxAc=
=hTTU
-----END PGP SIGNATURE-----

control: found -1 linux/5.10.28-1

Ohai,

I can reproduce this on a Lenovo Thinkpad Yoga 260 with the latest
kernel in bullseye.
Disabling IOMMU on the command line or changing the TPM to 1.2
("dedicated") in the BIOS fixes the issue here.

Would be nice if we could at least document this issue as a known thing
in the release notes.

According to aptitude's log, the first 5.x kernel I installed on this
machine was 5.9.11-1 on 2020-12-02 and since booting into that kernel, I
have not been able to (truly) poweroff the system.
Before on a 4.19 kernel that was no problem.

This system is my server, running Xen with an Asus Z10PA-D8 MB. If I
want to fully power off, I need to use the iKVM module and run 'Power
Off Server - Immediate' which I do after running 'poweroff' on the
system and waiting long enough that it can do its shutdown activity.

I saw earlier in this bug report mentions of disabling IOMMU. As this is
my Xen host, I don't consider that a viable option.
I haven't tried 'intel_iommu=on' as I assume it's already on.

It looks like 'reportbug' didn't include much/any Xen info, so below
you'll find the output of 'xl dmesg':

(XEN) Xen version 4.14.2-pre (Debian 4.14.1+11-gb0b734a8b3-1) (pkg-xen-devel@lists.alioth.debian.org) (x86_64-linux-gnu-gcc (Debian 10.2.1-6) 10.2.1 20210110) debug=n  Sun Feb 28 18:49:45 UTC 2021
(XEN) build-id: 1d961284bd66e3f10fbec90933460876a1ba6893
(XEN) Bootloader: GRUB 2.04-17
(XEN) Command line: placeholder dom0_mem=16G,max:16G dom0_max_vcpus=4 dom0_vcpus_pin=true iommu=required,dom0-passthrough loglvl=all guest_loglvl=all ucode=scan vga=gfx-1280x1024x32 smt=yes
(XEN) Xen image load base address: 0x79200000
(XEN) Video information:
(XEN)  VGA is graphics mode 1280x1024, 32 bpp
(XEN)  VBE/DDC methods: none; EDID transfer time: 1 seconds
(XEN)  EDID info not retrieved because no DDC retrieval method detected
(XEN) Disc information:
(XEN)  Found 5 MBR signatures
(XEN)  Found 5 EDD information structures
(XEN) CPU Vendor: Intel, Family 6 (0x6), Model 79 (0x4f), Stepping 1 (raw 000406f1)
(XEN) Xen-e820 RAM map:
(XEN)  [0000000000000000, 000000000009e7ff] (usable)
(XEN)  [000000000009e800, 000000000009ffff] (reserved)
(XEN)  [00000000000e0000, 00000000000fffff] (reserved)
(XEN)  [0000000000100000, 0000000079a89fff] (usable)
(XEN)  [0000000079a8a000, 000000007b8ccfff] (reserved)
(XEN)  [000000007b8cd000, 000000007b926fff] (ACPI data)
(XEN)  [000000007b927000, 000000007bed1fff] (ACPI NVS)
(XEN)  [000000007bed2000, 000000008fffffff] (reserved)
(XEN)  [00000000fed1c000, 00000000fed44fff] (reserved)
(XEN)  [00000000ff000000, 00000000ffffffff] (reserved)
(XEN)  [0000000100000000, 000000407fffffff] (usable)
(XEN) ACPI: RSDP 000F0580, 0024 (r2 ALASKA)
(XEN) ACPI: XSDT 7B8DF0A8, 00CC (r1 ALASKA   A M I   1072009 AMI     10013)
(XEN) ACPI: FACP 7B90BAB0, 010C (r5 ALASKA   A M I   1072009 AMI     10013)
(XEN) ACPI: DSDT 7B8DF210, 2C89F (r2 ALASKA   A M I   1072009 INTL 20091013)
(XEN) ACPI: FACS 7BED0F80, 0040
(XEN) ACPI: APIC 7B90BBC0, 0224 (r3 ALASKA   A M I   1072009 AMI     10013)
(XEN) ACPI: FPDT 7B90BDE8, 0044 (r1 ALASKA   A M I   1072009 AMI     10013)
(XEN) ACPI: FIDT 7B90BE30, 009C (r1 ALASKA   A M I   1072009 AMI     10013)
(XEN) ACPI: MCFG 7B90BED0, 003C (r1 ALASKA    A M I  1072009 MSFT       97)
(XEN) ACPI: EINJ 7B926DF8, 0130 (r1 ALASKA   A M I         1 INTL        1)
(XEN) ACPI: UEFI 7B90BF68, 0042 (r1 ALASKA   A M I   1072009             0)
(XEN) ACPI: HPET 7B90BFB0, 0038 (r1 ALASKA   A M I         1 INTL 20091013)
(XEN) ACPI: MSCT 7B90BFE8, 0090 (r1 ALASKA   A M I         1 INTL 20091013)
(XEN) ACPI: SLIT 7B90C078, 0030 (r1 ALASKA   A M I         1 INTL 20091013)
(XEN) ACPI: SRAT 7B90C0A8, 1158 (r3 ALASKA   A M I         1 INTL 20091013)
(XEN) ACPI: WDDT 7B90D200, 0040 (r1 ALASKA   A M I         0 INTL 20091013)
(XEN) ACPI: SSDT 7B90D240, 16FB3 (r2 ALASKA    PmMgt        1 INTL 20120913)
(XEN) ACPI: SPMI 7B9241F8, 0041 (r5 ALASKA   A M I         0 AMI.        0)
(XEN) ACPI: SSDT 7B924240, 2652 (r2 ALASKA SpsNm           2 INTL 20120913)
(XEN) ACPI: SSDT 7B926898, 0064 (r2 ALASKA SpsNvs          2 INTL 20120913)
(XEN) ACPI: PRAD 7B926900, 0102 (r2 ALASKA   A M I         2 INTL 20120913)
(XEN) ACPI: DMAR 7B926A08, 00E8 (r1 ALASKA   A M I         1 INTL 20091013)
(XEN) ACPI: HEST 7B926AF0, 00A8 (r1 ALASKA   A M I         1 INTL        1)
(XEN) ACPI: BERT 7B926B98, 0030 (r1 ALASKA   A M I         1 INTL        1)
(XEN) ACPI: ERST 7B926BC8, 0230 (r1 ALASKA   A M I         1 INTL        1)
(XEN) System RAM: 262042MB (268331168kB)
(XEN) SRAT: PXM 0 -> APIC 00 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 02 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 04 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 06 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 08 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 0a -> Node 0
(XEN) SRAT: PXM 0 -> APIC 0c -> Node 0
(XEN) SRAT: PXM 0 -> APIC 0e -> Node 0
(XEN) SRAT: PXM 1 -> APIC 10 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 12 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 14 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 16 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 18 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 1a -> Node 1
(XEN) SRAT: PXM 1 -> APIC 1c -> Node 1
(XEN) SRAT: PXM 1 -> APIC 1e -> Node 1
(XEN) SRAT: PXM 0 -> APIC 01 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 03 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 05 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 07 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 09 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 0b -> Node 0
(XEN) SRAT: PXM 0 -> APIC 0d -> Node 0
(XEN) SRAT: PXM 0 -> APIC 0f -> Node 0
(XEN) SRAT: PXM 1 -> APIC 11 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 13 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 15 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 17 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 19 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 1b -> Node 1
(XEN) SRAT: PXM 1 -> APIC 1d -> Node 1
(XEN) SRAT: PXM 1 -> APIC 1f -> Node 1
(XEN) SRAT: Node 0 PXM 0 0-80000000
(XEN) SRAT: Node 0 PXM 0 100000000-2080000000
(XEN) SRAT: Node 1 PXM 1 2080000000-4080000000
(XEN) NUMA: Allocated memnodemap from 407abd6000 - 407abd7000
(XEN) NUMA: Using 19 for the hash shift.
(XEN) Domain heap initialised DMA width 32 bits
(XEN) vesafb: framebuffer at 0x00000000c4000000, mapped to 0xffff82c000201000, using 6144k, total 32768k
(XEN) vesafb: mode is 1280x1024x32, linelength=5120, font 8x16
(XEN) vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
(XEN) found SMP MP-table at 000fdc20
(XEN) DMI 2.8 present.
(XEN) DMI not present.
(XEN) x2APIC mode is already enabled by BIOS.
(XEN) Using APIC driver x2apic_cluster
(XEN) ACPI: PM-Timer IO Port: 0x408 (24 bits)
(XEN) ACPI: v5 SLEEP INFO: control[0:0], status[0:0]
(XEN) ACPI: SLEEP INFO: pm1x_cnt[1:404,1:0], pm1x_evt[1:400,1:0]
(XEN) ACPI: 32/64X FACS address mismatch in FADT - 7bed0f80/0000000000000000, using 32
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x04] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x06] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x0c] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x0e] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x14] lapic_id[0x14] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x16] lapic_id[0x16] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x1c] lapic_id[0x1c] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x1e] lapic_id[0x1e] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x05] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x0d] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x0f] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x15] lapic_id[0x15] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x17] lapic_id[0x17] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x1d] lapic_id[0x1d] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x1f] lapic_id[0x1f] enabled)
(XEN) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x0c] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x0e] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x14] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x16] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x1c] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x1e] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x0d] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x0f] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x15] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x17] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x1d] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x1f] high edge lint[0x1])
(XEN) ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 1, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: IOAPIC (id[0x02] address[0xfec01000] gsi_base[24])
(XEN) IOAPIC[1]: apic_id 2, version 32, address 0xfec01000, GSI 24-47
(XEN) ACPI: IOAPIC (id[0x03] address[0xfec40000] gsi_base[48])
(XEN) IOAPIC[2]: apic_id 3, version 32, address 0xfec40000, GSI 48-71
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) ACPI: HPET id: 0x8086a701 base: 0xfed00000
(XEN) PCI: MCFG configuration 0: base 80000000 segment 0000 buses 00 - ff
(XEN) PCI: MCFG area at 80000000 reserved in E820
(XEN) PCI: Using MCFG for segment 0000 bus 00-ff
(XEN) Xen ERST support is initialized.
(XEN) HEST: Table parsing has been initialized
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) SMP: Allowing 32 CPUs (0 hotplug CPUs)
(XEN) IRQ limits: 72 GSI, 6584 MSI/MSI-X
(XEN) microcode: CPU0 updated from revision 0xb000036 to 0xb000038, date = 2019-06-18
(XEN) CPU0: 1200 ... 2100 MHz
(XEN) xstate: size: 0x340 and states: 0x7
(XEN) CMCI: threshold 0x2 too large for CPU0 bank 17, using 0x1
(XEN) CMCI: threshold 0x2 too large for CPU0 bank 18, using 0x1
(XEN) CMCI: threshold 0x2 too large for CPU0 bank 19, using 0x1
(XEN) CPU0: Intel machine check reporting enabled
(XEN) Speculative mitigation facilities:
(XEN)   Hardware features: IBRS/IBPB STIBP L1D_FLUSH SSBD MD_CLEAR
(XEN)   Compiled-in support: INDIRECT_THUNK SHADOW_PAGING
(XEN)   Xen settings: BTI-Thunk RETPOLINE, SPEC_CTRL: IBRS- SSBD-, Other: IBPB L1D_FLUSH VERW BRANCH_HARDEN
(XEN)   L1TF: believed vulnerable, maxphysaddr L1D 46, CPUID 46, Safe address 300000000000
(XEN)   Support for HVM VMs: MSR_SPEC_CTRL RSB EAGER_FPU MD_CLEAR
(XEN)   Support for PV VMs: MSR_SPEC_CTRL RSB EAGER_FPU MD_CLEAR
(XEN)   XPTI (64-bit PV only): Dom0 enabled, DomU enabled (with PCID)
(XEN)   PV L1TF shadowing: Dom0 disabled, DomU enabled
(XEN) Using scheduler: SMP Credit Scheduler rev2 (credit2)
(XEN) Initializing Credit2 scheduler
(XEN)  load_precision_shift: 18
(XEN)  load_window_shift: 30
(XEN)  underload_balance_tolerance: 0
(XEN)  overload_balance_tolerance: -3
(XEN)  runqueues arrangement: socket
(XEN)  cap enforcement granularity: 10ms
(XEN) load tracking window length 1073741824 ns
(XEN) Platform timer is 14.318MHz HPET
(XEN) Detected 2095.159 MHz processor.
(XEN) alt table ffff82d04043d290 -> ffff82d04044955c
(XEN) Intel VT-d iommu 0 supported page sizes: 4kB, 2MB, 1GB
(XEN) Intel VT-d iommu 1 supported page sizes: 4kB, 2MB, 1GB
(XEN) Intel VT-d Snoop Control enabled.
(XEN) Intel VT-d Dom0 DMA Passthrough enabled.
(XEN) Intel VT-d Queued Invalidation enabled.
(XEN) Intel VT-d Interrupt Remapping enabled.
(XEN) Intel VT-d Posted Interrupt not enabled.
(XEN) Intel VT-d Shared EPT tables enabled.
(XEN) I/O virtualisation enabled
(XEN)  - Dom0 mode: Passthrough
(XEN) Interrupt remapping enabled
(XEN) nr_sockets: 2
(XEN) Enabled directed EOI with ioapic_ack_old on!
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using old ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) TSC deadline timer enabled
(XEN) Defaulting to alternative key handling; send 'A' to switch to normal mode.
(XEN) Allocated console ring of 256 KiB.
(XEN) mwait-idle: MWAIT substates: 0x2120
(XEN) mwait-idle: v0.4.1 model 0x4f
(XEN) mwait-idle: lapic_timer_reliable_states 0xffffffff
(XEN) VMX: Supported advanced features:
(XEN)  - APIC MMIO access virtualisation
(XEN)  - APIC TPR shadow
(XEN)  - Extended Page Tables (EPT)
(XEN)  - Virtual-Processor Identifiers (VPID)
(XEN)  - Virtual NMI
(XEN)  - MSR direct-access bitmap
(XEN)  - Unrestricted Guest
(XEN)  - APIC Register Virtualization
(XEN)  - Virtual Interrupt Delivery
(XEN)  - Posted Interrupt Processing
(XEN)  - VMCS shadowing
(XEN)  - VM Functions
(XEN)  - Virtualisation Exceptions
(XEN)  - Page Modification Logging
(XEN) HVM: ASIDs enabled.
(XEN) VMX: Disabling executable EPT superpages due to CVE-2018-12207
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware Assisted Paging (HAP) detected
(XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB
(XEN) alt table ffff82d04043d290 -> ffff82d04044955c
(XEN) microcode: CPU2 updated from revision 0xb000036 to 0xb000038, date = 2019-06-18
(XEN) microcode: CPU4 updated from revision 0xb000036 to 0xb000038, date = 2019-06-18
(XEN) microcode: CPU6 updated from revision 0xb000036 to 0xb000038, date = 2019-06-18
(XEN) microcode: CPU8 updated from revision 0xb000036 to 0xb000038, date = 2019-06-18
(XEN) microcode: CPU10 updated from revision 0xb000036 to 0xb000038, date = 2019-06-18
(XEN) microcode: CPU12 updated from revision 0xb000036 to 0xb000038, date = 2019-06-18
(XEN) microcode: CPU14 updated from revision 0xb000036 to 0xb000038, date = 2019-06-18
(XEN) microcode: CPU16 updated from revision 0xb000036 to 0xb000038, date = 2019-06-18
(XEN) CMCI: threshold 0x2 too large for CPU16 bank 17, using 0x1
(XEN) CMCI: threshold 0x2 too large for CPU16 bank 18, using 0x1
(XEN) CMCI: threshold 0x2 too large for CPU16 bank 19, using 0x1
(XEN) microcode: CPU18 updated from revision 0xb000036 to 0xb000038, date = 2019-06-18
(XEN) microcode: CPU20 updated from revision 0xb000036 to 0xb000038, date = 2019-06-18
(XEN) microcode: CPU22 updated from revision 0xb000036 to 0xb000038, date = 2019-06-18
(XEN) microcode: CPU24 updated from revision 0xb000036 to 0xb000038, date = 2019-06-18
(XEN) microcode: CPU26 updated from revision 0xb000036 to 0xb000038, date = 2019-06-18
(XEN) microcode: CPU28 updated from revision 0xb000036 to 0xb000038, date = 2019-06-18
(XEN) microcode: CPU30 updated from revision 0xb000036 to 0xb000038, date = 2019-06-18
(XEN) Brought up 32 CPUs
(XEN) Scheduling granularity: cpu, 1 CPU per sched-resource
(XEN) Adding cpu 0 to runqueue 0
(XEN)  First cpu on runqueue, activating
(XEN) Adding cpu 1 to runqueue 0
(XEN) Adding cpu 2 to runqueue 0
(XEN) Adding cpu 3 to runqueue 0
(XEN) Adding cpu 4 to runqueue 0
(XEN) Adding cpu 5 to runqueue 0
(XEN) Adding cpu 6 to runqueue 0
(XEN) Adding cpu 7 to runqueue 0
(XEN) Adding cpu 8 to runqueue 0
(XEN) Adding cpu 9 to runqueue 0
(XEN) Adding cpu 10 to runqueue 0
(XEN) Adding cpu 11 to runqueue 0
(XEN) Adding cpu 12 to runqueue 0
(XEN) Adding cpu 13 to runqueue 0
(XEN) Adding cpu 14 to runqueue 0
(XEN) Adding cpu 15 to runqueue 0
(XEN) Adding cpu 16 to runqueue 1
(XEN)  First cpu on runqueue, activating
(XEN) Adding cpu 17 to runqueue 1
(XEN) Adding cpu 18 to runqueue 1
(XEN) Adding cpu 19 to runqueue 1
(XEN) Adding cpu 20 to runqueue 1
(XEN) Adding cpu 21 to runqueue 1
(XEN) Adding cpu 22 to runqueue 1
(XEN) Adding cpu 23 to runqueue 1
(XEN) Adding cpu 24 to runqueue 1
(XEN) Adding cpu 25 to runqueue 1
(XEN) Adding cpu 26 to runqueue 1
(XEN) Adding cpu 27 to runqueue 1
(XEN) Adding cpu 28 to runqueue 1
(XEN) Adding cpu 29 to runqueue 1
(XEN) Adding cpu 30 to runqueue 1
(XEN) Adding cpu 31 to runqueue 1
(XEN) mcheck_poll: Machine check polling timer started.
(XEN) NX (Execute Disable) protection active
(XEN) Dom0 has maximum 904 PIRQs
(XEN) *** Building a PV Dom0 ***
(XEN)  Xen  kernel: 64-bit, lsb, compat32
(XEN)  Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x322c000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   000000401c000000->0000004020000000 (4168696 pages to be allocated)
(XEN)  Init. ramdisk: 000000407dbf8000->000000407fffffb3
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: ffffffff81000000->ffffffff8322c000
(XEN)  Init. ramdisk: 0000000000000000->0000000000000000
(XEN)  Phys-Mach map: 0000008000000000->0000008002000000
(XEN)  Start info:    ffffffff8322c000->ffffffff8322c4b8
(XEN)  Xenstore ring: 0000000000000000->0000000000000000
(XEN)  Console ring:  0000000000000000->0000000000000000
(XEN)  Page tables:   ffffffff8322d000->ffffffff8324a000
(XEN)  Boot stack:    ffffffff8324a000->ffffffff8324b000
(XEN)  TOTAL:         ffffffff80000000->ffffffff83400000
(XEN)  ENTRY ADDRESS: ffffffff82c2f160
(XEN) Dom0 has maximum 4 VCPUs
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Scrubbing Free RAM in background
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input to DOM0 (type 'CTRL-a' three times to switch input)
(XEN) Freed 556kB init memory
(XEN) PCI add device 0000:ff:08.0
(XEN) PCI add device 0000:ff:08.2
(XEN) PCI add device 0000:ff:08.3
(XEN) PCI add device 0000:ff:09.0
(XEN) PCI add device 0000:ff:09.2
(XEN) PCI add device 0000:ff:09.3
(XEN) PCI add device 0000:ff:0b.0
(XEN) PCI add device 0000:ff:0b.1
(XEN) PCI add device 0000:ff:0b.2
(XEN) PCI add device 0000:ff:0b.3
(XEN) PCI add device 0000:ff:0c.0
(XEN) PCI add device 0000:ff:0c.1
(XEN) PCI add device 0000:ff:0c.2
(XEN) PCI add device 0000:ff:0c.3
(XEN) PCI add device 0000:ff:0c.4
(XEN) PCI add device 0000:ff:0c.5
(XEN) PCI add device 0000:ff:0c.6
(XEN) PCI add device 0000:ff:0c.7
(XEN) PCI add device 0000:ff:0f.0
(XEN) PCI add device 0000:ff:0f.1
(XEN) PCI add device 0000:ff:0f.4
(XEN) PCI add device 0000:ff:0f.5
(XEN) PCI add device 0000:ff:0f.6
(XEN) PCI add device 0000:ff:10.0
(XEN) PCI add device 0000:ff:10.1
(XEN) PCI add device 0000:ff:10.5
(XEN) PCI add device 0000:ff:10.6
(XEN) PCI add device 0000:ff:10.7
(XEN) PCI add device 0000:ff:12.0
(XEN) PCI add device 0000:ff:12.1
(XEN) PCI add device 0000:ff:13.0
(XEN) PCI add device 0000:ff:13.1
(XEN) PCI add device 0000:ff:13.2
(XEN) PCI add device 0000:ff:13.3
(XEN) PCI add device 0000:ff:13.4
(XEN) PCI add device 0000:ff:13.5
(XEN) PCI add device 0000:ff:13.6
(XEN) PCI add device 0000:ff:13.7
(XEN) PCI add device 0000:ff:14.0
(XEN) PCI add device 0000:ff:14.1
(XEN) PCI add device 0000:ff:14.2
(XEN) PCI add device 0000:ff:14.3
(XEN) PCI add device 0000:ff:14.4
(XEN) PCI add device 0000:ff:14.5
(XEN) PCI add device 0000:ff:14.6
(XEN) PCI add device 0000:ff:14.7
(XEN) PCI add device 0000:ff:15.0
(XEN) PCI add device 0000:ff:15.1
(XEN) PCI add device 0000:ff:15.2
(XEN) PCI add device 0000:ff:15.3
(XEN) PCI add device 0000:ff:16.0
(XEN) PCI add device 0000:ff:16.6
(XEN) PCI add device 0000:ff:16.7
(XEN) PCI add device 0000:ff:17.0
(XEN) PCI add device 0000:ff:17.4
(XEN) PCI add device 0000:ff:17.5
(XEN) PCI add device 0000:ff:17.6
(XEN) PCI add device 0000:ff:17.7
(XEN) PCI add device 0000:ff:1e.0
(XEN) PCI add device 0000:ff:1e.1
(XEN) PCI add device 0000:ff:1e.2
(XEN) PCI add device 0000:ff:1e.3
(XEN) PCI add device 0000:ff:1e.4
(XEN) PCI add device 0000:ff:1f.0
(XEN) PCI add device 0000:ff:1f.2
(XEN) PCI add device 0000:7f:08.0
(XEN) PCI add device 0000:7f:08.2
(XEN) PCI add device 0000:7f:08.3
(XEN) PCI add device 0000:7f:09.0
(XEN) PCI add device 0000:7f:09.2
(XEN) PCI add device 0000:7f:09.3
(XEN) PCI add device 0000:7f:0b.0
(XEN) PCI add device 0000:7f:0b.1
(XEN) PCI add device 0000:7f:0b.2
(XEN) PCI add device 0000:7f:0b.3
(XEN) PCI add device 0000:7f:0c.0
(XEN) PCI add device 0000:7f:0c.1
(XEN) PCI add device 0000:7f:0c.2
(XEN) PCI add device 0000:7f:0c.3
(XEN) PCI add device 0000:7f:0c.4
(XEN) PCI add device 0000:7f:0c.5
(XEN) PCI add device 0000:7f:0c.6
(XEN) PCI add device 0000:7f:0c.7
(XEN) PCI add device 0000:7f:0f.0
(XEN) PCI add device 0000:7f:0f.1
(XEN) PCI add device 0000:7f:0f.4
(XEN) PCI add device 0000:7f:0f.5
(XEN) PCI add device 0000:7f:0f.6
(XEN) PCI add device 0000:7f:10.0
(XEN) PCI add device 0000:7f:10.1
(XEN) PCI add device 0000:7f:10.5
(XEN) PCI add device 0000:7f:10.6
(XEN) PCI add device 0000:7f:10.7
(XEN) PCI add device 0000:7f:12.0
(XEN) PCI add device 0000:7f:12.1
(XEN) PCI add device 0000:7f:13.0
(XEN) PCI add device 0000:7f:13.1
(XEN) PCI add device 0000:7f:13.2
(XEN) PCI add device 0000:7f:13.3
(XEN) PCI add device 0000:7f:13.4
(XEN) PCI add device 0000:7f:13.5
(XEN) PCI add device 0000:7f:13.6
(XEN) PCI add device 0000:7f:13.7
(XEN) PCI add device 0000:7f:14.0
(XEN) PCI add device 0000:7f:14.1
(XEN) PCI add device 0000:7f:14.2
(XEN) PCI add device 0000:7f:14.3
(XEN) PCI add device 0000:7f:14.4
(XEN) PCI add device 0000:7f:14.5
(XEN) PCI add device 0000:7f:14.6
(XEN) PCI add device 0000:7f:14.7
(XEN) PCI add device 0000:7f:15.0
(XEN) PCI add device 0000:7f:15.1
(XEN) PCI add device 0000:7f:15.2
(XEN) PCI add device 0000:7f:15.3
(XEN) PCI add device 0000:7f:16.0
(XEN) PCI add device 0000:7f:16.6
(XEN) PCI add device 0000:7f:16.7
(XEN) PCI add device 0000:7f:17.0
(XEN) PCI add device 0000:7f:17.4
(XEN) PCI add device 0000:7f:17.5
(XEN) PCI add device 0000:7f:17.6
(XEN) PCI add device 0000:7f:17.7
(XEN) PCI add device 0000:7f:1e.0
(XEN) PCI add device 0000:7f:1e.1
(XEN) PCI add device 0000:7f:1e.2
(XEN) PCI add device 0000:7f:1e.3
(XEN) PCI add device 0000:7f:1e.4
(XEN) PCI add device 0000:7f:1f.0
(XEN) PCI add device 0000:7f:1f.2
(XEN) PCI add device 0000:00:00.0
(XEN) PCI add device 0000:00:01.0
(XEN) PCI add device 0000:00:02.0
(XEN) PCI add device 0000:00:03.0
(XEN) PCI add device 0000:00:05.0
(XEN) PCI add device 0000:00:05.1
(XEN) PCI add device 0000:00:05.2
(XEN) PCI add device 0000:00:05.4
(XEN) PCI add device 0000:00:11.0
(XEN) PCI add device 0000:00:11.4
(XEN) PCI add device 0000:00:14.0
(XEN) PCI add device 0000:00:16.0
(XEN) PCI add device 0000:00:16.1
(XEN) PCI add device 0000:00:1a.0
(XEN) PCI add device 0000:00:1c.0
(XEN) PCI add device 0000:00:1c.4
(XEN) PCI add device 0000:00:1c.5
(XEN) PCI add device 0000:00:1c.7
(XEN) PCI add device 0000:00:1d.0
(XEN) PCI add device 0000:00:1f.0
(XEN) PCI add device 0000:00:1f.2
(XEN) PCI add device 0000:00:1f.3
(XEN) PCI add device 0000:02:00.0
(XEN) PCI add device 0000:02:00.1
(XEN) PCI add device 0000:04:00.0
(XEN) PCI add device 0000:05:00.0
(XEN) PCI add device 0000:06:00.0
(XEN) PCI add device 0000:07:00.0
(XEN) PCI add device 0000:08:00.0
(XEN) PCI add device 0000:80:05.0
(XEN) PCI add device 0000:80:05.1
(XEN) PCI add device 0000:80:05.2
(XEN) PCI add device 0000:80:05.4

So this problem isn't restricted to Lenovo or laptops; I don't use
suspend though.

Cheers,
  Diederik

Hi!

I have the exact same problem on a fresh Debian 11 installation and a
T460s laptop.

Changing TPM from 2.0 to 1.2 in the BIOS resolves the poweroff and the
suspend issue.

Also FYI (not sure if that helps), as I did not found 949020 earlier, I
have used the following workaround on Buster + 5.10 bpo kernel
(hibernating just after booting to then be able to suspend until next
reboot):
| echo reboot >/sys/power/disk
| echo disk >/sys/power/state

As far as I can remember, I did not had the poweroff problem on Buster,
just suspend.

I was having (probably) related Issues on a Thinkpad T460. On a fresh install with encrypted LVM I could not cleanly shut down. After running "systemctl poweroff" the system showed me the usual systemd-logs on a console, but would not power off, showing

systemd-shutdown[1]: Could not detach DM /dev/dm-0: Device or resource busy.
systemd-shutdown[1]: Failed to finalize DM devices, ignoring.
pmouse serio2: Failed to disable mouse on synaptics-pc/serio0.
reboot: Power down.

From journalctl from a corresponding boot:
Mar 12 18:11:48 debian systemd-cryptsetup[1966]: Device sda3_crypt is still in use.Mar 12 18:11:48 debian systemd-cryptsetup[1966]: Failed to deactivate: Device or resource busyMar 12 18:11:48 debian systemd[1]: systemd-cryptsetup@sda3_crypt.service: Control process exited, code=exited, status=1/FAILUREMar 12 18:11:48 debian systemd[1]: systemd-cryptsetup@sda3_crypt.service: Failed with result 'exit-code'.Mar 12 18:11:48 debian systemd[1]: Stopped Cryptography Setup for sda3_crypt.

I then installed a newer kernel (6.0.0) from Backports. Booting into the newer kernel I could now shut down and the machine would actually power off, but I had trouble powering it on again. I had to repeatedly press the power-button, and it would sometimes, seemingly randomly, react to that, and sometimes not. Neither being connected to a power-supply, a socket, having the removable battery removed or not, nor the state of charge of the batteries seemed to have an impact.

Switching to TPM 1.2 solved both problems (not powering off with 5.10 and not powering on with 6.0).

Dear Maintainer,

   * What led up to the situation?
The kernel update from linux-image-6.1.0-44-amd64 to linux-image-6.1.0-45-amd64.

   * What exactly did you do (or not do) that was effective (or
     ineffective)?
Hibernate, poweroff or reboot my syste after an hour of using it. Initially
after booting it seems to work, but no longer after an hour or so. To me it
seems the acpi kernel modules are unloaded over time and not reloaded when
needed.

   * What was the outcome of this action?
I could switch off my system only by using the power button.

   * What outcome did you expect instead?
Poweroff, reboot or suspend my system from the command line.

Hi,

I suspect this is unlikely to be the same issue as repored in #949020.

After testing it is not #1135599 (i.e. testing the revert commit), if
it is differnt issue and still reproducing, could you please fill a
new bugreport separated from this?

Regards,
Salvatore