Comment 13 for bug 1762468

Some good and bad news: I have been testing this in a running Gnome 3 environment. I decided to start testing on console. On console, all kernels seem to fail using crypt swap. This suggests to me that failure must depend on current memory usage, dirty ratio, or some such runtime condition.

However, the good news, I have kernel messages on console. I'm attaching a screen shot, since none of them get written to syslog. A typical message is: task dm_write:xxx blocked for more than 120 seconds

There are no problems when not using dm_crypt for swap, i.e. 'normal' swap.