-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
В Fri, 24 Jan 2014 22:08:33 +0100 (CET)
"Carlos E. R."
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
I had been transferring some files to my Android phone. I had umounted the folders, but left the phone connected and charging.
When I attempted to hibernate the machine, it refused. It went through the motions, then aborted. There was no message anywhere saying why hibernation aborted.
There was no hint in "/var/log/pm-suspend.log".
I suddenly thought of unplugging the cell phone, and hibernation worked.
I have now been looking at /var/log/messages, and noticed this (the "<=====" below):
<0.6> 2014-01-24 19:10:25 Telcontar kernel - - - [ 3420.249019] sd 12:0:0:1: [sdg] <0.4> 2014-01-24 19:10:25 Telcontar kernel - - - [ 3420.249020] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE <0.6> 2014-01-24 19:10:25 Telcontar kernel - - - [ 3420.249021] sd 12:0:0:1: [sdg] <0.4> 2014-01-24 19:10:25 Telcontar kernel - - - [ 3420.249022] Sense Key : Not Ready [current] <0.6> 2014-01-24 19:10:25 Telcontar kernel - - - [ 3420.249023] sd 12:0:0:1: [sdg] <0.4> 2014-01-24 19:10:25 Telcontar kernel - - - [ 3420.249025] Add. Sense: Medium not present <0.3> 2014-01-24 19:10:25 Telcontar kernel - - - [ 3420.249032] dpm_run_callback(): scsi_bus_freeze+0x0/0x20 returns -5 <===== <0.3> 2014-01-24 19:10:25 Telcontar kernel - - - [ 3420.249033] PM: Device 12:0:0:1 failed to freeze async: error -5
sdg and sdf were the devices assigned to the phone. Was the phone doing something to impede hibernation, is this to be expected, or is this a bug?
I guess it depends on what driver tried to do at this point. "Medium not present" itself is not error, but I'm not sure how and why it would be returned here. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlLjWxIACgkQR6LMutpd94xoAgCfSYqhumyohn9pimWDUNbJ+JTn mAkAn2SCyB89p52bk04DjCieF8SFza2+ =cITb -----END PGP SIGNATURE-----