New: Hibernate failure with intel_iommu
A message that is not in the archive (sent off-list or not yet received): [email protected]/
A message that is not in the archive (sent off-list or not yet received): bug-90311-41252-3bo0kxnWaOQUvHkbgXJLS5sdmw4N0Rt+2LY78lusg7I@public.gmane.org/
[+cc Alex, linux-pci, iommu]
Quoted 36 lines · On Thu, Dec 25, 2014 at 12:13 PM, <bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BG…
https://bugzilla.kernel.org/show_bug.cgi?id=90311
Bug ID: 90311 Summary: Hibernate failure with intel_iommu Product: Drivers Version: 2.5 Kernel Version: 3.18.1 Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: PCI Assignee: drivers_pci-ztI5WcYan/[email protected] Reporter: [email protected] Regression: NoCreated attachment 161811
--> https://bugzilla.kernel.org/attachment.cgi?id=161811&action=edit
dmesg with iommu onEnabling intel_iommu=on causes uswsusp s2disk to fail. Hibernate always works fine without iommu and as far as I can tell everything works fine with iommu on without hibernating. With
intel_iommuset to on I can enter hibernate but the system doesn't come back properly. By that I mean the kernel can't read from swap and everything freezes. I can still switch between virtual terminals, view the system log and use magic sysrq to reboot. The system log is spammed with error messages from the scsi subsystem. http://i.imgur.com/ToFd8NM.jpg sdb contains root and swap.I'm guessing the iommu mapping isn't setup properly after resume so the disk controller can't do DMA anymore. I have made sure the kernel command line contains intel_iommu=on before and after suspend. I have one of the bad marvell 88SE9172 controllers but the swap is not connected to it (bug #42679).
Quoted 4 lines
I'm running a gentoo system with kernel 3.18.1 on a Gigabyte Z97X-Gaming G1 mobo with bios F7 (latest). Finding the problem might be difficult and I don't know what kind of information to provide. I can give you any debug output needed and apply debug patches if needed.
Is this a regression? If so, what was the most recent working kernel?
Quoted 39 lines · Bjorn Helgaas
[+cc Alex, linux-pci, iommu]
Quoted 36 lines · On Thu, Dec 25, 2014 at 12:13 PM, <[email protected]> wrote:
https://bugzilla.kernel.org/show_bug.cgi?id=90311
Bug ID: 90311 Summary: Hibernate failure with intel_iommu Product: Drivers Version: 2.5 Kernel Version: 3.18.1 Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: PCI Assignee: [email protected] Reporter: [email protected] Regression: NoCreated attachment 161811
--> https://bugzilla.kernel.org/attachment.cgi?id=161811&action=edit
dmesg with iommu onEnabling intel_iommu=on causes uswsusp s2disk to fail. Hibernate always works fine without iommu and as far as I can tell everything works fine with iommu on without hibernating. With
intel_iommuset to on I can enter hibernate but the system doesn't come back properly. By that I mean the kernel can't read from swap and everything freezes. I can still switch between virtual terminals, view the system log and use magic sysrq to reboot. The system log is spammed with error messages from the scsi subsystem. http://i.imgur.com/ToFd8NM.jpg sdb contains root and swap.I'm guessing the iommu mapping isn't setup properly after resume so the disk controller can't do DMA anymore. I have made sure the kernel command line contains intel_iommu=on before and after suspend. I have one of the bad marvell 88SE9172 controllers but the swap is not connected to it (bug #42679).
Quoted 6 lines
Quoted 4 lines
I'm running a gentoo system with kernel 3.18.1 on a Gigabyte Z97X-Gaming G1 mobo with bios F7 (latest). Finding the problem might be difficult and I don't know what kind of information to provide. I can give you any debug output needed and apply debug patches if needed.
Is this a regression? If so, what was the most recent working kernel?
It's not a regression but I've only been able to test iommu on kernel 3.17 and up because of that faulty marvell controller. Hibernate fails on both 3.17 and 3.18 but I don't know about older kernels.