February 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1195313] failed to install wireless driver on Acer Swift 3
by bugzilla_noreply＠suse.com 04 Feb '22

04 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1195313 http://bugzilla.opensuse.org/show_bug.cgi?id=1195313#c5 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kadlecf(a)fzu.cz, | |tiwai(a)suse.com Flags| |needinfo?(kadlecf(a)fzu.cz) --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- Please give the dmesg output and the hwinfo output from the installed 5.16.x kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1195313] failed to install wireless driver on Acer Swift 3
by bugzilla_noreply＠suse.com 04 Feb '22

04 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1195313 http://bugzilla.opensuse.org/show_bug.cgi?id=1195313#c4 --- Comment #4 from Filip Kadlec <kadlecf(a)fzu.cz> --- You may be right for the firmware; however, I don't know how to check this. There does not seem to be anything related to Mediatek in https://download.opensuse.org/repositories/hardware/openSUSE_Leap_15.3/x86_… . But perhaps I am not looking at the right place. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1195313] failed to install wireless driver on Acer Swift 3
by bugzilla_noreply＠suse.com 03 Feb '22

03 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1195313 https://bugzilla.suse.com/show_bug.cgi?id=1195313#c3 Stefan Hundhammer <shundhammer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Installation |Kernel Assignee|yast2-maintainers(a)suse.de |kernel-bugs(a)opensuse.org QA Contact|jsrain(a)suse.com |qa-bugs(a)suse.de --- Comment #3 from Stefan Hundhammer <shundhammer(a)suse.com> --- Please check if you also need to download and install a firmware package for that driver. But anyway, this is not installer related, it's vaguely in the kernel area. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1195461] New: Bluetooth can't be enabled
by bugzilla_noreply＠suse.com 03 Feb '22

