February 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1195027] New: HDA Analog: ASoC: dpcm_fe_dai_hw_params failed (-22)
by bugzilla_noreply＠suse.com 02 Feb '22

02 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1195027 Bug ID: 1195027 Summary: HDA Analog: ASoC: dpcm_fe_dai_hw_params failed (-22) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: suse(a)rop.cx QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After resume from sleep mode, the sound disappeared [ 4787.005478] sof-audio-pci-intel-tgl 0000:00:1f.3: ipc tx error for 0x80010000 (msg/reply size: 216/12): -19 [ 4787.005496] sof-audio-pci-intel-tgl 0000:00:1f.3: error: failed resetting DAI config for HDA0.OUT [ 4787.035273] sof-audio-pci-intel-tgl 0000:00:1f.3: ipc tx error for 0x30010000 (msg/reply size: 96/20): -22 [ 4787.035289] sof-audio-pci-intel-tgl 0000:00:1f.3: error: failed to load widget HDA0.OUT [ 4787.036568] sof-audio-pci-intel-tgl 0000:00:1f.3: error: failed widget list set up for pcm 0 dir 0 [ 4787.036580] sof-audio-pci-intel-tgl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:00:1f.3: -22 [ 4787.036589] HDA Analog: ASoC: soc_pcm_hw_params() failed (-22) [ 4787.036644] HDA Analog: ASoC: dpcm_fe_dai_hw_params failed (-22) [ 4787.036897] sof-audio-pci-intel-tgl 0000:00:1f.3: ipc tx error for 0x30010000 (msg/reply size: 96/20): -22 [ 4787.036904] sof-audio-pci-intel-tgl 0000:00:1f.3: error: failed to load widget HDA0.OUT [ 4787.036908] sof-audio-pci-intel-tgl 0000:00:1f.3: error: failed setting up DAI widget HDA0.OUT [ 4787.036912] sof-audio-pci-intel-tgl 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on Analog CPU DAI: -22 [ 4787.036922] Analog Playback and Capture: ASoC: soc_pcm_hw_params() failed (-22) [ 4787.036926] HDA Analog: ASoC: dpcm_fe_dai_hw_params failed (-22) [ 4787.037122] sof-audio-pci-intel-tgl 0000:00:1f.3: ipc tx error for 0x30010000 (msg/reply size: 96/20): -22 [ 4787.037129] sof-audio-pci-intel-tgl 0000:00:1f.3: error: failed to load widget HDA0.OUT [ 4787.037133] sof-audio-pci-intel-tgl 0000:00:1f.3: error: failed setting up DAI widget HDA0.OUT [ 4787.037137] sof-audio-pci-intel-tgl 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on Analog CPU DAI: -22 [ 4787.037146] Analog Playback and Capture: ASoC: soc_pcm_hw_params() failed (-22) [ 4787.037150] HDA Analog: ASoC: dpcm_fe_dai_hw_params failed (-22) [ 4787.037339] sof-audio-pci-intel-tgl 0000:00:1f.3: ipc tx error for 0x30010000 (msg/reply size: 96/20): -22 [ 4787.037345] sof-audio-pci-intel-tgl 0000:00:1f.3: error: failed to load widget HDA0.OUT [ 4787.037349] sof-audio-pci-intel-tgl 0000:00:1f.3: error: failed setting up DAI widget HDA0.OUT [ 4787.037353] sof-audio-pci-intel-tgl 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on Analog CPU DAI: -22 [ 4787.037361] Analog Playback and Capture: ASoC: soc_pcm_hw_params() failed (-22) [ 4787.037365] HDA Analog: ASoC: dpcm_fe_dai_hw_params failed (-22) [ 4787.037552] sof-audio-pci-intel-tgl 0000:00:1f.3: ipc tx error for 0x30010000 (msg/reply size: 96/20): -22 [ 4787.037558] sof-audio-pci-intel-tgl 0000:00:1f.3: error: failed to load widget HDA0.OUT [ 4787.037562] sof-audio-pci-intel-tgl 0000:00:1f.3: error: failed setting up DAI widget HDA0.OUT [ 4787.037566] sof-audio-pci-intel-tgl 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on Analog CPU DAI: -22 [ 4787.037574] Analog Playback and Capture: ASoC: soc_pcm_hw_params() failed (-22) [ 4787.037578] HDA Analog: ASoC: dpcm_fe_dai_hw_params failed (-22) -- You are receiving this mail because: You are the assignee for the bug.

1 13

