No idea what this is and not finding any real info on it. I get some crashes and this always seems to be in the journal/
event2: Failed to call EVIOCSKEYCODE with scan code 0xc01cb, and key code 108: Invalid argument
This should help Keyboard input - ArchWiki about scancodes
Some keyboards have their own USB ports to connect different devices trough it … the following comment might explain things about your issue Comment #22 : Bug #1890186 : Bugs : systemd package : Ubuntu
Taken from here systemd error / Newbie Corner / Arch Linux Forums where someone reports similar issue.
1 Like
Hello,
I have the same issue, but with different key code from couple of updates back.
I googled around and found out that the bug was introduced in systemd 251, and that they won’t fix it
as it is harmless according to them.
I checked all keys on my keyboard as it has extra keys and they all work fine.
Also haven’t seen any side effects from the error. It just pollutes the journal.
On some ubuntu forums I found a workaround, but I didn’t dare to try it, because everything works fine
on my end.
I don’t think its the eviocskeycode error that causes the crashes.
This is just my 2 cents 
Cheers…
Oh there are some other errors and I am just trying to sort it out. That is one that keeps popping up.
If needed: use “blacklist eeepc_wmi” by
sudo nano /etc/modprobe.d/EVIOCSKEYCODE.conf
and reboot.
I am searching for disadvantages, so no warranty…
1 Like