Hide Forgot
Description of problem: Allowing f20 / xfce, on a T530, to lie idle long enough to auto-suspend, then hitting the power button to resume - user home directory writes (eg. "touch foo" are denied with "read-only filesystem". I suspect a fs, scsi or disk error on an inode (from previous peeks at logs) results in a deliberate transition to RO. Version-Release number of selected component (if applicable): 3.11.7-300.fc20.x86_64 How reproducible: >80%. Both mains & battery operation. Note that deliberate suspend (or hibernate) from the xfce menu does *not* seem to induce it. Steps to Reproduce: 1. Boot system & log in 2. Leave idle until suspend happens, then resume 3. Attempt a file write Actual results: Write to filesystem fails, EROFS. "mount" still shows RW. Expected results: Write operates normally. Additional info: Have configured for kdump & taken one in the EROFS state. At 105MB I can't attach here, but I'll keep it around in case of interest.
Can also duplicate on 3.11.6-302.fc20.x86_64 . From this one I photo'd dmesg after resume; it shows an I/O error on sdb, which happens to be an inode: (manually retyped) PM: Finishing wakeup Restarting tasks ... done. usb 2-1.6: USB disconnect, device number 3 video LNXVIDEO:00: Restoring backlight state sd 6:0:0:0: [sdb] Unhandled error code sd 6:0:0:0: [sdb] Result: hostbyte=DID_NO_CONNECT droverbyte=DRIVER_OK sd 6:0:0:0: [sdb] CDB: Write(10): 2a 00 03 53 d0 00 00 00 08 00 end_request: I/O error, dev sdb, sector 55824384
Created attachment 821330 [details] screen photo of dmesg, showing disk error
Still present in 3.12.5-302.fc20.x86_64
Also on 3.12.8-300.fc20.x86_64 - this time a deliberate suspend-to-ram.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.13.4-200.fc20. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug has been in a needinfo state for several weeks and is being closed with insufficient data due to inactivity. If this is still an issue with Fedora 20, please feel free to reopen the bug and provide the additional information requested.
Still present on 3.13.6-200.fc20.x86_64, triggered by deliberate suspend.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.14.4-200.fc20. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
Still present on 3.14.4-200.fc20.x86_64
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.17.2-200.fc20. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21. If you experience different issues, please open a new bug report for those.
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.