My test platform is a ASUS M2N32-SLI moboard with dual core AMD.
I upgraded (DVD) from 12.1, preserving my /home partition.
I am currently running the “stock” 12.2/KDE 4.85/Kernel 3.4.6
I have performed updates from the on-line OSS, nonOSS and Updates repos but little else.
I am stuck trying to get s2ram to work again (worked fine on 11.4, 12.1)
Here is a /var/log/pm-suspend.log
((I had to delete pm-suspend.log to meet the charter count restriction. Where did that come from?? pm-suspend.log does not appear to be informative))
Here is a segment of /var/log/messages in the time frame of the suspend failure:
Oct 5 19:08:59 PVE-Beast kernel: 1190.448034] PM: Entering mem sleep
Oct 5 19:08:59 PVE-Beast kernel: 1190.448060] Suspending console(s) (use no_console_suspend to debug)
Oct 5 19:08:59 PVE-Beast kernel: 1190.448408] sd 4:0:0:0: [sdc] Synchronizing SCSI cache
Oct 5 19:08:59 PVE-Beast kernel: 1190.448469] sd 3:0:0:0: [sdb] Synchronizing SCSI cache
Oct 5 19:08:59 PVE-Beast kernel: 1190.448587] sd 2:0:0:0: [sda] Synchronizing SCSI cache
Oct 5 19:08:59 PVE-Beast kernel: 1190.448779] parport_pc 00:0a: disabled
Oct 5 19:08:59 PVE-Beast kernel: 1190.448913] serial 00:09: disabled
Oct 5 19:08:59 PVE-Beast kernel: 1190.448918] serial 00:09: wake-up capability disabled by ACPI
Oct 5 19:08:59 PVE-Beast kernel: 1190.449202] ACPI handle has no context!
Oct 5 19:08:59 PVE-Beast kernel: 1190.450726] sd 4:0:0:0: [sdc] Stopping disk
Oct 5 19:08:59 PVE-Beast kernel: 1190.460161] sd 2:0:0:0: [sda] Stopping disk
Oct 5 19:08:59 PVE-Beast kernel: 1190.462755] sd 3:0:0:0: [sdb] Stopping disk
Oct 5 19:08:59 PVE-Beast kernel: 1220.704438] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct 5 19:08:59 PVE-Beast kernel: 1220.704441] ata3.00: failed command: STANDBY IMMEDIATE
Oct 5 19:08:59 PVE-Beast kernel: 1220.704445] ata3.00: cmd e0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Oct 5 19:08:59 PVE-Beast kernel: 1220.704446] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 5 19:08:59 PVE-Beast kernel: 1220.704447] ata3.00: status: { DRDY }
Oct 5 19:08:59 PVE-Beast kernel: 1220.704451] ata3: hard resetting link
Oct 5 19:08:59 PVE-Beast kernel: 1220.704452] ata3: nv: skipping hardreset on occupied port
Oct 5 19:08:59 PVE-Beast kernel: 1220.768527] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct 5 19:08:59 PVE-Beast kernel: 1220.768528] ata5.00: failed command: STANDBY IMMEDIATE
Oct 5 19:08:59 PVE-Beast kernel: 1220.768532] ata5.00: cmd e0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Oct 5 19:08:59 PVE-Beast kernel: 1220.768533] res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 (timeout)
Oct 5 19:08:59 PVE-Beast kernel: 1220.768534] ata5.00: status: { DRDY }
Oct 5 19:08:59 PVE-Beast kernel: 1220.768537] ata5: hard resetting link
Oct 5 19:08:59 PVE-Beast kernel: 1220.768538] ata5: nv: skipping hardreset on occupied port
Oct 5 19:08:59 PVE-Beast kernel: 1221.158025] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Oct 5 19:08:59 PVE-Beast kernel: 1221.167309] ata3.00: configured for UDMA/133
Oct 5 19:08:59 PVE-Beast kernel: 1221.167311] ata3.00: device reported invalid CHS sector 0
Oct 5 19:08:59 PVE-Beast kernel: 1221.167317] ata3: EH complete
Oct 5 19:08:59 PVE-Beast kernel: 1221.167328] sd 2:0:0:0: [sda] START_STOP FAILED
Oct 5 19:08:59 PVE-Beast kernel: 1221.167331] sd 2:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Oct 5 19:08:59 PVE-Beast kernel: 1221.167334] sd 2:0:0:0: [sda] Sense Key : Aborted Command [current] [descriptor]
Oct 5 19:08:59 PVE-Beast kernel: 1221.167336] sd 2:0:0:0: [sda] Add. Sense: No additional sense information
Oct 5 19:08:59 PVE-Beast kernel: 1221.167344] dpm_run_callback(): scsi_bus_suspend+0x0/0x20 returns 134217730
Oct 5 19:08:59 PVE-Beast kernel: 1221.167348] PM: Device 2:0:0:0 failed to suspend async: error 134217730
Oct 5 19:08:59 PVE-Beast kernel: 1221.222025] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Oct 5 19:08:59 PVE-Beast kernel: 1226.228132] ata5.00: qc timeout (cmd 0xec)
Oct 5 19:08:59 PVE-Beast kernel: 1226.228134] ata5.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Oct 5 19:08:59 PVE-Beast kernel: 1226.228136] ata5.00: revalidation failed (errno=-5)
Oct 5 19:08:59 PVE-Beast kernel: 1226.228138] ata5: hard resetting link
Oct 5 19:08:59 PVE-Beast kernel: 1226.228139] ata5: nv: skipping hardreset on occupied port
Oct 5 19:08:59 PVE-Beast kernel: 1226.682041] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Oct 5 19:08:59 PVE-Beast kernel: 1226.691320] ata5.00: configured for UDMA/133
Oct 5 19:08:59 PVE-Beast kernel: 1226.691321] ata5.00: device reported invalid CHS sector 0
Oct 5 19:08:59 PVE-Beast kernel: 1226.691327] ata5: EH complete
Oct 5 19:08:59 PVE-Beast kernel: 1226.691334] sd 4:0:0:0: [sdc] START_STOP FAILED
Oct 5 19:08:59 PVE-Beast kernel: 1226.691335] sd 4:0:0:0: [sdc] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Oct 5 19:08:59 PVE-Beast kernel: 1226.691337] sd 4:0:0:0: [sdc] Sense Key : Aborted Command [current] [descriptor]
Oct 5 19:08:59 PVE-Beast kernel: 1226.691339] sd 4:0:0:0: [sdc] Add. Sense: No additional sense information
Oct 5 19:08:59 PVE-Beast kernel: 1226.691343] dpm_run_callback(): scsi_bus_suspend+0x0/0x20 returns 134217730
Oct 5 19:08:59 PVE-Beast kernel: 1226.691347] PM: Device 4:0:0:0 failed to suspend async: error 134217730
Oct 5 19:08:59 PVE-Beast kernel: 1226.691380] PM: Some devices failed to suspend
Oct 5 19:08:59 PVE-Beast kernel: 1226.691698] ohci_hcd 0000:00:0a.0: setting latency timer to 64
Oct 5 19:08:59 PVE-Beast kernel: 1226.691700] ehci_hcd 0000:00:0a.1: setting latency timer to 64
Oct 5 19:08:59 PVE-Beast kernel: 1226.691741] pci 0000:00:0e.0: setting latency timer to 64
Oct 5 19:08:59 PVE-Beast kernel: 1226.692991] serial 00:09: activated
Oct 5 19:08:59 PVE-Beast kernel: 1226.693418] parport_pc 00:0a: activated
Oct 5 19:08:59 PVE-Beast kernel: 1226.702059] snd_hda_intel 0000:00:0e.1: setting latency timer to 64
Oct 5 19:08:59 PVE-Beast kernel: 1226.702078] sata_nv 0000:00:0d.2: setting latency timer to 64
Oct 5 19:08:59 PVE-Beast kernel: 1226.702334] pata_amd 0000:00:0c.0: setting latency timer to 64
Oct 5 19:08:59 PVE-Beast kernel: 1226.703223] ata2: port disabled--ignoring
Oct 5 19:08:59 PVE-Beast kernel: 1227.039230] ata1.01: ACPI cmd ef/03:44:00:00:00:b0 (SET FEATURES) filtered out
Oct 5 19:08:59 PVE-Beast kernel: 1227.039232] ata1.01: ACPI cmd ef/03:0c:00:00:00:b0 (SET FEATURES) filtered out
Oct 5 19:08:59 PVE-Beast kernel: 1227.067399] ata1.00: ACPI cmd ef/03:44:00:00:00:a0 (SET FEATURES) filtered out
Oct 5 19:08:59 PVE-Beast kernel: 1227.067402] ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out
Oct 5 19:08:59 PVE-Beast kernel: 1227.067408] ata1: nv_mode_filter: 0x739f&0x1f39f->0x739f, BIOS=0x1f000 (0xc5c50000) ACPI=0x1f01f (30:30:0x1f)
Oct 5 19:08:59 PVE-Beast kernel: 1227.067411] ata1: nv_mode_filter: 0x739f&0x1f39f->0x739f, BIOS=0x1f000 (0xc5c50000) ACPI=0x1f01f (30:30:0x1f)
Oct 5 19:08:59 PVE-Beast kernel: 1227.098226] ata1.00: configured for UDMA/33
Oct 5 19:08:59 PVE-Beast kernel: 1227.131634] ata1.01: configured for UDMA/33
Oct 5 19:08:59 PVE-Beast kernel: 1227.149613] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Oct 5 19:08:59 PVE-Beast kernel: 1227.163633] ata4.00: ACPI cmd ef/03:46:00:00:00:a0 (SET FEATURES) filtered out
Oct 5 19:08:59 PVE-Beast kernel: 1227.163636] ata4.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
Oct 5 19:08:59 PVE-Beast kernel: 1227.182316] ata4.00: configured for UDMA/133
Oct 5 19:08:59 PVE-Beast kernel: 1227.182360] sd 3:0:0:0: [sdb] Starting disk
Oct 5 19:08:59 PVE-Beast kernel: 1227.217319] forcedeth 0000:00:11.0: irq 42 for MSI/MSI-X
Oct 5 19:08:59 PVE-Beast kernel: 1227.218747] forcedeth 0000:00:11.0: eth1: MSI enabled
Oct 5 19:08:59 PVE-Beast kernel: 1227.219069] forcedeth 0000:00:11.0: eth1: no link during initialization
Oct 5 19:08:59 PVE-Beast kernel: 1227.255149] firewire_core 0000:01:0b.0: rediscovered device fw0
Oct 5 19:08:59 PVE-Beast kernel: 1227.416468] ata6: SATA link down (SStatus 0 SControl 300)
Oct 5 19:08:59 PVE-Beast kernel: 1227.426472] ata7: SATA link down (SStatus 0 SControl 300)
Oct 5 19:08:59 PVE-Beast kernel: 1227.427510] ata8: SATA link down (SStatus 0 SControl 300)
Oct 5 19:08:59 PVE-Beast kernel: 1228.723035] ata10: SATA link down (SStatus 0 SControl 0)
Oct 5 19:08:59 PVE-Beast kernel: 1228.723095] ata9: SATA link down (SStatus 0 SControl 0)
Oct 5 19:08:59 PVE-Beast kernel: 1229.770802] forcedeth 0000:00:11.0: eth1: link up
Oct 5 19:08:59 PVE-Beast kernel: 1231.859487] PM: resume of devices complete after 5168.103 msecs
Oct 5 19:08:59 PVE-Beast kernel: 1231.859669] PM: Finishing wakeup.
I have three hard drives on this system.
One is dedicated to Windows.
One has Linux partitions for /boot, swap and /
One has a single partition for /home.
When pm-suspend executes, I hear “clicks” from the system, something spins down (probably a fan) but the power supply stays awake and after 30 seconds or so the desktop comes alive again, of sorts. Some desktop navigation is possible, but some windows are clearly broken.
Attempting to shut down or reboot the computer in this state fails - hangs with a console message:
Could not unmount /home: Device or resource busy
At that point, only a hard (push button) restart or 4 second power off seem to be effective.
I have never seen this behavior before - disks refusing to sleep.
Any thoughts?