On Wed, 14 Oct 2020 at 18:09:54 -0400, Ashton Fagg wrote: > Basically if you are trying to use the build-in keyboard from the > console, you'll eventually start getting the console spammed with the > above error message. This usually starts within about 30 seconds of the > machine coming up. I can't seem to correlate it with any event, just > that it usually occurs while typing or just after typing. > > This is quite disruptive because it basically fills the whole > screen. These messages also show up in dmesg. Probably end up getting a > few hundred of these within a few minutes of operation. > > Plugging in a USB keyboard and *not* using the built-in keyboard does > not exhibit this same behavior. As such, the machine is basically > unusable in console mode without a USB keyboard. > > With X running, everything seems to work fine but the messages still > show up in dmesg. Keyboard doesn't seem to be acting unusually.
Do the messages appear if you use the touchpad or just the keyboard? Your machine seems to be another that attaches a legacy pms(4) version of the touchpad in addition to the I2C version (imt/ims) which is probably sending conflicting messages to the devices/bus. If you "boot -c" at the boot loader, and then "disable pms*" do the messages still appear when you use the keyboard? > dwiic0 at acpi0 I2CD addr 0xfedc5000/0x1000 irq 6 > iic0 at dwiic0 > ihidev0 at iic0 addr 0x15 gpio 90, vendor 0x4f3 product 0x312a, ELAN0504 > ihidev0: 14 report ids > imt0 at ihidev0: clickpad, 5 contacts > wsmouse0 at imt0 mux 0 > ims0 at ihidev0 reportid 1: 2 buttons > wsmouse1 at ims0 mux 0 > pckbc0 at isa0 port 0x60/5 irq 1 irq 12 > pckbd0 at pckbc0 (kbd slot) > wskbd0 at pckbd0: console keyboard > pms0 at pckbc0 (aux slot) > wsmouse2 at pms0 mux 0 > pms0: Elantech Clickpad, version 4, firmware 0x4f5001
