Comment 122 for bug 1063354

Revision history for this message
Axel Pospischil (apos) wrote : Re: Sudden Read-Only Filesystems

Unfortunetely with the settings from above i was not lucky this morning. When I turned on the W510 notebook (#3.) it stuck like before. I really think, this is system specific for this laptop, because the other computers with itdentical software are running flawlessly ... 24/7 (via suspend / resume).

I also have to add, that all disks run on lvm based cryptsetup!

> cat /var/log/syslog.1 | grep ata1 | cut -d "[" -f2

    1.419360] ata1: SATA max UDMA/133 abar m2048@0xf2627000 port 0xf2627100 irq 53
    1.737774] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    1.741004] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
    1.741014] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
    1.741020] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
    1.741298] ata1.00: ATA-9: Samsung SSD 840 EVO 500GB, EXT0BB0Q, max UDMA/133
    1.741303] ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
    1.742899] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
    1.742907] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered ou
    1.742913] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
    1.743209] ata1.00: configured for UDMA/133

I will investigate further