Edge-V: Domain: kernel - Infrared daemon floods syslog with 2 error messages per second

Describe the bug
A clear and concise description of what the bug is.

After one day the Edge-V was not responding anymore over WiFi.
Looking deeper into syslog I found that lircd emitted every two seconds error messages:

To Reproduce
Steps to reproduce the behavior:

Board: Edge-V
OS: Edge_Ubuntu-server-bionic_Linux-4.4_arm64_SD-USB_V20181115

Executing sudo systemctl -b -1 I got tons of

Aug 17 20:17:04 Khadas lircd-0.10.0[688]: Notice: /etc/lirc/lircd.conf.d/devinput.lircd.conf: devinput-64: Multiple values for same code: BTN_SOUTH
Aug 17 20:17:04 Khadas lircd-0.10.0[688]: Notice: /etc/lirc/lircd.conf.d/devinput.lircd.conf: devinput-64: Multiple values for same code: BTN_TOOL_PEN
Aug 17 20:17:04 Khadas lircd-0.10.0[688]: Notice: /etc/lirc/lircd.conf.d/devinput.lircd.conf: devinput-64: Multiple values for same code: BTN_TRIGGER
Aug 17 20:17:04 Khadas lircd-0.10.0[688]: Notice: /etc/lirc/lircd.conf.d/devinput.lircd.conf: devinput-64: Multiple values for same code: BTN_TRIGGER_HAPPY1
Aug 17 20:17:04 Khadas lircd-0.10.0[688]: Notice: /etc/lirc/lircd.conf.d/devinput.lircd.conf: devinput-64: Multiple values for same code: BTN_WHEEL
Aug 17 20:17:04 Khadas lircd-0.10.0[688]: Info: Using remote: devinput-32.
Aug 17 20:17:04 Khadas lircd-0.10.0[688]: Notice: /etc/lirc/lircd.conf.d/devinput.lircd.conf: devinput-32: Multiple values for same code: BTN_MISC
Aug 17 20:17:04 Khadas lircd-0.10.0[688]: Notice: /etc/lirc/lircd.conf.d/devinput.lircd.conf: devinput-32: Multiple values for same code: BTN_MOUSE
Aug 17 20:17:04 Khadas systemd[1]: Started resolvconf-pull-resolved.service.
Aug 17 20:17:04 Khadas lircd-0.10.0[688]: Notice: /etc/lirc/lircd.conf.d/devinput.lircd.conf: devinput-32: Multiple values for same code: BTN_SOUTH
Aug 17 20:17:04 Khadas lircd-0.10.0[688]: Notice: /etc/lirc/lircd.conf.d/devinput.lircd.conf: devinput-32: Multiple values for same code: BTN_TOOL_PEN
Aug 17 20:17:04 Khadas lircd-0.10.0[688]: Notice: /etc/lirc/lircd.conf.d/devinput.lircd.conf: devinput-32: Multiple values for same code: BTN_TRIGGER
Aug 17 20:17:04 Khadas lircd-0.10.0[688]: Notice: /etc/lirc/lircd.conf.d/devinput.lircd.conf: devinput-32: Multiple values for same code: BTN_TRIGGER_HAPPY1
Aug 17 20:17:04 Khadas lircd-0.10.0[688]: Notice: /etc/lirc/lircd.conf.d/devinput.lircd.conf: devinput-32: Multiple values for same code: BTN_WHEEL
Aug 17 20:17:04 Khadas lircd-0.10.0[688]: Notice: lircd(devinput) ready, using /var/run/lirc/lircd
Aug 17 20:17:04 Khadas lircd-0.10.0[688]: Notice: accepted new client on /var/run/lirc/lircd
Aug 17 20:17:04 Khadas lircd-0.10.0[688]: Info: initializing 'auto'
Aug 17 20:17:04 Khadas lircd-0.10.0[688]: Cannot run glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*: No such file or directory
Aug 17 20:17:04 Khadas lircd-0.10.0[688]: Notice: No input device available for devinput driver. Consider stopping lircd.socket or reconfigure lirc
Aug 17 20:17:04 Khadas lircd-0.10.0[688]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
Aug 17 20:17:04 Khadas lircd-0.10.0[688]: Warning: Failed to initialize hardware
Aug 17 20:17:04 Khadas lircd-0.10.0[688]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
Aug 17 20:17:04 Khadas lircd-0.10.0[688]: Notice: accepted new client on /var/run/lirc/lircd
Aug 17 20:17:04 Khadas lircd-0.10.0[688]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
Aug 17 20:17:04 Khadas lircd-0.10.0[688]: Notice: accepted new client on /var/run/lirc/lircd

Expected behavior
A clear and concise description of what you expected to happen.

No error messages

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

I disabled and masked the lircd socket and service with:

sudo systemctl stop lircd.socket lircd.service
sudo systemctl disable lircd.socket lircd.service
sudo systemctl mask lircd.socket lircd.service

I found a fix that explains a possible configuration mismatch from 16.04

Hello @giminni

Thanks for your feedback.

Acctually, this issue has been fixed. https://github.com/khadas/fenix/commit/0c64008712012488bc5126520e895f7325206acd#diff-a03915357f6cc6ee619a1853b372fabc

But the image you use is too old and without this commit…

And we will release new image for Edge this month…

Thx @numbqq,

Today I was able to compile my own kernel with fenix 0.7, is the above mentioned commit applied to the latest master?

Yes. it is, the commit is applied.