usb keyboard not working *right after boot*

[Cardinal Kracker]

I have been using a Lenovo 480s with Ubuntu mate 18.04 for a year.

But after Installation the latest (signed) kernel 5.3.0-46 the keyboard
(and sometimes the mouse too) do not work right after boot.

Builtin keyboard and trackpad do work.

Unplugging/replugging to different ports does not help.

Mass storage devices are not affected.

After a couple of minutes keyboard and mouse begin to work as usual.

5.3.0-45 does not have that problem (keyboard works right from the start)

I found a hint to install "xserver-xorg-input-all". Did not help.

[Chris Ritson (chrisritson)]

I am using an intel NUC and ubuntu-mate 18.04-4 which is up to date. I'm making extensive use of firefox and remmina for working at home (if relevant). While I was on 5.3.0-45 kernel everything was stable. Since switching to 5.3.0-46 I have experiences about one system freeze per day. This is so hard a freeze that the "magic" alt/sysrq is not seen by the kernel (which it is on the previous kernel). I haven't tried waiting a long time as described here, but I have tried unpluging / replugging them to no effect.

I'm not sure how to get the necessary information out of a hung system.

[Francis Ginther (fginther)]

@chris

There may be events saved to /var/log/kern.log during the freeze. If you can reproduce the freeze again on 5.3.0-46, reboot then collect and post the contents of /var/log/kern.log around the time of the freeze.

[Cardinal Kracker (launchpap-user)]

Problem still exists in Kernel 5.3.0-51-generic.

By the way, since Kernel 5.3.0-46 I also get occasionally some X hangs
accompanied by:

Apr 29 09:55:41 titania kernel: i915 0000:00:02.0: GPU HANG: ecode 9:0:0x00000000, hang on rcs0
Apr 29 09:55:41 titania kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0

[Chris Ritson (chrisritson)]

@Francis

There's noting consistently logged in kern.log just before a crash/restart. There are quite a few complaints along the lines of:

Apr 1 09:02:20 chris-nuc kernel: [ 1565.582004] perf: interrupt took too long (
2517 > 2500), lowering kernel.perf_event_max_sample_rate to 79250

with sample rates getting lower and lower. I see these with all kernels and have no reason to beleive they are linked to the fault. The attachment contains a full kern.log for over several weeks and kernel versions but with all start up lines with a time stamp up to T+99 seconds deleted to make them small enough to look at.

Yesterday I updated the BIOS (5 years out of date) and the system, so I now have one newer kernel to try, but for now will stay on 5.3.0-46-generic #38~18.04.1-Ubuntu to see if the BIOS update has helped.

[Chris Ritson (chrisritson)]

Oops wrong bug - this bug was sugested as a possible duplicate of mine - unexpected hang which cannot be broken into with SysRQ but not straigt after boot and also new with -46.

[Cardinal Kracker (launchpap-user)]

Problem persists on Mate 20.04 LTS (kernel 4.5.0.29-generic)

I'd like to rule out HW issues as the keyboard works with BIOS and GRUB.

[Cardinal Kracker (launchpap-user)]

Meanwhile I got a grip on a different keyboard which does not exhibit this behavior.

I have seen glitches (occasional reconnects) regarding the Keyboard (a WASD 87key V2 ID=04D9:0169) before. So I assume now that the firmware is not quite standard compliant which starts to cause problems starting with 5.3.0-46.

[Launchpad Janitor (janitor)]

[Expired for Ubuntu MATE because there has been no activity for 60 days.]