FS#55705 - [linux] intel_mmu from 4.13.3-1 causes my Thinkpad T560 to fail to resume from suspend
Attached to Project:
Arch Linux
Opened by Ronan (ronjouch) - Friday, 22 September 2017, 15:38 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 11 October 2017, 17:44 GMT
Opened by Ronan (ronjouch) - Friday, 22 September 2017, 15:38 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 11 October 2017, 17:44 GMT
|
Details
Description:
With intel_mmu=on (default in 4.13), on my Thinkpad T560, suspend works, but pressing on POWER / Enter / whatever key (which under 4.12 resumes the system) doesn't resume; I have to force shutdown with a long press on POWER, and restart. Turning intel_mmu=off from GRUB works around the issue. Additional info: * package version: bug present in testing/linux-{4.13.3-1, 4.13.2-1} * config and/or log files etc: none, please help me help you, I have no idea what to provide and where to look Steps to reproduce: |
This task depends upon
Closed by Doug Newgard (Scimmia)
Wednesday, 11 October 2017, 17:44 GMT
Reason for closing: Fixed
Additional comments about closing: linux 4.13.5-1
Wednesday, 11 October 2017, 17:44 GMT
Reason for closing: Fixed
Additional comments about closing: linux 4.13.5-1
- A few users affected on Reddit: https://www.reddit.com/r/archlinux/comments/72z2rv/linux_41331_is_in_core/dnmjaeo/
- Got news from Intel engineers on the iommu mailing list, they will be having a look: https://lists.linuxfoundation.org/pipermail/iommu/2017-September/024383.html
- Rolling back to 4.12.13-1 and manually activating `intel_iommu=on`, resume is similarly broken. Thus, this bug has nothing specific to 4.13; `intel_iommu={on, igfx_on}` probably have been breaking resume for a long time on my system, I just happened to notice it now due to being `on` by default.