NetBSD Problem Report #55024
From www@netbsd.org Wed Feb 26 18:11:32 2020
Return-Path: <www@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
by mollari.NetBSD.org (Postfix) with ESMTPS id B4B711A9213
for <gnats-bugs@gnats.NetBSD.org>; Wed, 26 Feb 2020 18:11:32 +0000 (UTC)
Message-Id: <20200226181131.DFF121A9217@mollari.NetBSD.org>
Date: Wed, 26 Feb 2020 18:11:31 +0000 (UTC)
From: rcbixler@nyx.net
Reply-To: rcbixler@nyx.net
To: gnats-bugs@NetBSD.org
Subject: track pad, mouse buttons non-responsive when first starting X
X-Send-Pr-Version: www-1.0
>Number: 55024
>Category: port-amd64
>Synopsis: track pad, mouse buttons non-responsive when first starting X
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: port-amd64-maintainer
>State: closed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed Feb 26 18:15:00 +0000 2020
>Closed-Date: Thu Apr 30 10:59:13 +0000 2020
>Last-Modified: Thu Apr 30 10:59:13 +0000 2020
>Originator: Roy Bixler
>Release: NetBSD 9
>Organization:
>Environment:
NetBSD localhost 9.0_STABLE NetBSD 9.0_STABLE (GENERIC) #0: Tue Feb 25 18:40:44 UTC 2020 mkrepro@mkrepro.NetBSD.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64
>Description:
After first starting X, the track pad does not move the cursor. Likewise, the mouse buttons don't work.
I see some messages like this in dmesg output:
[ 44.092818] pms_input: unusual delay (0.040036 s), scheduling reset
[ 46.064589] pms_input: unusual delay (0.040036 s), scheduling reset
[ 46.965398] pms_input: unusual delay (0.040036 s), scheduling reset
The system is a Lenovo Thinkpad Carbon X1 (same as in PR 55023).
>How-To-Repeat:
Start X using "startx", try to use the trackpad to move the cursor or press the mouse buttons. I will occasionally see a little cursor movement, but it generally doesn't work.
>Fix:
My workaround is to move the cursor using the red mouse pad in the middle of the keyboard. Once I do that, then the track pad and other mouse buttons work normally.
>Release-Note:
>Audit-Trail:
From: Roy Bixler <rcbixler@nyx.net>
To: gnats-bugs@netbsd.org
Cc:
Subject: Re: port-amd64/55024: track pad, mouse buttons non-responsive when
first starting X
Date: Wed, 26 Feb 2020 11:40:28 -0700
I forgot to mention that this problem also didn't happen in NetBSD-8
or 8.1.
--
Roy Bixler <rcbixler@nyx.net>
"The fundamental principle of science, the definition almost, is this: the
sole test of the validity of any idea is experiment."
-- Richard P. Feynman
From: Roy Bixler <rcbixler@nyx.net>
To: gnats-bugs@netbsd.org
Cc:
Subject: Re: port-amd64/55024: track pad, mouse buttons non-responsive when
first starting X
Date: Wed, 26 Feb 2020 11:58:24 -0700
Also, some "dmesg" output showing the device:
[ 1.049240] pckbd0 at pckbc1 (kbd slot)
[ 1.049240] pckbc1: using irq 1 for kbd slot
[ 1.049240] wskbd0 at pckbd0: console keyboard
[ 1.049240] pms0 at pckbc1 (aux slot)
[ 1.049240] pms0: Synaptics touchpad version 8.1
[ 1.049240] pms0: Extended W mode, Passthrough, Palm detect, One button click pad, Multi-finger Report, Multi-finger
[ 1.049240] pckbc1: using irq 12 for aux slot
[ 1.049240] wsmouse0 at pms0 mux 0
--
Roy Bixler <rcbixler@nyx.net>
"The fundamental principle of science, the definition almost, is this: the
sole test of the validity of any idea is experiment."
-- Richard P. Feynman
State-Changed-From-To: open->feedback
State-Changed-By: maya@NetBSD.org
State-Changed-When: Wed, 26 Feb 2020 20:09:44 +0000
State-Changed-Why:
Does this commit help?
http://mail-index.netbsd.org/source-changes/2020/02/25/msg114465.html
From: Roy Bixler <rcbixler@nyx.net>
To: gnats-bugs@netbsd.org
Cc:
Subject: Re: port-amd64/55024 (track pad, mouse buttons non-responsive when
first starting X)
Date: Thu, 27 Feb 2020 12:51:53 -0700
On Wed, Feb 26, 2020 at 08:09:45PM +0000, maya@NetBSD.org wrote:
> Synopsis: track pad, mouse buttons non-responsive when first starting X
>
> State-Changed-From-To: open->feedback
> State-Changed-By: maya@NetBSD.org
> State-Changed-When: Wed, 26 Feb 2020 20:09:44 +0000
> State-Changed-Why:
> Does this commit help?
> http://mail-index.netbsd.org/source-changes/2020/02/25/msg114465.html
No, sorry, it didn't change the symptom.
--
Roy Bixler <rcbixler@nyx.net>
"The fundamental principle of science, the definition almost, is this: the
sole test of the validity of any idea is experiment."
-- Richard P. Feynman
From: Ryo ONODERA <ryo@tetera.org>
To: gnats-bugs@netbsd.org, rcbixler@nyx.net
Cc:
Subject: Re: port-amd64/55024 (track pad, mouse buttons non-responsive when first starting X)
Date: Fri, 28 Feb 2020 12:05:55 +0900
Roy Bixler <rcbixler@nyx.net> writes:
> > State-Changed-From-To: open->feedback
> > State-Changed-By: maya@NetBSD.org
> > State-Changed-When: Wed, 26 Feb 2020 20:09:44 +0000
> > State-Changed-Why:
> > Does this commit help?
> > http://mail-index.netbsd.org/source-changes/2020/02/25/msg114465.html
>
> No, sorry, it didn't change the symptom.
That commit should not fix the problem for the device with extended W
mode like yours.
How about the output of boot with "-x"?
When "boot -x", some aprint_debug()s will show some useful messages.
My older synaptics touchpad in Panasonic CF-Y8, which has no extended
W mode, loses absolute mode setting and return to relative mode.
So I get the following messages from kernel
pms0: pms_synaptics_input: dropped in relative mode, reset
pms0: pms_synaptics_input: 0x9a out of sync
pms0: pms_synaptics_input: 0x09 out of sync
(snip many similar lines including delay messages)
And could you show me the PNP ID of your touchpad?
It will be found like as follows:
pckbc1 at acpi0 (PS2K, HPQ8001) (kbd port): io 0x60,0x64 irq 1
pckbc2 at acpi0 (PS2M, SYN326A) (aux port): irq 12
In this case, I want to know SYN326A as the ID.
--
Ryo ONODERA // ryo@tetera.org
PGP fingerprint = 82A2 DC91 76E0 A10A 8ABB FD1B F404 27FA C7D1 15F3
From: Roy Bixler <rcbixler@nyx.net>
To: gnats-bugs@netbsd.org
Cc: port-amd64-maintainer@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org
Subject: Re: port-amd64/55024 (track pad, mouse buttons non-responsive when
first starting X)
Date: Fri, 28 Feb 2020 08:17:58 -0700
On Fri, Feb 28, 2020 at 03:10:03AM +0000, Ryo ONODERA wrote:
> How about the output of boot with "-x"?
> When "boot -x", some aprint_debug()s will show some useful messages.
> My older synaptics touchpad in Panasonic CF-Y8, which has no extended
> W mode, loses absolute mode setting and return to relative mode.
> So I get the following messages from kernel
>
> pms0: pms_synaptics_input: dropped in relative mode, reset
> pms0: pms_synaptics_input: 0x9a out of sync
> pms0: pms_synaptics_input: 0x09 out of sync
> (snip many similar lines including delay messages)
Agreed - I see the following:
Feb 28 15:01:01 localhost /netbsd: [ 37.8457202] pms_input: unusual delay (0.250204 s), scheduling reset
Feb 28 15:01:01 localhost /netbsd: [ 40.0575250] pms_input: unusual delay (0.040033 s), scheduling reset
Feb 28 15:01:01 localhost /netbsd: [ 40.9582601] pms_input: unusual delay (0.040033 s), scheduling reset
Feb 28 15:01:01 localhost /netbsd: [ 41.8589951] pms_input: unusual delay (0.040033 s), scheduling reset
Feb 28 15:01:01 localhost /netbsd: [ 43.4202692] pms_input: unusual delay (0.050041 s), scheduling reset
Feb 28 15:01:30 localhost /netbsd: [ 41.9594388] pms0: reset 0 0xaa 0x00
Feb 28 15:01:30 localhost /netbsd: [ 42.4395924] pms0: reset 0 0xaa 0x00
Feb 28 15:01:30 localhost /netbsd: [ 41.9594388] pms0: reset 0 0xaa 0x00
Feb 28 15:01:34 localhost /netbsd: [ 44.0007954] pms0: pms_input: 0x18 out of sync
Feb 28 15:01:34 localhost /netbsd: [ 44.0007954] pms0: pms_input: 0xff out of sync
Feb 28 15:01:34 localhost /netbsd: [ 44.0007954] pms0: pms_input: 0x00 out of sync
Feb 28 15:01:34 localhost /netbsd: [ 44.0208121] pms0: pms_input: 0x08 out of sync
Feb 28 15:01:34 localhost /netbsd: [ 44.0208121] pms0: pms_input: 0x00 out of sync
Feb 28 15:01:34 localhost /netbsd: [ 44.0308205] pms0: pms_input: 0x01 out of sync
Feb 28 15:01:34 localhost /netbsd: [ 44.0308205] pms0: pms_input: dropped in relative mode, reset
Feb 28 15:01:34 localhost /netbsd: [ 44.7891564] pms0: reset 0 0xaa 0x00
Feb 28 15:01:34 localhost /netbsd: [ 44.9816065] pms0: pms_input: unusual delay (0.040033 s), scheduling reset
Feb 28 15:01:34 localhost /netbsd: [ 44.9816065] pms_input: unusual delay (0.040033 s), scheduling reset
Feb 28 15:01:34 localhost /netbsd: [ 45.7360729] pms0: reset 0 0xaa 0x00
Feb 28 15:01:34 localhost /netbsd: [ 45.8823515] pms0: pms_input: unusual delay (0.040033 s), scheduling reset
Feb 28 15:01:34 localhost /netbsd: [ 45.8823515] pms_input: unusual delay (0.040033 s), scheduling reset
Feb 28 15:01:34 localhost /netbsd: [ 46.6340642] pms0: reset 0 0xaa 0x00
Feb 28 15:01:35 localhost /netbsd: [ 46.9532370] pms0: pms_input: 0x18 out of sync
Feb 28 15:01:35 localhost /netbsd: [ 46.9632455] pms0: pms_input: 0xff out of sync
Feb 28 15:01:35 localhost /netbsd: [ 46.9632455] pms0: pms_input: 0x05 out of sync
Feb 28 15:01:35 localhost /netbsd: [ 46.9632455] pms0: pms_input: 0x08 out of sync
Feb 28 15:01:35 localhost /netbsd: [ 46.9732538] pms0: pms_input: 0x00 out of sync
Feb 28 15:01:35 localhost /netbsd: [ 46.9732538] pms0: pms_input: 0x03 out of sync
Feb 28 15:01:35 localhost /netbsd: [ 46.9732538] pms0: pms_input: dropped in relative mode, reset
Feb 28 15:01:35 localhost /netbsd: [ 47.7345007] pms0: reset 0 0xaa 0x00
> And could you show me the PNP ID of your touchpad?
> It will be found like as follows:
>
> pckbc1 at acpi0 (PS2K, HPQ8001) (kbd port): io 0x60,0x64 irq 1
> pckbc2 at acpi0 (PS2M, SYN326A) (aux port): irq 12
>
> In this case, I want to know SYN326A as the ID.
I see the following:
Feb 28 15:03:22 localhost /netbsd: [ 1.0474956] pckbc1 at acpi0 (KBD, LEN0071) (kbd port): io 0x60,0x64 irq 1
Feb 28 15:03:22 localhost /netbsd: [ 1.0474956] pckbc2 at acpi0 (MOU, LEN0030) (aux port): irq 12
--
Roy Bixler <rcbixler@nyx.net>
"The fundamental principle of science, the definition almost, is this: the
sole test of the validity of any idea is experiment."
-- Richard P. Feynman
State-Changed-From-To: feedback->open
State-Changed-By: maya@NetBSD.org
State-Changed-When: Fri, 24 Apr 2020 13:48:35 +0000
State-Changed-Why:
feedback provided
State-Changed-From-To: open->feedback
State-Changed-By: jmcneill@NetBSD.org
State-Changed-When: Tue, 28 Apr 2020 23:09:58 +0000
State-Changed-Why:
I had this problem on my X260 and fixed it with synaptics.c r1.66, can you try it?
From: Roy Bixler <rcbixler@nyx.net>
To: gnats-bugs@netbsd.org
Cc: port-amd64-maintainer@netbsd.org, netbsd-bugs@netbsd.org,
gnats-admin@netbsd.org, jmcneill@NetBSD.org
Subject: Re: port-amd64/55024 (track pad, mouse buttons non-responsive when
first starting X)
Date: Wed, 29 Apr 2020 17:35:47 -0600
On Tue, Apr 28, 2020 at 11:09:58PM +0000, jmcneill@NetBSD.org wrote:
> Synopsis: track pad, mouse buttons non-responsive when first starting X
>
> State-Changed-From-To: open->feedback
> State-Changed-By: jmcneill@NetBSD.org
> State-Changed-When: Tue, 28 Apr 2020 23:09:58 +0000
> State-Changed-Why:
> I had this problem on my X260 and fixed it with synaptics.c r1.66, can you try it?
I applied the patch to 9-STABLE and that definitely helped.
--
Roy Bixler <rcbixler@nyx.net>
"The fundamental principle of science, the definition almost, is this: the
sole test of the validity of any idea is experiment."
-- Richard P. Feynman
State-Changed-From-To: feedback->closed
State-Changed-By: jmcneill@NetBSD.org
State-Changed-When: Thu, 30 Apr 2020 10:59:13 +0000
State-Changed-Why:
Fix pulled up to netbsd-9, thanks for the report!
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.46 2020/01/03 16:35:01 leot Exp $
$NetBSD: gnats_config.sh,v 1.9 2014/08/02 14:16:04 spz Exp $
Copyright © 1994-2020
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.