Bug 720904

As of two days, I've started having problems with suspend on my Thinkpad R61. The machine has been suspending and resuming like clockwork for ages before that, so something must have changed.

The problem appeared after I got a nouveau hang which forced me to reboot. After that I've seen the behaviour that the first suspend works, but the second time it will fail to suspend and resume again immediately. Trying the suspend a few more times results in a lockup.

I checked dmesg and this is what I can see as the problem:

[66822.978939] Freezing user space processes ... (elapsed 0.01 seconds) done.
[66822.990125] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
[66823.001114] PM: Entering mem sleep
[66823.001168] Suspending console(s) (use no_console_suspend to debug)
[66823.013475] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[66823.013599] sd 0:0:0:0: [sda] Stopping disk
[66823.237024] parport_pc 00:0b: disable failed
[66823.237031] legacy_suspend(): pnp_bus_suspend+0x0/0x85 returns -5
[66823.237034] PM: Device 00:0b failed to suspend: error -5
[66823.237036] PM: Some devices failed to suspend
[66823.572247] sd 0:0:0:0: [sda] Starting disk
[66823.780919] thinkpad_acpi: ACPI backlight control delay disabled
[66823.787270] PM: resume of devices complete after 550.229 msecs
[66823.787441] PM: Finishing wakeup.
[66823.787442] Restarting tasks ... done.
[66823.797105] video LNXVIDEO:01: Restoring backlight state

As you can see, it is complaining about parport_pc. I tried to remove the module and attempt the suspend again, but all I got was the hang.

I'm running the same kernel as when things were fine (2.6.35.13-92.fc14.x86_64). The machine had been running for about a month before the forced reboot:

[root@mjolnir log]# grep Linux.version messages-*
messages-20110619:Jun 15 19:31:28 mjolnir kernel: [    0.000000] Linux version 2.6.35.13-92.fc14.x86_64 (mockbuild.fedoraproject.org) (gcc version 4.5.1 20100924 (Red Hat 4.5.1-4) (GCC) ) #1 SMP Sat May 21 17:26:25 UTC 2011

Oddly enough, I have not a single line about the parallel port before the problems started:

[root@mjolnir log]# grep parport messages-*
[root@mjolnir log]#

A whole bunch after though:

[root@mjolnir log]# grep parport messages
Jul 11 14:28:15 mjolnir kernel: [    5.778727] parport_pc 00:0b: [io  0x03bc-0x03be]
Jul 11 14:28:15 mjolnir kernel: [    5.778909] parport_pc 00:0b: [irq 7]
Jul 11 14:28:15 mjolnir kernel: [    5.779693] parport_pc 00:0b: activated
Jul 11 14:28:15 mjolnir kernel: [    5.779697] parport_pc 00:0b: reported by Plug and Play ACPI
Jul 11 14:28:15 mjolnir kernel: [    5.779762] parport0: PC-style at 0x3bc, irq 7 [PCSPP,TRISTATE]
Jul 11 17:56:22 mjolnir kernel: [ 9519.488852] parport_pc 00:0b: disabled
Jul 11 17:56:22 mjolnir kernel: [ 9524.760219] parport_pc 00:0b: activated
Jul 12 09:51:20 mjolnir kernel: [66823.237024] parport_pc 00:0b: disable failed
Jul 12 09:53:52 mjolnir kernel: [66975.315818] parport_pc 00:0b: disable failed
Jul 12 10:16:40 mjolnir kernel: [    5.297108] parport_pc 00:0b: [io  0x03bc-0x03be]
Jul 12 10:16:40 mjolnir kernel: [    5.297311] parport_pc 00:0b: [irq 7]
Jul 12 10:16:40 mjolnir kernel: [    5.298001] parport_pc 00:0b: activated
Jul 12 10:16:40 mjolnir kernel: [    5.298005] parport_pc 00:0b: reported by Plug and Play ACPI
Jul 12 10:16:40 mjolnir kernel: [    5.298102] parport0: PC-style at 0x3bc, irq 7 [PCSPP,TRISTATE]
Jul 12 21:00:12 mjolnir kernel: [37289.232991] parport_pc 00:0b: disabled
Jul 12 21:00:12 mjolnir kernel: [37294.404218] parport_pc 00:0b: activated
Jul 13 09:27:12 mjolnir kernel: [82116.979593] parport_pc 00:0b: disable failed
Jul 13 09:28:56 mjolnir kernel: [82221.310936] parport_pc 00:0b: disable failed
Jul 13 09:29:17 mjolnir kernel: [82242.374266] parport_pc 00:0b: disable failed

I'm a bit confused where this came from. I have not been in the BIOS for months and I haven't booted the other OS recently either. :/

And no, the machine does not have a parellel port.