Comment # 54 on bug 1205410 from Takashi Iwai

I meant not the "section" but just the all output from dmesg.
That is, simply run
  dmesg > dmesg.out
and attach the dmesg.out file to Bugzilla.

For debugging such hardware issues, you need to see the full picture, not only
the focused on.  Especially a case like this is involved with different layers
(the input device is enabled via ACPI, then transport via designware i2c bus
over kernel i2c layer, kernel HID layer, kernel HID touchpad driver, then
kernel input driver, finally comes to user-space, then interpreted by libinput,
and reaches to the desktop environment at last -- maybe there are something
middle I forgot, too).