Strange R64 behavior with a USB keyboard on 0.6.44
#1
Hi,

The subject says it all.  To be clear, the keyboard worked fine in 0.6.41 and now it does not. (I am running Stretch Minimal and the board has been running flawlessly for about a year.)  I am trying to sort out what changed.  Is anyone else seeing this?

I opened a case in github with a ton of details including screenshots and dmesg output.  However, as a quick summary, when I plug in my USB keyboard it is recognized fine, but every time I type a key, the following appears in the console:

rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]

This happens with every keypress and if I hold shift, it repeats rapidly. The Rock64 still accepts the characters normally though, but all this junk makes the physical keyboard unusable.  SSH access still works without an issue and everything seems to be running normally besides this.

Anyone else have this issue?  Any suggestions on how to address it?

Thank you!
  Reply
#2
What's the output of dmesg in relation to USB look like. Try unplugging the keyboard, running dmesg and then plugging it back in and running dmesg again. It looks like your keyboard is not being recognised as a standard HID keyboard.
  Reply
#3
(05-30-2018, 02:49 PM)Rocklobster Wrote: What's the output of dmesg in relation to USB look like. Try unplugging the keyboard, running dmesg and then plugging it back in and running dmesg again. It looks like your keyboard is not being recognised as a standard HID keyboard.

Hi,

Here you go:

Code:
[   40.560047] usb 1-1: new low-speed USB device number 2 using dwc2
[   40.733804] usb 1-1: New USB device found, idVendor=04f2, idProduct=0833
[   40.734841] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   40.735949] usb 1-1: Product: USB Keyboard
[   40.736621] usb 1-1: Manufacturer: CHICONY
[   40.744441] input: CHICONY USB Keyboard as /devices/platform/ff580000.usb/usb1/1-1/1-1:1.0/0003:04F2:0833.0001/input/input1
[   40.798693] hid-generic 0003:04F2:0833.0001: input,hidraw0: USB HID v1.11 Keyboard [CHICONY USB Keyboard] on usb-ff580000.usb-1/input0
[   40.815006] input: CHICONY USB Keyboard as /devices/platform/ff580000.usb/usb1/1-1/1-1:1.1/0003:04F2:0833.0002/input/input2
[   40.867902] hid-generic 0003:04F2:0833.0002: input,hiddev0,hidraw1: USB HID v1.11 Device [CHICONY USB Keyboard] on usb-ff580000.usb-1/input1
[   45.652965] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
[   45.716363] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
[   50.894438] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
[   50.964350] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
[   52.790411] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
[   52.876362] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
  Reply
#4
Seems to be experimenting with various methods with dmc related issues
The message is for debugging put in for dmc operation check

ayufan: rockchip: sip: debug print all sip calls
https://github.com/ayufan-rock64/linux-k...c2dd3dff1d

I think that debug message output part will be deleted when dmc becomes stable
  Reply
#5
(05-30-2018, 03:33 PM)t4_4t Wrote: Seems to be experimenting with various methods with dmc related issues
The message is for debugging put in for dmc operation check

ayufan: rockchip: sip: debug print all sip calls
https://github.com/ayufan-rock64/linux-k...c2dd3dff1d

I think that debug message output part will be deleted when dmc becomes stable

Great find!  Thank you.
  Reply
#6
Did you manage to resolve the spurious output from the keyboard presses.
  Reply
#7
(06-01-2018, 03:14 PM)Rocklobster Wrote: Did you manage to resolve the spurious output from the keyboard presses.

Hi,

No, there has been no resolution.  I assume that it will need the next update to fix,
  Reply
#8
(06-01-2018, 08:32 PM)jl_678 Wrote:
(06-01-2018, 03:14 PM)Rocklobster Wrote: Did you manage to resolve the spurious output from the keyboard presses.

Hi,

No, there has been no resolution.  I assume that it will need the next update to fix,


I can also reproduce this on the 0.6.44 bionic images with a wireless keyboard. I'd say this will go away once the dmc memory issues are resolved.

The referenced commit does indeed look to be the cause of the messages. From the looks of things you shouldn't be seeing those messages by default, as the default kernel log level for the images appears to be '4' (do a cat /proc/config.gz | gunzip | grep LOGLEVEL_DEFAULT to see what your kernel was compiled with) and this is a level 6 message (meaning a log level greater than 6 is needed to see it). Anyway, If you check /proc/sys/kernel/printk, and and the number is 7 or higher, do a echo 4 > /proc/sys/kernel/printk when logged in with su or some such method of getting around the fact you can't sudo when piping. That should stop you seeing the rockchip-sip messages. However, it won't stick, so will need to be reapplied after a reboot or power cycle, so you may want to set it in rc.local, etc.


