Bug#949020: linux-image-5.5.0-rc5-amd64: Poweroff/suspend doesn't work in 5.5.0-rc5
- To: Uwe Kleine-König <uwe@kleine-koenig.org>, 949020@bugs.debian.org
- Cc: Lennert Van Alboom <lennert@vanalboom.org>
- Subject: Bug#949020: linux-image-5.5.0-rc5-amd64: Poweroff/suspend doesn't work in 5.5.0-rc5
- From: Evgeni Golov <evgeni@debian.org>
- Date: Sat, 24 Apr 2021 15:11:55 +0200
- Message-id: <[🔎] 20210424131155.yhq3i7es4wnz5pcv@yatsu.egolov.redhat.com>
- Reply-to: Evgeni Golov <evgeni@debian.org>, 949020@bugs.debian.org
- In-reply-to: <20200511202219.GA2890@taurus.defre.kleine-koenig.org>
- References: <20200418112226.GA4039@taurus.defre.kleine-koenig.org> <20200418131835.GA2466@taurus.defre.kleine-koenig.org> <20200418224242.GA2248@taurus.defre.kleine-koenig.org> <RJh6dyMTQBla5JtK3GvRK49Gu2MWflEOjEKMJDHKLleyCAfzE0eDoac04cupTCJxyvD6yewh0UZ4IC0EoBCvY_ePSicRB2qMRqYf7BYuI8c=@vanalboom.org> <20200419135616.GA8193@taurus.defre.kleine-koenig.org> <oNQiO631oR-qzcLZOK56iifKAoq-LTEXoBrWAyWpa2GMzzO-3T7KpzhPTR4Nx9eduLIPCBOzqg2y5UtPg2FcaNZUxQlFsl_gwvtaewY6cEg=@vanalboom.org> <157916038430.2653.3254320802053211816.reportbug@Nesbitt.lan.init6.eu> <24WQk-s2DnZThg8-bZXjMyuYgZQ5QjrzBhEYShjonBY9K684PXa8jNA0uNmPWhcP4p_4qSB5YAFcORrvUW8GukR-_IVXEcf5XvblTBy8uZ8=@vanalboom.org> <157916038430.2653.3254320802053211816.reportbug@Nesbitt.lan.init6.eu> <20200511202219.GA2890@taurus.defre.kleine-koenig.org> <157916038430.2653.3254320802053211816.reportbug@Nesbitt.lan.init6.eu>
control: found -1 linux/5.10.28-1
Ohai,
On Mon, May 11, 2020 at 10:22:23PM +0200, Uwe Kleine-König wrote:
> > Verified: my 5.7.0-rc1 system with intel_iommu=on can suspend/resume without issues.
>
> 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.
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.
Reply to: