Re: kern/57400

[David Daniels <dave_daniels%argonet.co.uk@localhost>]

The following reply was made to PR kern/57400; it has been noted by GNATS.

From: David Daniels <dave_daniels%argonet.co.uk@localhost>
To: gnat-bugs <gnats-bugs%NetBSD.org@localhost>
Cc: 
Subject: Re: kern/57400
Date: Fri, 19 May 2023 19:11:34 +0100

 I have managed to compile a kernel with the DIAGNOSTIC option by
 adding the line 'option DIAGNOSTIC' to the configuration file for
 the kernel (RPI2). I assume this is how you do it. I have carried
 out some tests with this kernel and now get the message:
 
 wskbd_input: evar->q=NULL
 
 What I did was:
 
 1) Boot with the diagnostic kernel
 2) Log on and start a Xwindows session
 3) Switch to a different machine on the KVM
 4) Wait for a minute or so
 5) Switch back to the NetBSD machine
 6) Press Ctrl-Alt-F1 to go to the ttyE0 session
 
 The message came out twice after this whenever I pressed and
 released any key, that is, one message came out when the key
 was pressed and one came out when it was released. There was no
 kernel panic this time.
 
 I found that if I switched to a different machine on the
 KVM again and then switched back the keyboard started to work
 and I no longer got the wskbd_input message. There were messages
 to indicate that it had reconnected to the keyboard as follows:
 
 wskbd_input: evar->q=NULL
 wskbd_input: evar->q=NULL
 ukbd0: was console keyboard
 wskbd0: detached
 ukbd0: detached
 uhidev0: detached
 uhidev0: at uhub2 port 2 (addr 5) disconnected
 wsmouse0: detached
 ums0: detached
 uhidev1: detached
 uhidev1: at uhub2 port 3 (addr 6) disconnected
 uhub2: detached
 uhub2: at uhub1 port 2 (addr 4) disconnected
 uhub2 at uhub1 port 2: vendor 1a40 (0x1a40) USB 2.0 Hub [Safe] (0x101), class 9/0, rev 2.00/1.11, addr 4
 uhub2: 4 ports with 4 removable, self powered
 uhidev0 at uhub2 port 2 configuration 1 interface 0
 uhidev0: Chicony (0x4f2) USB Keyboard (0x110), rev 1.10/1.01, addr 5, iclass 3/1
 ukbd0 at uhidev0: 8 Variable keys, 6 Array codes
 wskbd0 at ukbd0: console keyboard, using wsdisplay0
 uhidev1 at uhub2 port 3 configuration 1 interface 0
 uhidev1: PixArt (0x93a) USB Optical Mouse (0x2510), rev 1.10/1.00, addr 6, iclass 3/1
 ums0 at uhidev1: 3 buttons and Z dir
 wsmouse0 at ums0 mux 0
 
 Hopefully this will give you some more information. I do not
 get the kernel panic when using the diagnostic kernel so I will
 continue using this for now. I have also got a workaround for when
 it starts putting out the wskbd_input messages, that is, to switch
 to another session on the KVM and back again, so I am in a
 position where the machine is usable with the KVM now.
 
 I would be happy to test any patch you write for this problem.
 
 Regards,
 Dave Daniels