03 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1195461 Bug ID: 1195461 Summary: Bluetooth can't be enabled Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: Jan.Mussche(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Suddenly bluetooth was disabled and until now I can't enable it again. The evening before there were updates, also related to bluetooth and wifi but since the laptop was okay for a few hours until it happened, I can't imagine it was caused by the updates. I restored a Timeshift backup from before installing the updates, but this didn't change anything. For more test results see also: https://forums.opensuse.org/showthread.php/565947-Bluetooth-can-not-be-enab… ------------------------------------- /usr/sbin/rfkill ID TYPE DEVICE SOFT HARD 0 wlan phy0 unblocked unblocked 1 bluetooth hci0 unblocked unblocked ------------------------------------- sudo systemctl status bluetooth bluetooth.service bluetooth.target bluetooth-mesh.service [sudo] password for root: �� bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled) Active: active (running) since Wed 2022-02-02 16:38:21 CET; 1h 38min ago Docs: man:bluetoothd(8) Main PID: 1647 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4915) CPU: 22ms CGroup: /system.slice/bluetooth.service ��1647 /usr/libexec/bluetooth/bluetoothd Feb 02 16:38:21 localhost systemd[1]: Starting Bluetooth service... Feb 02 16:38:21 localhost bluetoothd[1647]: Bluetooth daemon 5.62 Feb 02 16:38:21 localhost systemd[1]: Started Bluetooth service. Feb 02 16:38:21 localhost bluetoothd[1647]: Starting SDP server Feb 02 16:38:21 localhost bluetoothd[1647]: Bluetooth management interface 1.21 initialized �� bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled) Active: active (running) since Wed 2022-02-02 16:38:21 CET; 1h 38min ago Docs: man:bluetoothd(8) Main PID: 1647 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4915) CPU: 22ms CGroup: /system.slice/bluetooth.service ��1647 /usr/libexec/bluetooth/bluetoothd Feb 02 16:38:21 localhost systemd[1]: Starting Bluetooth service... Feb 02 16:38:21 localhost bluetoothd[1647]: Bluetooth daemon 5.62 Feb 02 16:38:21 localhost systemd[1]: Started Bluetooth service. Feb 02 16:38:21 localhost bluetoothd[1647]: Starting SDP server Feb 02 16:38:21 localhost bluetoothd[1647]: Bluetooth management interface 1.21 initialized �� bluetooth.target - Bluetooth Support Loaded: loaded (/usr/lib/systemd/system/bluetooth.target; static) Active: active since Wed 2022-02-02 16:38:21 CET; 1h 38min ago Docs: man:systemd.special(7) Feb 02 16:38:21 localhost systemd[1]: Reached target Bluetooth Support. �� bluetooth-mesh.service - Bluetooth mesh service Loaded: loaded (/usr/lib/systemd/system/bluetooth-mesh.service; enabled; vendor preset: disabled) Active: inactive (dead) since Wed 2022-02-02 16:38:21 CET; 1h 38min ago Main PID: 1646 (code=exited, status=0/SUCCESS) CPU: 17ms Feb 02 16:38:21 localhost systemd[1]: Starting Bluetooth mesh service... Feb 02 16:38:21 localhost bluetooth-meshd[1646]: D-Bus ready Feb 02 16:38:21 localhost bluetooth-meshd[1646]: Request name failed Feb 02 16:38:21 localhost systemd[1]: bluetooth-mesh.service: Deactivated successfully. Feb 02 16:38:21 localhost systemd[1]: Started Bluetooth mesh service. ------------------------------------- sudo hwinfo grep bluetooth P: /devices/pci0000:00/0000:00:08.1/0000:02:00.4/usb3/3-2/3-2.2/3-2.2:1.0/bluetooth/hci0 E: DEVPATH=/devices/pci0000:00/0000:00:08.1/0000:02:00.4/usb3/3-2/3-2.2/3-2.2:1.0/bluetooth/hci0 E: SUBSYSTEM=bluetooth E: SYSTEMD_ALIAS=/sys/subsystem/bluetooth/devices/hci0 E: SYSTEMD_WANTS=bluetooth.target E: SYSTEMD_USER_WANTS=bluetooth.target P: /devices/pci0000:00/0000:00:08.1/0000:02:00.4/usb3/3-2/3-2.2/3-2.2:1.0/bluetooth/hci0/rfkill1 E: DEVPATH=/devices/pci0000:00/0000:00:08.1/0000:02:00.4/usb3/3-2/3-2.2/3-2.2:1.0/bluetooth/hci0/rfkill1 E: RFKILL_TYPE=bluetooth /devices/pci0000:00/0000:00:08.1/0000:02:00.4/usb3/3-2/3-2.2/3-2.2:1.0/bluetooth/hci0 /devices/pci0000:00/0000:00:08.1/0000:02:00.4/usb3/3-2/3-2.2/3-2.2:1.0/bluetooth/hci0/rfkill1 bluetooth 745472 14 bnep,btusb,btrtl,btbcm,btintel, Live 0xffffffffc19ba000 ecdh_generic 16384 1 bluetooth, Live 0xffffffffc169c000 rfkill 28672 10 bluetooth,cfg80211, Live 0xffffffffc0904000 Hardware Class: bluetooth ------------------------------------- dmesg | grep luetooth [ 5.265345] Bluetooth: Core ver 2.22 [ 5.277623] Bluetooth: HCI device and connection manager initialized [ 5.277631] Bluetooth: HCI socket layer initialized [ 5.277636] Bluetooth: L2CAP socket layer initialized [ 5.277646] Bluetooth: SCO socket layer initialized [ 5.492130] Bluetooth: hci0: unexpected event for opcode 0x0000 [ 5.535178] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 5.535183] Bluetooth: BNEP filters: protocol multicast [ 5.535190] Bluetooth: BNEP socket layer initialized [ 9.497626] Bluetooth: hci0: Controller not accepting commands anymore: ncmd = 0 [ 15.641599] Bluetooth: hci0: sending initial HCI reset failed (-110) -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1195461] Bluetooth can't be enabled
by bugzilla_noreply＠suse.com 03 Feb '22

03 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1195461 https://bugzilla.suse.com/show_bug.cgi?id=1195461#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Jan.Mussche(a)gmail.com, | |tiwai(a)suse.com Flags| |needinfo?(Jan.Mussche@gmail | |.com) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Please give the full dmesg output after a fresh boot, and the output of hwinfo. Also, you can try to turn off your machine and power off completely once (unplug the power cable), then retry. The BT error -110 is often related with an intel chip initialization problem. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1194086] Touchpad scrolling is not working on some boots
by bugzilla_noreply＠suse.com 03 Feb '22

03 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1194086 https://bugzilla.suse.com/show_bug.cgi?id=1194086#c29 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #29 from Takashi Iwai <tiwai(a)suse.com> --- OK, thanks for confirmation. The workaround patch was merged in stable branch and destined for TW release in a near future. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1194086] Touchpad scrolling is not working on some boots
by bugzilla_noreply＠suse.com 03 Feb '22

03 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1194086 https://bugzilla.suse.com/show_bug.cgi?id=1194086#c28 --- Comment #28 from Victor Zhestkov <victor.zhestkov(a)suse.com> --- Hi Takashi. It works fine I think. Here is the message I see on this boot: [ 1.436522] psmouse serio1: synaptics: Query error (-5), retrying... But it works fine after. If you need some extra info, feel free to ask. Thanks a lot for the fix!!! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1187701] New: Ten64 fails to boot (kernel panic in initramfs) from nvme after upgrade to kernel 5.3.18-59.5-default
by bugzilla_noreply＠suse.com 03 Feb '22