[Bug 1195451] New: [RPi 400] No bluetooth device detected
by bugzilla_noreply＠suse.com 02 Feb '22

02 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1195451 Bug ID: 1195451 Summary: [RPi 400] No bluetooth device detected Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dheidler(a)suse.com QA Contact: qa-bugs(a)suse.de CC: guillaume.gardet(a)opensuse.org Found By: --- Blocker: --- Created attachment 855807 --> https://bugzilla.suse.com/attachment.cgi?id=855807&action=edit dmesg On the raspberry pi 400 no bluetooth controller is detected. On the raspberry pi 4b it works out of the box. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1194418] Unable to wake up keyboard and mouse
by bugzilla_noreply＠suse.com 02 Feb '22

02 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1194418 https://bugzilla.suse.com/show_bug.cgi?id=1194418#c15 --- Comment #15 from Takashi Iwai <tiwai(a)suse.com> --- Well, you mentioned in the original report "I have to restart computer", and this has to be clarified whether it's really no other way to wake up or it's just because the USB keyboard/mouse wakeup doesn't work. The USB problem is often rather a configuration problem, you'd need to disable the runtime PM or whatever the power-saving stuff for USB. But if the wakeup / resume doesn't work with PS/2 in some condition, this is another (more severe) bug. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1194418] Unable to wake up keyboard and mouse
by bugzilla_noreply＠suse.com 02 Feb '22

02 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1194418 https://bugzilla.suse.com/show_bug.cgi?id=1194418#c14 --- Comment #14 from macias - <bluedzins(a)wp.pl> --- Ok, I can do this, but I am lost here what we are looking for. PS/2 keyboard is attached just in case a secondary keyboard. The main issue is USB keyboard (and mouse) is unresponsive. So if we wait for suspend to ram to trigger the same behaviour it is already done, because suspend to ram makes USB keyboard unresponsive indeed. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193255] Uninformative video device names as of Kernel 5.15.3
by bugzilla_noreply＠suse.com 02 Feb '22

02 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1193255 https://bugzilla.suse.com/show_bug.cgi?id=1193255#c30 --- Comment #30 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2022:0288-1: An update that solves 9 vulnerabilities, contains 7 features and has 30 fixes is now available. Category: security (important) Bug References: 1065729,1071995,1154353,1154492,1156395,1167773,1176447,1176774,1177437,1190256,1191271,1192931,1193255,1193328,1193669,1193727,1193767,1193901,1193927,1194001,1194027,1194302,1194493,1194516,1194517,1194518,1194529,1194580,1194584,1194586,1194587,1194589,1194590,1194591,1194592,1194888,1194953,1194985,1195062 CVE References: CVE-2021-4083,CVE-2021-4135,CVE-2021-4149,CVE-2021-4197,CVE-2021-4202,CVE-2021-44733,CVE-2021-46283,CVE-2022-0185,CVE-2022-0322 JIRA References: SLE-13294,SLE-13533,SLE-14777,SLE-15172,SLE-16683,SLE-23432,SLE-8464 Sources used: SUSE Linux Enterprise Module for Realtime 15-SP3 (src): kernel-rt-5.3.18-150300.71.1, kernel-rt_debug-5.3.18-150300.71.1, kernel-source-rt-5.3.18-150300.71.1, kernel-syms-rt-5.3.18-150300.71.1 SUSE Linux Enterprise Micro 5.1 (src): kernel-rt-5.3.18-150300.71.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190256] Keyboard not working after cold-boot on ASUS Zenbook 14 UM425UA with Tumbleweed 20210904
by bugzilla_noreply＠suse.com 02 Feb '22

02 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1190256 https://bugzilla.suse.com/show_bug.cgi?id=1190256#c37 --- Comment #37 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2022:0288-1: An update that solves 9 vulnerabilities, contains 7 features and has 30 fixes is now available. Category: security (important) Bug References: 1065729,1071995,1154353,1154492,1156395,1167773,1176447,1176774,1177437,1190256,1191271,1192931,1193255,1193328,1193669,1193727,1193767,1193901,1193927,1194001,1194027,1194302,1194493,1194516,1194517,1194518,1194529,1194580,1194584,1194586,1194587,1194589,1194590,1194591,1194592,1194888,1194953,1194985,1195062 CVE References: CVE-2021-4083,CVE-2021-4135,CVE-2021-4149,CVE-2021-4197,CVE-2021-4202,CVE-2021-44733,CVE-2021-46283,CVE-2022-0185,CVE-2022-0322 JIRA References: SLE-13294,SLE-13533,SLE-14777,SLE-15172,SLE-16683,SLE-23432,SLE-8464 Sources used: SUSE Linux Enterprise Module for Realtime 15-SP3 (src): kernel-rt-5.3.18-150300.71.1, kernel-rt_debug-5.3.18-150300.71.1, kernel-source-rt-5.3.18-150300.71.1, kernel-syms-rt-5.3.18-150300.71.1 SUSE Linux Enterprise Micro 5.1 (src): kernel-rt-5.3.18-150300.71.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193255] Uninformative video device names as of Kernel 5.15.3
by bugzilla_noreply＠suse.com 02 Feb '22

