This bit in your dmesg looks interesting:
[ 34.760459] i2c-adapter i2c-0: unable to read EDID block. [ 34.816202] i915 0000:00:02.0: VGA-1: no EDID data [ 34.920459] i2c-adapter i2c-0: unable to read EDID block. [ 34.976117] i915 0000:00:02.0: VGA-1: no EDID data [ 35.178176] ppdev: user-space parallel port driver [ 35.333308] i2c-adapter i2c-0: unable to read EDID block. [ 35.388108] i915 0000:00:02.0: VGA-1: no EDID data [ 35.492590] i2c-adapter i2c-0: unable to read EDID block. [ 35.548108] i915 0000:00:02.0: VGA-1: no EDID data
Possibly this is the same kernel bug that caused bug #394492, esp. since you were able to fix it by downrevving the kernel.
This bit in your dmesg looks interesting:
[ 34.760459] i2c-adapter i2c-0: unable to read EDID block.
[ 34.816202] i915 0000:00:02.0: VGA-1: no EDID data
[ 34.920459] i2c-adapter i2c-0: unable to read EDID block.
[ 34.976117] i915 0000:00:02.0: VGA-1: no EDID data
[ 35.178176] ppdev: user-space parallel port driver
[ 35.333308] i2c-adapter i2c-0: unable to read EDID block.
[ 35.388108] i915 0000:00:02.0: VGA-1: no EDID data
[ 35.492590] i2c-adapter i2c-0: unable to read EDID block.
[ 35.548108] i915 0000:00:02.0: VGA-1: no EDID data
Possibly this is the same kernel bug that caused bug #394492, esp. since you were able to fix it by downrevving the kernel.