Opened 2 years ago

Closed 2 years ago

#17841 closed bug (fixed)

PS2 Touchpad Disconnects

Reported by: navjack27 Owned by: waddlesplash
Priority: normal Milestone: R1/beta4
Component: Drivers/Input/PS2/Mouse Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description

On my Gateway laptop model MS2274 I have Haiku's nighty installed. Sorry for being vague but somewhere between hrev56272 and hrev56297 a change was done that causes the PS2 touchpad to disconnect after being touched. I'll attach the current full syslogs. If you need me to I can go back to a known working version and then get the syslogs from that.

Attachments (3)

new_broken_syslogs.7z (20.5 KB ) - added by navjack27 2 years ago.
syslog-56291 (165.3 KB ) - added by navjack27 2 years ago.
syslog from working revsion 5621
syslog-56295 (165.6 KB ) - added by navjack27 2 years ago.
syslog from broken revision 56295

Download all attachments as: .zip

Change History (11)

by navjack27, 2 years ago

Attachment: new_broken_syslogs.7z added

comment:1 by pulkomandy, 2 years ago

I suspected hrev56268 (PS2 keyboard reset changes) but that's just before the range you listed, so, if that range is correct, that's not it.

My next guess, but that is really a guess, is that hrev56274 (kernel/scheduler: Reset the invoke_scheduler flag on reschedule) allows for some race condition with the interrupts in the PS2 code somehow?

comment:2 by pulkomandy, 2 years ago

Oh and there's also hrev56293 which changed the touchpad code quite a lot, so that's more likely to be related.

by navjack27, 2 years ago

Attachment: syslog-56291 added

syslog from working revsion 5621

by navjack27, 2 years ago

Attachment: syslog-56295 added

syslog from broken revision 56295

comment:3 by navjack27, 2 years ago

i attached two new files. i used pkgman to sync to previous releases and found that 56295 is where the mouse has the disconnect bug introduced.

Version 0, edited 2 years ago by navjack27 (next)

comment:4 by pulkomandy, 2 years ago

Ok so in the new log we can see this:

2570	KERN: Mouse device exiting, Operation timed out

Indeed it seems something did not work as expected with the move of movementmake to userspace in hrev56293. However I don't really see how this could happen by looking at the code?

comment:5 by waddlesplash, 2 years ago

Please retest after hrev56301.

comment:6 by waddlesplash, 2 years ago

Owner: set to waddlesplash
Status: newin-progress

in reply to:  6 comment:7 by navjack27, 2 years ago

Replying to waddlesplash:

hrev56301 works! No mouse issues. Awesome! Thank you.

comment:8 by pulkomandy, 2 years ago

Milestone: UnscheduledR1/beta4
Resolution: fixed
Status: in-progressclosed

Thanks for reporting and testing :)

Note: See TracTickets for help on using tickets.