Comment 13 for bug 1641919

In case anyone's interested, tried again after a recent Kernel Update (Linux version 4.8.0-37-generic (buildd@lcy01-17) (gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) ) #39-Ubuntu SMP Thu Jan 26 02:27:07 UTC 2017 (Ubuntu 4.8.0-37.39-generic 4.8.16))

But same story on tty1 (This is not a log file, typed this from a photo I took, the [...] stands for a time stamp)

melvinh@MH4Linux:~$ sudo pm-hibernate
[sudo] Passwort für melvinh
---screen goes black, system does something - no HDD activity, screen turns on again, errors appear as follows---
[...] do_IRQ: 1.226 No irq handler for vector
[...] do_IRQ: 3.178 No irq handler for vector
[...] do_IRQ: 3.178 No irq handler for vector
[...] ata2.00: revalidation failed (errno=-5)
[...] ata1.00: revalidation failed (errno=-5)
[...] do_IRQ: 3.178 No irq handler for vector
[...] do_IRQ: 3.178 No irq handler for vector
[...] do_IRQ: 3.178 No irq handler for vector
[...] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR* [CRTC:26:pipe A] flip_done timed out
[...] ata2.00: revalidation failed (errno=-5)
[...] ata1.00: revalidation failed (errno=-5)
[...] do_IRQ: 3.178 No irq handler for vector
[...] do_IRQ: 3.178 No irq handler for vector
[...] do_IRQ: 3.178 No irq handler for vector
[...] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR* [CRTC:26:pipe A] flip_done timed out
[...] ata2.00: revalidation failed (errno=-5)
[...] ata1.00: revalidation failed (errno=-5)
[...] do_IRQ: 3.178 No irq handler for vector
[...] blk_update_request: I/O error, dev sda, sector 939400954
[...] blk_update_request: I/O error, dev sda, sector 936002719
[...] Buffer I/O error on device sda6, logical block 4818437
melvinh@MH4Linux:~$ [...] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR* [CRTC:26:pipe A] flip_done timed out
[...] EXT4-fs (sda6): Delayed block allocation failed for inode 788068 at logical offset 0 with max blocks 1 with error 5
[...] EXT4-fs (sda6): This should not happen!! Data will be lost
[...]
[...] blk_update_request: I/O error, dev sda, sector 926883199
[...] blk_update_request: I/O error, dev sda, sector 918700167
[...] Aborting journal on device sda6-8
[...] blk_update_request: I/O error, dev sda, sector 918697087
[...] blk_update_request: I/O error, dev sda, sector 918697087
[...] Buffer I/O error on dev sda6, logical block 2655233, lost sync page write
[...] JBD2: Error -5 detected when updating journal superblock for sda6-8
[...] blk_update_request: I/O error, dev sda, sector 897455223
[...] blk_update_request: I/O error, dev sda, sector 897455223
[...] Buffer I/O error on dev sda6, logical block 0, lost sync page write
[...] EXT4-fs error (device sda6): ext4_journal_check_start:56: Detected aborted journal
[...] EXT4-fs (sda6): Remounting filesystem readonly
[...] EXT4-fs (sda6): previous I/O error to superblock detected
[...] blk_update_request: I/O error, dev sda, sector 897455223
[...] blk_update_request: I/O error, dev sda, sector 897455223
[...] Buffer I/O error on dev sda6, logical block 0, lost sync page write