Code:
[ 5063.080668] usb 3-1: new full-speed USB device number 2 using ohci-platform
[ 5063.269736] usb 3-1: New USB device found, idVendor=046d, idProduct=c52e
[ 5063.269769] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 5063.269791] usb 3-1: Product: USB Receiver
[ 5063.269811] usb 3-1: Manufacturer: Logitech
[ 5063.279854] input: Logitech USB Receiver as /devices/platform/ff5d0000.usb/usb3/3-1/3-1:1.0/0003:046D:C52E.0001/input/input1
[ 5063.332708] hid-generic 0003:046D:C52E.0001: input,hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-ff5d0000.usb-1/input0
[ 5063.340356] input: Logitech USB Receiver as /devices/platform/ff5d0000.usb/usb3/3-1/3-1:1.1/0003:046D:C52E.0002/input/input2
[ 5063.392028] hid-generic 0003:046D:C52E.0002: input,hiddev0,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-ff5d0000.usb-1/input1
[ 5070.714003] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
[ 5070.764764] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
[ 5071.292766] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
[ 5071.412763] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
[ 5071.916767] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
[ 5072.020763] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
[ 5073.837079] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
[ 5074.076776] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
[ 5074.172778] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
[ 5074.236762] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
[ 5075.749101] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
[ 5075.932772] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
[ 5076.028758] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
[ 5076.108755] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
  Reply
#9
(06-01-2018, 10:38 PM)pfeerick Wrote:
(06-01-2018, 08:32 PM)jl_678 Wrote:
(06-01-2018, 03:14 PM)Rocklobster Wrote: Did you manage to resolve the spurious output from the keyboard presses.

Hi,

No, there has been no resolution.  I assume that it will need the next update to fix,


I can also reproduce this on the 0.6.44 bionic images with a wireless keyboard. I'd say this will go away once the dmc memory issues are resolved.

The referenced commit does indeed look to be the cause of the messages. From the looks of things you shouldn't be seeing those messages by default, as the default kernel log level for the images appears to be '4' (do a cat /proc/config.gz | gunzip | grep LOGLEVEL_DEFAULT to see what your kernel was compiled with) and this is a level 6 message (meaning a log level greater than 6 is needed to see it). Anyway, If you check /proc/sys/kernel/printk, and and the number is 7 or higher, do a echo 4 > /proc/sys/kernel/printk when logged in with su or some such method of getting around the fact you can't sudo when piping. That should stop you seeing the rockchip-sip messages. However, it won't stick, so will need to be reapplied after a reboot or power cycle, so you may want to set it in rc.local, etc.


Code:
[ 5063.080668] usb 3-1: new full-speed USB device number 2 using ohci-platform
[ 5063.269736] usb 3-1: New USB device found, idVendor=046d, idProduct=c52e
[ 5063.269769] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 5063.269791] usb 3-1: Product: USB Receiver
[ 5063.269811] usb 3-1: Manufacturer: Logitech
[ 5063.279854] input: Logitech USB Receiver as /devices/platform/ff5d0000.usb/usb3/3-1/3-1:1.0/0003:046D:C52E.0001/input/input1
[ 5063.332708] hid-generic 0003:046D:C52E.0001: input,hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-ff5d0000.usb-1/input0
[ 5063.340356] input: Logitech USB Receiver as /devices/platform/ff5d0000.usb/usb3/3-1/3-1:1.1/0003:046D:C52E.0002/input/input2
[ 5063.392028] hid-generic 0003:046D:C52E.0002: input,hiddev0,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-ff5d0000.usb-1/input1
[ 5070.714003] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
[ 5070.764764] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
[ 5071.292766] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
[ 5071.412763] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
[ 5071.916767] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
[ 5072.020763] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
[ 5073.837079] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
[ 5074.076776] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
[ 5074.172778] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
[ 5074.236762] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
[ 5075.749101] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
[ 5075.932772] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
[ 5076.028758] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
[ 5076.108755] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]

I can confirm that this solved the problem.  Thank you!  As an FYI, LOGLEVEL_DEFAULT was 4. Printk was  7 4 1 7.  Echoing 4 to it turned it into 4 4 1 7, and this solved the error message issue.

Thank you!
  Reply
#10
(06-02-2018, 07:43 PM)jl_678 Wrote: I can confirm that this solved the problem.  Thank you!  As an FYI, LOGLEVEL_DEFAULT was 4. Printk was  7 4 1 7.  Echoing 4 to it turned it into 4 4 1 7, and this solved the error message issue.

Great! Glad to hear it worked. Since you had a 7 4 1 7, and the LOGLEVEL_DEFAULT was correctly set at 4, you may still need to reapply it at boot, as something has changed it.

As a followup (should have included this before), this is what the grouping means. There's also a great write-up about what it all means here.

Code:
4       4       1       7
current    default    minimum    boot-time-default
  Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
Exclamation Strange graphical "glitches" grpeople 10 4,280 09-06-2018, 03:19 PM
Last Post: Luke
  monitor setting & keyboard issues gpine1 2 1,288 05-27-2018, 03:51 PM
Last Post: Luke
  keyboard/mouse freeze after 2-3 seconds on Debian Davo-CC 4 2,610 12-15-2017, 09:54 AM
Last Post: Davo-CC

Forum Jump:


Users browsing this thread: 1 Guest(s)