Comment 123 for bug 1063354

[Problem probably solved]

I changed my fstab and removed the "defaults"-entry:
Probably this was the problem and the "defaults"-entry puts some mount options, that interfere with the ssd.

fatab-NEW: /dev/mapper/vg--myvg-root / ext4 noatime,errors=remount-ro 0 1
fstab-OLD: /dev/mapper/vg--myvg-root / ext4 defaults,noatime,errors=remount-ro 0 1

I left the libata option in modprobe and kernel boot options:
> cat /etc/modprobe.d/options
options libata noacpi=1

> cat /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash libata.force=noncq libata.noacpi=1"

Since two days the system is running without any filesystem-freezes.

I am attaching an ubuntu bug-report which can probably help to solve and analyse the problem.
The system is up to date as time of writing and all necessary updates are applied.

-------------------------------------------------------------------------------

I have to add, that I am running a newer version of lvm2 with gives me the option of using TRIM:
ii lvm2 2.02.95-4ubuntu1.1~p Linux Logical Volume Manager
All necessary entries in crytptab and lvm.conf are done and trim is working (on demand).

> dmesg | grep libata
[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.11.0-15-generic root=/dev/mapper/vg--madagaskar-root ro quiet splash libata.force=noncq libata.noacpi=1
[ 0.517478] libata version 3.00 loaded.

> dmesg | grep ata1
[ 1.400125] ata1: SATA max UDMA/133 abar m2048@0xf2627000 port 0xf2627100 irq 53
[ 1.717874] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1.719776] ata1.00: FORCE: horkage modified (noncq)
[ 1.719843] ata1.00: ATA-9: Samsung SSD 840 EVO 500GB, EXT0BB0Q, max UDMA/133
[ 1.719848] ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (not used)
[ 1.720159] ata1.00: configured for UDMA/133
[12726.396872] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[12726.398974] ata1.00: configured for UDMA/133
[54682.379955] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[54682.382006] ata1.00: configured for UDMA/133