Comparing your two dmesg logs, I can see that the touchscreen is identified in the good dmesg, but nothing in the bad one. Here's the message from the good one:
[ 3.296644] input: SYNA7500:00 06CB:3AF0 as /devices/pci0000:00/INT33C3:00/i2c-9/i2c-SYNA7500:00/0018:06CB:3AF0.0002/input/input10
[ 3.298646] hid-multitouch 0018:06CB:3AF0.0002: input,hidraw0: I2C HID v1.00 Device [SYNA7500:00 06CB:3AF0] on i2c-SYNA7500:00
I see one touchscreen specific change from 4.12.0-13 and 4.13.0-10. I disabled this option and reverted commit 78bcac7b2ae1e4f in this test kernel:
Comparing your two dmesg logs, I can see that the touchscreen is identified in the good dmesg, but nothing in the bad one. Here's the message from the good one: pci0000: 00/INT33C3: 00/i2c- 9/i2c-SYNA7500: 00/0018: 06CB:3AF0. 0002/input/ input10 3AF0.0002: input,hidraw0: I2C HID v1.00 Device [SYNA7500:00 06CB:3AF0] on i2c-SYNA7500:00
[ 3.296644] input: SYNA7500:00 06CB:3AF0 as /devices/
[ 3.298646] hid-multitouch 0018:06CB:
I see one touchscreen specific change from 4.12.0-13 and 4.13.0-10. I disabled this option and reverted commit 78bcac7b2ae1e4f in this test kernel:
http:// kernel. ubuntu. com/~jsalisbury /lp1745342
Can you give this kernel a try? If it still has the bug, we can bisect between 4.12.0-13 and 4.13.0-10 and see if we can narrow it down that way.