Summary: | =sys-kernel/gentoo-sources-2.6.36-r5: suspend failes due to tpm_tis | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Stefan Huber <shuber> |
Component: | [OLD] Core system | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | chaujc, doron.fediuck |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://bugzilla.kernel.org/show_bug.cgi?id=20132 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Stefan Huber
2010-12-12 17:18:03 UTC
Apparently related prior bugs are known since the development phase of 2.6.36. (But since gentoo-sources-2.6.36-r4 works this seems to be a new issue). See: https://bugzilla.kernel.org/show_bug.cgi?id=16256 https://lists.linux-foundation.org/pipermail/bugme-new/2010-October/025821.html As reported above, removing the module tpm_tis before suspending (resp. hibernating) resolves the problem. (In reply to comment #1) > > As reported above, removing the module tpm_tis before suspending (resp. > hibernating) resolves the problem. > It seems that there's a nice workaround for it: modprobe -r tpm_tis && modprobe tpm_tis itpm=1 The itpm=1 parameter makes it work. Source: https://bbs.archlinux.org/viewtopic.php?id=109977 I appear to have the same problem/error on my Lenovo X301 (same error code, different numbers following pnp_bus_suspend though): [ 8341.241285] sd 0:0:0:0: [sda] Synchronizing SCSI cache [ 8341.247119] tpm_tis 00:0a: tpm_transmit: tpm_send: error -5 [ 8341.247130] legacy_suspend(): pnp_bus_suspend+0x0/0x90 returns -5 [ 8341.247134] PM: Device 00:0a failed to freeze: error -5 [ 8341.467030] sd 0:0:0:0: [sda] Starting disk Started consistently experiencing this after upgrading from sys-kernel/gentoo-sources-2.6.34-r12 to sys-kernel/gentoo-sources-2.6.36-r5. Activating the iTPM (the itpm=1 option to tpm_tis) workaround appears to fix this hibernation problem for me. Thanks! We'll track the upstream bug, it's good the workaround is working for you. |