Some Fn+F* and dot keys on keyboard stop working after resume from suspend mode

[lvd]

OS: Ubuntu MATE 21.10
KERNEL: Linux 5.13.0-22-generic
HW: asus vivobook pro 15 oled M3500QA L1063T (ryzen 5 5600h, radeon gfx)

After going to suspend mode and then returning from it, the following keys stop working:
 - screen brightness control (Fn+F4/F5)
 - touchpad on/off (Fn+F6)
 - keyboard brightness control (Fn+F7)
 - dot key on main keyboard: '>.'
 - dot/delete key on numpad

Other Fn+F* keep working:
 - Sound on/off (Fn+F1)
 - Sound volume control (Fn+F2/F3)

Dot keys also stop working in text console (Ctrl+Alt+F1)

[lvd (lvd-mhm)]

my lspci

[lvd (lvd-mhm)]

This seems to be the same issue: https://askubuntu.com/questions/1380496/asus-vivobook-dot-key-and-brightness-fn-controls-dont-work-after-suspend

[lvd (lvd-mhm)]

Abother related link: https://unix.stackexchange.com/questions/673942/cannot-activate-fn-buttons-and-dot-after-suspend-andresume

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1956093/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[lvd (lvd-mhm)]

For those who'll get the same bug: building vanilla 5.15.x kernel (5.15.13 in my case) using .config from the ubuntu's default (and then make oldconfig with all default choices) seemed to fix the bug.