Bug 200307
| Summary: | Read only file system after failed suspend | ||
|---|---|---|---|
| Product: | SCSI Drivers | Reporter: | Antonín Dach (dach) |
| Component: | Other | Assignee: | scsi_drivers-other |
| Status: | RESOLVED PATCH_ALREADY_AVAILABLE | ||
| Severity: | normal | CC: | dach |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 4.17.0 MANJARO flavor ( vanilla with custom config ) | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: |
screenshot of journalctl, failed suspension
inix lshw -short kernel config |
||
Created attachment 276917 [details]
inix
Created attachment 276919 [details]
lshw -short
Created attachment 276921 [details]
kernel config
This seems to be fixed on kernel 4.19, I've tested and I am able to suspend and resume flawlesly. Hope this will be the best kernel series :) exact package in manjaro repo Version : 4.19rc1.0826.g5b394b2-1 this works. I am closing this, if the issue returns I will reopen and this time bisect the commit that causes the issue of suspend. |
Created attachment 276915 [details] screenshot of journalctl, failed suspension Hi, There's a new issue with new kernel 4.17 ( is not happening on 4.16 and prior ) My AMD system with Mobo: Gigabyte model: F2A88XN-WIFI rev.3 fails to suspend. More inxi system information in attachment. I can clearly see a power down on main Power LED but system often fails to remain in suspension and wakes cca a quater second later. The woken system is completely unuseable as every drive (except ramdisk) is rendered Read only. I can't post the enitre journal as it fails to launch and is never written. I was lucky enough to have tail on journal once so I took and photo of my screen. ( please do not hate I had not idea how export the journal as no command would run on READONLY FS) IOMMU is disabled. Not using RAID. $ lsscsi [0:0:0:0] disk ATA INTEL SSDSC2BW24 RG21 /dev/sda [1:0:0:0] disk ATA WDC WD5003AZEX-0 1A01 /dev/sdb