Hi
I wonder if setting the debug kernel options for wmi might glean more info, add the following to the bootloader kernel options;
wmi.debug_event=1 wmi.debug_dump_wdg=1
parm: debug_event:Log WMI Events [0/1] (bool)
parm: debug_dump_wdg:Dump available WMI interfaces [0/1] (bool)
Bitals
January 16, 2020, 9:57am
22
malcolmlewis:
Hi
I wonder if setting the debug kernel options for wmi might glean more info, add the following to the bootloader kernel options;
wmi.debug_event=1 wmi.debug_dump_wdg=1
parm: debug_event:Log WMI Events [0/1] (bool)
parm: debug_dump_wdg:Dump available WMI interfaces [0/1] (bool)
Hello.
I added them in grub:
➜ ~ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-5.4.7-1-default root=UUID=0e99f3bb-846d-4f99-9679-7995cd81a9df splash=silent resume=/dev/mapper/cr_ata-SanDisk_SD9SN8W512G1122_183798800782-part4 mitigations=auto quiet wmi.debug_event=1 wmi.debug_dump_wdg=1
But I cannot find any logs in dmesg or journalctl. Where should I look?
Bitals:
Hello.
I added them in grub:
➜ ~ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-5.4.7-1-default root=UUID=0e99f3bb-846d-4f99-9679-7995cd81a9df splash=silent resume=/dev/mapper/cr_ata-SanDisk_SD9SN8W512G1122_183798800782-part4 mitigations=auto quiet wmi.debug_event=1 wmi.debug_dump_wdg=1
But I cannot find any logs in dmesg or journalctl. Where should I look?
Hi
Can you check down in /var/log/directory. I would have thought entries would be there in journalctl.
Bitals
January 16, 2020, 5:07pm
24
See nothing wmi related:
total 61752
drwxr-xr-x 1 root root 1066 Jan 16 19:04 .
drwxr-xr-x 1 root root 132 Jan 13 12:07 ..
-rw-r--r-- 1 root root 36165 Jan 16 19:03 alternatives.log
drwxr-xr-x 1 root root 0 Dec 2 21:51 apparmor
drwx------ 1 root root 40 Jan 13 12:33 audit
-rw-r--r-- 1 root root 16241799 Jan 16 19:04 auto-cpufreq.log
-rw------- 1 root root 2177808 Jan 16 19:00 boot.log
-rw-rw---- 1 root utmp 384 Dec 12 23:15 btmp
drwxr-x--- 1 chrony chrony 0 Nov 16 01:50 chrony
drwxr-xr-x 1 lp lp 38 Dec 18 13:27 cups
drwxr-x--- 1 firebird firebird 0 Jul 9 2019 firebird
-rw-r----- 1 root root 14434 Jan 15 16:26 firewalld
drwx--x--x 1 root gdm 0 Dec 5 09:22 gdm
drwxr-sr-x 1 root systemd-journal 64 Jan 2 18:22 journal
drwx------ 1 root root 0 Dec 16 20:31 krb5
-rw-rw-r-- 1 root utmp 292292 Jan 16 19:00 lastlog
drwx------ 1 root root 24 Jan 1 18:43 libvirt
lrwxrwxrwx 1 root root 18 Dec 5 09:20 log -> /run/initramfs/log
-rw------- 1 root root 22166 Jan 13 17:42 pbl.log
-rw-r----- 1 root root 0 Jan 16 19:00 pk_backend_zypp
-rw-r----- 1 root root 15586761 Jan 16 18:51 pk_backend_zypp-1
drwx------ 1 root root 0 Dec 5 09:18 private
-rw-r--r-- 1 root root 1040 Dec 3 19:58 README
drwxr-x--- 1 root root 0 Dec 24 04:43 samba
-rw-r----- 1 root root 2237660 Jan 16 19:04 snapper.log
drwx------ 1 root root 0 Nov 16 07:23 speech-dispatcher
drwx--x--x 1 root root 14 Jan 1 18:43 swtpm
drwxr-xr-x 1 root root 106 Dec 10 17:17 teamviewer15
drwxr-x--- 1 root root 0 Nov 28 12:16 tuned
drwxr-xr-x 1 root root 1114 Jan 15 16:11 updateTestcase-2020-01-15-16-11-25
drwxr-xr-x 1 root root 1114 Jan 15 16:25 updateTestcase-2020-01-15-16-25-43
-rw-r----- 1 root root 1057883 Jan 16 19:00 wpa_supplicant.log
-rw-rw-r-- 1 root utmp 388224 Jan 16 19:00 wtmp
-rw-r--r-- 1 root root 43257 Dec 12 23:24 Xorg.0.log
-rw-r--r-- 1 root root 47675 Dec 12 23:16 Xorg.0.log.old
-rw-r--r-- 1 root root 21702 Dec 12 23:10 Xorg.1.log
-rw-r--r-- 1 root root 42473 Dec 12 23:09 Xorg.1.log.old
drwx------ 1 root root 550 Jan 16 19:03 YaST2
drwxr-x--- 1 root root 14 Jan 10 22:19 zypp
-rw-r----- 1 root root 17973007 Jan 16 19:04 zypper.log
-rw-r----- 1 root root 482896 Dec 7 17:32 zypper.log-20191208.xz
-rw-r----- 1 root root 1224584 Dec 14 00:57 zypper.log-20191214.xz
-rw-r----- 1 root root 908400 Dec 15 02:13 zypper.log-20191215.xz
-rw-r----- 1 root root 1500736 Dec 21 00:10 zypper.log-20191221.xz
-rw-r----- 1 root root 744432 Dec 27 10:16 zypper.log-20191229.xz
-rw-r----- 1 root root 620516 Dec 31 22:47 zypper.log-20200101.xz
-rw-r----- 1 root root 1789984 Jan 14 23:33 zypper.log-20200115.xz
Hi
All strange…
You have files in ~/.config/pulse? Can you make a backup, then can you logout from the desktop, open a tty, login as root at then head over to your /home/yuor_user/.config/pulse and delete the files, the log back into the desktop. Does this help? The only other thought is something up with the snd-hda-intel module…
Bitals
January 17, 2020, 10:41am
26
malcolmlewis:
Hi
All strange…
You have files in ~/.config/pulse? Can you make a backup, then can you logout from the desktop, open a tty, login as root at then head over to your /home/yuor_user/.config/pulse and delete the files, the log back into the desktop. Does this help? The only other thought is something up with the snd-hda-intel module…
Hello. Deleted this, logged in and nothing changed. I still think this looks more like wmi problem than audio problem because I can now use Fn+F7/8 hotkeys freely, and showkey says that they send the exact same keycode as the side buttons, which are handled strangely by the system.
Bitals:
Hello. Deleted this, logged in and nothing changed. I still think this looks more like wmi problem than audio problem because I can now use Fn+F7/8 hotkeys freely, and showkey says that they send the exact same keycode as the side buttons, which are handled strangely by the system.
Hi
Then I would suggest a bug against wmi and see where it goes, can you post back the bug reference please
Bitals
January 20, 2020, 10:21am
28
Bitals
January 21, 2020, 3:58pm
29
Takashi Iwai helped to trace it down to intel-hid driver, it and and keyboard devices were both handling events for side volume buttons simultaneously.
Blacklisting intel-hid seems to get rid of this, and I did not see any other functionality affected yet.
He suggested to come with this to a kernel Bugzilla, and this time I was able to find a somewhat similar bug that is pretty old:
https://bugzilla.kernel.org/show_bug.cgi?id=95221
Will have to wait for reply and see if it is actually the same case, if not - create a new report.
oldcpu
January 22, 2020, 4:08am
30
Bitals:
Takashi Iwai helped to trace it down to intel-hid driver, it and and keyboard devices were both handling events for side volume buttons simultaneously.
Blacklisting intel-hid seems to get rid of this, and I did not see any other functionality affected yet.
He suggested to come with this to a kernel Bugzilla, and this time I was able to find a somewhat similar bug that is pretty old:
95221 – Audio keys captured twice on HP Compaq 6735s (laptop)
Will have to wait for reply and see if it is actually the same case, if not - create a new report.
Many thanks for following this through.
Takashi provides great support and its good to a work around for you.