Description of problem: Thinkpad T400 is reporting an error in console when suspending/resuming: dpm_run_callback(): pnp_bus_resume+0x0/0x70 return -19 PM: Device 00:0a failed to resume: error -19 and also PM: Device 00:0b failed to resume: error -19 and also PM: Device 00:0c failed to resume: error -19 Found in dmesg: [ 0.152968] pnp 00:0a: Plug and Play ACPI device, IDs PNP0501 (disabled) [ 1.028125] serial 00:0a: [io 0x03f8-0x03ff] [ 1.028189] serial 00:0a: [irq 4] [ 1.028413] serial 00:0a: activated [ 1.049085] 00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A [ 0.153073] pnp 00:0b: [io 0x03bc-0x03be] [ 0.153078] pnp 00:0b: [irq 7] [ 0.153135] pnp 00:0b: Plug and Play ACPI device, IDs PNP0400 (active) [ 30.150026] parport_pc 00:0b: reported by Plug and Play ACPI [ 0.173118] pnp 00:0c: [mem 0xfed40000-0xfed44fff] [ 0.173161] pnp 00:0c: Plug and Play ACPI device, IDs PNP0c31 (active) [ 24.774034] tpm_tis 00:0c: 1.2 TPM (device-id 0x1020, rev-id 6) [ 24.774037] tpm_tis 00:0c: Intel iTPM workaround enabled [ 24.862029] tpm_tis 00:0c: A TPM error (6) occurred attempting to read a pcr value [ 24.862033] tpm_tis 00:0c: TPM is disabled/deactivated (0x6) Steps to Reproduce: Suspend and resume T400 laptop several times while placed in dock. Additional info: It seems that there is possibly some issue with resume while the Thinkpad is using dock as the serial port a parallel port are not integral part of T400 but they are present on the dock.
# Mass update to all open bugs. Kernel 3.6.2-1.fc16 has just been pushed to updates. This update is a significant rebase from the previous version. Please retest with this kernel, and let us know if your problem has been fixed. In the event that you have upgraded to a newer release and the bug you reported is still present, please change the version field to the newest release you have encountered the issue with. Before doing so, please ensure you are testing the latest kernel update in that release and attach any new and relevant information you may have gathered. If you are not the original bug reporter and you still experience this bug, please file a new report, as it is possible that you may be seeing a different problem. (Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).
With no response, we are closing this bug under the assumption that it is no longer an issue. If you still experience this bug, please feel free to reopen the bug report.
Created attachment 648408 [details] screenshot
It still occurs in 3.6.6-1.fc17.x86_64
Also still the same issue on 3.6.5-2.fc16.i686 therefore reopening it.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
hi there)) have the same issue on F20 with all last updates... ---------------- >uname -a >Linux pa-wlan 3.14.4-200.fc20.x86_64 #1 SMP Tue May 13 13:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ---------------- [ 2642.167923] dpm_run_callback(): pnp_bus_resume+0x0/0x80 returns -19 [ 2642.167925] PM: Device 00:09 failed to resume: error -19 and [ 4716.052875] dpm_run_callback(): pnp_bus_resume+0x0/0xa0 returns -19 [ 4716.052878] PM: Device 00:09 failed to resume: error -19 ---------------- founded in "old" log-files (from 18.5 and 25.5 - days of restarts) I use Thinkpad T400, too. For more Information - just ask