02 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1193255 https://bugzilla.suse.com/show_bug.cgi?id=1193255#c29 --- Comment #29 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2022:0289-1: An update that solves 10 vulnerabilities and has 9 fixes is now available. Category: security (important) Bug References: 1071995,1184209,1191271,1193255,1193660,1193669,1193727,1193767,1193901,1193927,1194001,1194087,1194094,1194302,1194516,1194517,1194529,1194888,1194985 CVE References: CVE-2021-4083,CVE-2021-4135,CVE-2021-4149,CVE-2021-4197,CVE-2021-4202,CVE-2021-44733,CVE-2021-45485,CVE-2021-45486,CVE-2022-0185,CVE-2022-0322 JIRA References: Sources used: SUSE Linux Enterprise Module for Realtime 15-SP2 (src): kernel-rt-5.3.18-68.1, kernel-rt_debug-5.3.18-68.1, kernel-source-rt-5.3.18-68.1, kernel-syms-rt-5.3.18-68.1 SUSE Linux Enterprise Micro 5.0 (src): kernel-rt-5.3.18-68.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1195291] initrd is being rebuilt when kernel is being removed after kernel update
by bugzilla_noreply＠suse.com 02 Feb '22

02 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1195291 https://bugzilla.suse.com/show_bug.cgi?id=1195291#c6 --- Comment #6 from Martin Wilck <martin.wilck(a)suse.com> --- (In reply to Michal Suchanek from comment #5) > You don't need to reinstall bootloader when the set of kernels and ramdisks > before and after adding/removing the package is the same. Don't we do this already ? We trigger bootloader installation only if the base package is added or removed, not for -extra or -optional. @Ulrich, I'd advise you to set GRUB_DISABLE_OS_PROBER="true". We disable it by default on SLE for a reason. If there are other installations on the same system, you're usually better off with a custom.cfg that looks like menuentry 'partition 3' { set root=(hd0,3) configfile /boot/grub/grub.cfg } etc. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1195291] initrd is being rebuilt when kernel is being removed after kernel update
by bugzilla_noreply＠suse.com 02 Feb '22

02 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1195291 https://bugzilla.suse.com/show_bug.cgi?id=1195291#c5 --- Comment #5 from Michal Suchanek <msuchanek(a)suse.com> --- You don't need to reinstall bootloader when the set of kernels and ramdisks before and after adding/removing the package is the same. Of course, if you do anything only once in posttrans that solves the problem too. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1195291] initrd is being rebuilt when kernel is being removed after kernel update
by bugzilla_noreply＠suse.com 02 Feb '22

02 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1195291 https://bugzilla.suse.com/show_bug.cgi?id=1195291#c4 --- Comment #4 from Martin Wilck <martin.wilck(a)suse.com> --- (In reply to Michal Suchanek from comment #2) > But we don't need to reinstall bootloader on KMP removal, do we? No, and we don't. That only happens in the main kernel scriptlets. > LILO needed reinstall because it referenced specific blocks in the > filesystem rather than the filename. > > Do we have some scheme that copies the initrd (such as to the EFI partition) > that would require reinstall of bootloader when initrd changes? No idea. It might be a leftover from ancient past. (In reply to Michal Suchanek from comment #3) > we probably don't track if the ramdisk was built or rebuilt but that should > be feasible Not sure where you're heading here. When we remove kernel-default-extra, we must remove the initrd, *unless* we already know we'll remove kernel-default, too. I know it's true in >90% of cases, but that doesn't solve the problem that we don't know for sure. posttrans is really the only way. in posttrans we'll see that the kernel is gone, and we can't build an initrd for it. I have patches here that do this but they haven't had enought testing, and we won't merge them before 15.4 release. Sorry about that. -- You are receiving this mail because: You are the assignee for the bug.

1 0