03 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1187701 Bug ID: 1187701 Summary: Ten64 fails to boot (kernel panic in initramfs) from nvme after upgrade to kernel 5.3.18-59.5-default Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: aarch64 OS: openSUSE Leap 15.3 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: matt(a)traverse.com.au QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 850544 --> http://bugzilla.opensuse.org/attachment.cgi?id=850544&action=edit Failed boot on kernel 5.3.18-59.5-default Hello, After Leap 15.3 appliance images were updated recently, I have found the newer versions no longer boot on Ten64. Working image build: openSUSE-Leap-15.3-ARM-JeOS-efi.aarch64-2021.05.21-Build9.94.raw.xz / kernel 5.3.18-57-default Not working: openSUSE-Leap-15.3-ARM-JeOS-efi.aarch64-2021.05.21-Build9.106.raw.xz / kernel 5.3.18-59.5-default If I upgrade the kernel inside Build9.94 with 'zypper up', the same issue occurs. If I then choose the previous snapshot from GRUB the system can once again be booted with 5.3.18-57. Boot fails due to this, during initramfs/dracut: [ 6.227357] Internal error: synchronous external abort: 96000210 [#1] SMP [ 6.232443] mmc0: SDHCI controller on 2140000.esdhc [2140000.esdhc] using ADMA 64-bit [ 6.234152] Modules linked in: nvme nvme_core dwc3 sdhci_of_esdhc(+) sdhci_pltfm sdhci t10_pi mmc_core ulpi udc_core rtc_fsl_ftm_alarm i2c_imx gpio_keys sg scsi_mod [ 6.256675] Supported: Yes [ 6.259380] CPU: 6 PID: 7 Comm: kworker/u16:0 Not tainted 5.3.18-59.5-default #1 SLE15-SP3 [ 6.267643] Hardware name: traverse ten64/ten64, BIOS 2020.07-rc1-gb47b96d4 06/25/2021 [ 6.275581] Workqueue: nvme-reset-wq nvme_reset_work [nvme] [ 6.275587] pstate: a0000005 (NzCv daif -PAN -UAO) [ 6.275594] pc : nvme_reset_work+0x16c/0x12f8 [nvme] [ 6.275600] lr : nvme_reset_work+0x164/0x12f8 [nvme] [ OK 6.275601] sp : ffff8000100a3c80 m] Reached targe[ 6.275603] x29: ffff8000100a3c80 x28: ffff0732958af0c0 t Basic[ 6.275606] x27: ffff0732958af0c0 x26: ffff0732954412c0 System. [ 6.275609] x25: ffff073295441300 x24: ffff073295441710 [ 6.275611] x23: ffff0732958af000 x22: ffff073295441000 [ 6.275614] x21: ffffb9bd5bd89000 x20: ffff073295440f10 [ 6.275617] x19: ffff073295441000 x18: ffffffffffffffff [ 6.275620] x17: 0000000000000000 x16: ffffb9bd5a7a35a0 [ 6.275622] x15: ffffb9bd5bd89908 x14: 0000000000000040 [ 6.275625] x13: 0000000000000228 x12: 0000000000000000 [ 6.275628] x11: 0000000000000000 x10: 0000000000001a50 [ 6.275630] x9 : ffff8000100a3d10 x8 : 000000000000007d [ 6.275633] x7 : 0000000000000006 x6 : 0000000000010000 [ 6.275635] x5 : 0000000000000000 x4 : 0000000000000000 [ 6.275638] x3 : 0000000080000000 x2 : 0000000000000000 [ 6.275641] x1 : ffffffffffffffff x0 : ffff8000105b201c [ 6.275644] Call trace: [ 6.275651] nvme_reset_work+0x16c/0x12f8 [nvme] [ 6.275659] process_one_work+0x200/0x458 [ 6.275662] worker_thread+0x144/0x4f0 [ 6.275666] kthread+0x130/0x138 [ 6.275670] ret_from_fork+0x10/0x18 [ 6.275675] Code: aa1c03e0 940005af f9414ac0 91007000 (b9400000) [ 6.275678] ---[ end trace c33296e2e9bf08c4 ]--- I have confirmed this issue with multiple Ten64 units and different SSD models, so it does not appear to be hardware related -- You are receiving this mail because: You are the assignee for the bug.

1 22

[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