Opened 4 months ago

Last modified 2 months ago

#18946 new bug

TrackPoint and TouchPad unreliable on Lenovo T460

Reported by: jbmorley Owned by: PreetpalKaur
Priority: normal Milestone: Unscheduled
Component: Drivers/Input/PS2 Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description

I've been seeing inconsistent TrackPoint and TouchPad behavior with my Lenovo T460; sometimes they work perfectly, sometimes I'm seeing what feels like incredibly low sample rates, and sometimes they don't work at all.

I seem to be seeing both the TrackPoint and TouchPad drop into the following three states, independent of each other, following booting:

  • device doesn't work at all
  • device seems to work but very unreliably and the cursor jumps with what feels like a sample rate of ~1s; this leads to some move events being missed entirely and leaves input almost unusable
  • device works just fine!

The TrackPoint typically doesn't work and surprises me when it does. It probably works <10% of the time. The TouchPad seems to be more reliable, probably working 25% of the time on a fresh boot, and maybe 80% of the time after a warm restart (this makes me wonder if it's related to https://dev.haiku-os.org/ticket/14236). Feels a lot like we're not successfully initializing the hardware correctly.

I can imagine these might be completely different issues, but I thought I'd raise them together and we could split them out if necessary.

I'm pretty new to this reporting process with Haiku, so please let me know what information I can capture and what I can do to help.

Attachments (8)

listdev_working_touchpad_warm_reboot.txt (3.0 KB ) - added by jbmorley 4 months ago.
listimage_drivers_working_touchpad_warm_reboot.txt (1.9 KB ) - added by jbmorley 4 months ago.
listusb_working_touchpad_warm_reboot.txt (32.8 KB ) - added by jbmorley 4 months ago.
syslog_working_touchpad_warm_reboot.txt (99.0 KB ) - added by jbmorley 4 months ago.
listdev_not_working.txt (3.0 KB ) - added by jbmorley 4 months ago.
listimage_drivers_not_working.txt (1.9 KB ) - added by jbmorley 4 months ago.
listusb_not_working.txt (32.8 KB ) - added by jbmorley 4 months ago.
syslog_not_working.txt (350.7 KB ) - added by jbmorley 4 months ago.

Download all attachments as: .zip

Change History (15)

comment:1 by jbmorley, 4 months ago

I've added logs described in https://www.haiku-os.org/docs/welcome/en/bugreports.html. 'usb_hid_report' doesn't seem to be available on my path so that output is missing.

There are two sets of logs:

  • '_working_touchpad_warm_report' logs from a warm reboot where the TouchPad is working but the TrackPoint is not working
  • '_not_working' logs from a cold boot where neither the TouchPad or TrackPoint is working
Version 0, edited 4 months ago by jbmorley (next)

by jbmorley, 4 months ago

Attachment: listdev_not_working.txt added

by jbmorley, 4 months ago

by jbmorley, 4 months ago

Attachment: listusb_not_working.txt added

by jbmorley, 4 months ago

Attachment: syslog_not_working.txt added

comment:2 by waddlesplash, 4 months ago

Component: Drivers/InputDrivers/Input/PS2

There are no USB HID reports because your TrackPoint and Touchpad are both PS/2.

The last boot in the "non-working" has these two lines (not next to each other, but in this order):

KERN: ps2: devfs_publish_device input/touchpad/ps2/synaptics_0, status = 0x00000000
KERN: ps2: devfs_publish_device input/keyboard/at/0, status = 0x00000000
KERN: ps2: devfs_publish_device input/mouse/ps2/ibm_trackpoint_0, status = 0x00000000
KERN: ps2: keyboard found

It seems odd that the TrackPoint isn't working on this boot but the touchpad is (even if in "low-resolution" state), I wonder what's the difference?

In the "working warm reboot" syslog, we have this:

KERN: ps2: devfs_publish_device input/touchpad/ps2/synaptics_0, status = 0x00000000
KERN: ps2: devfs_publish_device input/keyboard/at/0, status = 0x00000000
KERN: ps2: keyboard found
KERN: ps2_dev: reset failed: I/O error
KERN: ps2: devfs_publish_device input/mouse/ps2/synaptics_passthrough, status = 0xffffffff

I wonder what's different for us to get the "synaptics passthrough" device? Perhaps related to the trackpoint being missing?

comment:3 by jbmorley, 4 months ago

Thanks for digging into this!

Just to clarify—the TrackPoint isn’t functioning in either of the boots I captured logs for. I’ll try to capture a log next time I see it working but it does so with a lower frequency than the TouchPad.

In case it’s relevant, I noticed yesterday that the TouchPad started working on its own accord some time into a cold boot (tens of minutes). That doesn’t happen consistently though.

Please let me know if there’s anything I can do to help diagnose or investigate further.

comment:4 by waddlesplash, 4 months ago

Well, I'm not really an expert in our PS/2 stack, and I don't have any immediate plans to dig into it; I just wanted to take a first pass at triaging the issue. The information you've provided so far is certainly helpful, though.

comment:5 by waddlesplash, 2 months ago

Please retest after hrev58155.

comment:6 by jbmorley, 2 months ago

Testing on hrev58157, the TouchPad seems to come up reliably and work great! The hardware mouse cursor buttons seem to be reliable too, but the TrackPoint still seems to work very infrequently---I saw it work once following a warm reboot after updating to href58155, but haven't seen it work since.

Thank you! This is all very exciting. Let me know what I can do to help further.

comment:7 by jbmorley, 2 months ago

Unfortunatley, I think I might have spoken too soon. I just rebooted and saw the earlier incredibly low sample rate / laggy behaviour on the TouchPad, and neither the TrackPoint or hardware mouse buttons were working.

Note: See TracTickets for help on using tickets.