November 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[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 1192091] New: 5.14.14 assumes USB controller as dead
by bugzilla_noreply＠suse.com 28 Jan '22

28 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1192091 Bug ID: 1192091 Summary: 5.14.14 assumes USB controller as dead Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: stigpro(a)outlook.fr QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Description : No USB(-C) at all when running `5.14.14` on a Lenovo Thinkpad X1 Yoga Gen 6 Steps to reproduce : 1. Boot `5.14.14` Excpected : Working USB like in `5.14.11` Result : Kernel assumes the USB contoller as dead System info : https://paste.opensuse.org/5d9b92f7 Log : https://paste.opensuse.org/f5553d43 Other info : The assumption of the USB controller being dead is at line 1005 (xhci error), it works with no issue on both `5.14.11` and `5.15.0-rc3-next-20210930-1.gd782f60-vanilla` -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1192181] New: brightness keys mute mic instead (HP Elitebook 840 G6)
by bugzilla_noreply＠suse.com 27 Jan '22

27 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1192181 Bug ID: 1192181 Summary: brightness keys mute mic instead (HP Elitebook 840 G6) 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: andreas_nordal_4(a)hotmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On a HP Elitebook 840 G6 laptop, both the backlight brightness keys (F3 and F4) toggle microphone mute state instead of doing their intended thing. The good thing is that other keys, such as mute, volume and the actual microphone mute key (F5, F6, F7, F8) work as intended. No messages appear in dmesg --follow or journalctl --follow when pressing these keys. In evtest, the brightness up and down keys appear as the same identical sequence, which is also a common prefix of the actual mic mute key: Common prefix: type 4 (EV_MSC), code 4 (MSC_SCAN), value 81 type 1 (EV_KEY), code 190 (KEY_F20), value 1 -------------- SYN_REPORT ------------ type 4 (EV_MSC), code 4 (MSC_SCAN), value 81 type 1 (EV_KEY), code 190 (KEY_F20), value 0 -------------- SYN_REPORT ------------ Actual mic mute key (unique suffix part): type 4 (EV_MSC), code 4 (MSC_SCAN), value 42 -------------- SYN_REPORT ------------ Kernel: Linux 5.14.6-1-default I found similar reports about these keys not working: 1. https://bugzilla.opensuse.org/show_bug.cgi?id=1105997 2. https://bugzilla.opensuse.org/show_bug.cgi?id=1160911 The first one was about not showing it correctly, but the last one says: Update: The issue is gone in the latest BIOS update issued by HP. Version: R70 Ver. 01.04.05 Release Date: 02/18/2020 That seems to be the same version as I have (according to lshw): *-firmware description: BIOS vendor: HP physical id: 1 version: R70 Ver. 01.04.05 date: 02/18/2020 size: 64KiB capacity: 32MiB capabilities: pci pcmcia upgrade shadowing cdboot bootselect edd int5printscreen int9keyboard int14serial int17printer acpi usb smartbattery biosbootspecification netboot uefi I haven't tried updating BIOS, but it doesn't look easy. -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 1180260] New: [RPi4] Switch to vc4 for display/sound (was rooted through efifb)
by bugzilla_noreply＠suse.com 21 Jan '22

21 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1180260 Bug ID: 1180260 Summary: [RPi4] Switch to vc4 for display/sound (was rooted through efifb) 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: nsaenzjulienne(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- With v5.10 vc4, the driver enabling RPi's display controller, now supports RPi4. Let's switch the board's kernel configuration and firmware config to use this instead of efifb, which is extremely limited (no sound, no resolution changes). Among other things, some clocks have to be set-up as builtin, a fix is needed in u-boot so as to cater to DT changes involved in enabling vc4 and some overlays have to be selected in config.txt -- You are receiving this mail because: You are the assignee for the bug.

1 4

[kernel-bugs] [Bug 1179226] New: System hang related to power saving
by bugzilla_noreply＠suse.com 21 Jan '22

21 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1179226 Bug ID: 1179226 Summary: System hang related to power saving 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: jc(a)phocean.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- # Issue : Screen and input devices would stop responding (black screen, no TTY), as soon as the computer goes into some low power mode. It can be triggered by locking the screen in Gnome (through gdm), and can also be reproduced in XFCE / LightDM by just leaving the computer for a while. # Impact : - black screen, no TTY access - unresponsive system (impossible to launch new processes, reboot, no way to switch init3 & init 5, etc.) - SSH/network access still available, existing process seem to run Moreover, no related log entry, no error (journalctl, dmesg...). # Notes : Hardware is very likely to be fine : - no issue with a Fedora LiveUSB ; - memtest tests passed. # Hardware : Asus PN40 Intel(R) Celeron(R) J4005 CPU @ 2.00GHz Intel Corporation UHD Graphics 605 (rev 03) # System Tumbleweed 20201123 I have no idea on how to debug it further. My huntch is that it is power saving related with Intel chipset. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[kernel-bugs] [Bug 1176646] New: Latest Kernel has i915 GPU Hang
by bugzilla_noreply＠suse.com 19 Jan '22

19 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1176646 Bug ID: 1176646 Summary: Latest Kernel has i915 GPU Hang Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: erecio(a)polywog.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 841741 --> http://bugzilla.opensuse.org/attachment.cgi?id=841741&action=edit dmesg output The following kernel works fine with my i915 GPU (5.6.14-1). However, the latest kernel 5.7+ (kernel-default-5.8.7-1.2.x86_64) causes my GPU to hang and it flickers and can never login. Switch back to 5.6 and it works fine. There have been other reports on Fedora with the same thing. https://bugzilla.redhat.com/show_bug.cgi?id=1843274 I have attached my dmesg output. I use the zap option to kill the xorg server and kdm comes up just fine most of the time. Trying to login is no good though. Also I can ctrl-alt-f2 to go on command line just fine. So it seems to be xorg with the new kernel. [ 163.236358] ------------[ cut here ]------------ [ 163.236365] WARNING: CPU: 0 PID: 0 at kernel/sched/core.c:4576 default_wake_function+0x16/0x30 [ 163.236366] Modules linked in: xt_MASQUERADE xt_addrtype iptable_nat nf_nat nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_state xt_LOG xt_multiport xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c af_packet iscsi_ibft iscsi_boot_sysfs ip6table_filter ip6_tables iptable_filter ip_tables x_tables bpfilter rfkill tun binfmt_misc dmi_sysfs msr crypto_simd glue_helper dm_crypt intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_realtek snd_hda_codec_generic coretemp ledtrig_audio kvm_intel snd_hda_codec_hdmi snd_hda_intel kvm snd_intel_dspcfg irqbypass snd_hda_codec at24 mei_hdcp iTCO_wdt snd_hda_core intel_pmc_bxt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel iTCO_vendor_support cryptd snd_hwdep pcspkr snd_pcm snd_timer fan thermal snd e1000e soundcore i2c_i801 tiny_power_button i2c_smbus button mei_me lpc_ich mei hid_generic usbhid i915 i2c_algo_bit drm_kms_helper xhci_pci xhci_pci_renesas syscopyarea sysfillrect [ 163.236389] sysimgblt fb_sys_fops cec xhci_hcd rc_core ehci_pci ehci_hcd drm crc32c_intel usbcore video sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua [ 163.236396] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.8.7-1-default #1 openSUSE Tumbleweed [ 163.236397] Hardware name: Gigabyte Technology Co., Ltd. B85M-Gaming 3/B85M-Gaming 3, BIOS F1 09/05/2014 [ 163.236399] RIP: 0010:default_wake_function+0x16/0x30 [ 163.236401] Code: e8 df 53 45 00 eb 99 0f 0b 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 f7 c2 fe ff ff ff 75 09 48 8b 7f 08 e9 da f9 ff ff <0f> 0b 48 8b 7f 08 e9 cf f9 ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 [ 163.236401] RSP: 0018:ffffa51080003eb8 EFLAGS: 00010086 [ 163.236402] RAX: ffffffffb0cf0e30 RBX: ffffa51080203db0 RCX: ffffa51080003ed0 [ 163.236403] RDX: 00000000fffffffb RSI: 0000000000000003 RDI: ffffa51080203db0 [ 163.236404] RBP: ffff980009218568 R08: 0000000000000000 R09: ffffffffc0321600 [ 163.236404] R10: ffff97ffdbd86280 R11: 0000000000000001 R12: 0000000000000046 [ 163.236405] R13: ffff980009218560 R14: ffffa51080003ed0 R15: ffffa51080003f60 [ 163.236406] FS: 0000000000000000(0000) GS:ffff980017200000(0000) knlGS:0000000000000000 [ 163.236406] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 163.236407] CR2: 00007f8ff0b07000 CR3: 000000003f80a001 CR4: 00000000000606f0 [ 163.236408] Call Trace: [ 163.236409] <IRQ> [ 163.236414] autoremove_wake_function+0xe/0x30 [ 163.236460] __i915_sw_fence_complete+0x160/0x1c0 [i915] [ 163.236483] dma_i915_sw_fence_wake_timer+0x2c/0x50 [i915] [ 163.236506] signal_irq_work+0x21c/0x310 [i915] [ 163.236510] irq_work_single+0x2c/0x40 [ 163.236511] irq_work_run_list+0x2d/0x40 [ 163.236512] irq_work_run+0x14/0x30 [ 163.236514] __sysvec_irq_work+0x2d/0xb0 [ 163.236517] asm_call_on_stack+0x12/0x20 [ 163.236518] </IRQ> [ 163.236520] sysvec_irq_work+0x6f/0x90 [ 163.236522] asm_sysvec_irq_work+0x12/0x20 [ 163.236524] RIP: 0010:cpuidle_enter_state+0xb6/0x3f0 [ 163.236525] Code: 10 ee c0 4e e8 eb 52 8d ff 49 89 c7 0f 1f 44 00 00 31 ff e8 cc 69 8d ff 80 7c 24 0f 00 0f 85 d4 01 00 00 fb 66 0f 1f 44 00 00 <45> 85 e4 0f 88 e0 01 00 00 49 63 d4 4c 2b 7c 24 10 48 8d 04 52 48 [ 163.236526] RSP: 0018:ffffffffb2403e58 EFLAGS: 00000246 [ 163.236527] RAX: ffff98001722e680 RBX: ffff980017239600 RCX: 000000000000001f [ 163.236527] RDX: 0000000000000000 RSI: 000000002817b731 RDI: 0000000000000000 [ 163.236528] RBP: ffffffffb24f6260 R08: 0000002601a4c721 R09: 00000000000002ee [ 163.236528] R10: ffff98001722d444 R11: 00000000000005f4 R12: 0000000000000004 [ 163.236529] R13: 0000000000000004 R14: 0000000000000004 R15: 0000002601a4c721 [ 163.236531] ? cpuidle_enter_state+0xa4/0x3f0 [ 163.236533] cpuidle_enter+0x29/0x40 [ 163.236535] cpuidle_idle_call+0x13f/0x210 [ 163.236536] do_idle+0x73/0xd0 [ 163.236538] cpu_startup_entry+0x19/0x20 [ 163.236541] start_kernel+0x485/0x4a4 [ 163.236544] secondary_startup_64+0xb6/0xc0 [ 163.236546] ---[ end trace 5ea2057b70f281c8 ]--- [ 163.236548] ------------[ cut here ]------------ [ 574.899156] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc79, in ksplashqml [3389] [ 574.899728] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [ 575.003261] i915 0000:00:02.0: [drm] ksplashqml[3389] context reset due to GPU hang [ 580.786335] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc79, in ksplashqml [3389] [ 580.786882] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [ 580.890229] i915 0000:00:02.0: [drm] ksplashqml[3389] context reset due to GPU hang [ 583.858065] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc7b, in plasmashell [3461] [ 583.858294] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [ 583.961652] i915 0000:00:02.0: [drm] plasmashell[3461] context reset due to GPU hang [ 586.929534] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc7b, in kwin_x11 [3427] [ 586.929859] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [ 587.033116] i915 0000:00:02.0: [drm] kwin_x11[3427] context reset due to GPU hang -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1190286] New: Kernel 5.14 freezes in conjunction with Dell Docking Station
by bugzilla_noreply＠suse.com 19 Jan '22

19 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1190286 Bug ID: 1190286 Summary: Kernel 5.14 freezes in conjunction with Dell Docking Station 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: felix.niederwanger(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 852364 --> http://bugzilla.opensuse.org/attachment.cgi?id=852364&action=edit Screenshot of frozen tty1 After the recent update to the 5.14 kernel, my Dell Latitude 7290 Laptop freezes on system startup after like 30 seconds. I could login via the display manager and even open a terminal and then the system froze. I could still move the mouse, but the terminal and everything else was stuck. I could switch to tty1 and tried to login as root there, but was stuck after the password prompt (See attached Screenshot). After about 5 minutes I had to forcefully terminate the system. I did a full system rollback to the previous snapshot (including Kernel 5.13), then installed all updates except the new kernel and rebooted. The system behaves nicely. Then I updated the Kernel as well, rebooted the Laptop and it was frozen again. The issue only happens when the Laptop is connected to the Dell Docking station. When disconnected from the Dock, it behaves nicely. When the system is stuck, disconnecting it from the docking station and waiting a bit also help to unfreeze the system. After reconnecting, the system remains responsive and does not freeze again (I'm writing on it right now). I also restarted the Docking Station but this had no effect at all. The Laptop was still freezing. -- You are receiving this mail because: You are the assignee for the bug.

1 29

[Bug 1191929] New: NVMe SSD slow since openSUSE-LEAP-15.3 (especially with cryptsetup / dm-crypt device)
by bugzilla_noreply＠suse.com 17 Jan '22

17 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1191929 Bug ID: 1191929 Summary: NVMe SSD slow since openSUSE-LEAP-15.3 (especially with cryptsetup / dm-crypt device) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: duge(a)pre-sense.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I got a system with a NVMe SSD, whose performance with dm-crypt dropped from > 200 MB/s to below 2 MB/s from openSUSE-15.2 to openSUSE-15.3. Test procedure: dd oflag=direct bs="$((64 * 1024 * 1024))" count="$((16 * 1024 / 64))" if=dev/zero of=/dev/nvme0n1 dd oflag=sync bs="$((64 * 1024 * 1024))" count="$((16 * 1024 / 64))" if=dev/zero of=/dev/nvme0n1 cryptsetup --cipher "aes-cbc-essiv:sha256" create crypt_test /dev/nvme0n1 dd oflag=direct bs="$((64 * 1024 * 1024))" count="$((16 * 1024 / 64))" if=dev/zero of=/dev/mapper/crypt_test dd oflag=sync bs="$((64 * 1024 * 1024))" count="$((16 * 1024 / 64))" if=dev/zero of=/dev/mapper/crypt_test For oflag=direct openSUSE 15.2 and 15.3 both write with over 800 MB/s to /dev/nvme0n1 and over 300 MB/s to /dev/mapper/crypt_test. openSUSE-15.2 will write with over 600 MB/s to /dev/nvme0n1 and over 200 MB/s to /dev/mapper/crypt_test openSUSE-15.3 will write with 100 MB/s to /dev/nvme0n1 and less than 2 MB/s to /dev/mapper/crypt_test. Finally an "mkfs.ext4 /dev/mapper/crypt_test" takes more than 20 minutes and "iotop" shows even less I/O than 1 MB/s! Tumbleweed-x86_64-Snapshot20211019 (Linux-5.14.11) performs like openSUSE-15.2 or even better. localhost:~ # grep PRETTY /etc/os-release PRETTY_NAME="openSUSE Leap 15.3" localhost:~ # lsblk /dev/nvme0n1 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT nvme0n1 259:0 0 238,5G 0 disk localhost:~ # lspci -v -d 1344:5410 04:00.0 Non-Volatile memory controller: Micron Technology Inc Device 5410 (rev 01) (prog-if 02 [NVM Express]) Subsystem: Micron Technology Inc Device 0100 Flags: bus master, fast devsel, latency 0, IRQ 16, NUMA node 0 Memory at a2100000 (64-bit, non-prefetchable) [size=16K] Capabilities: [80] Express Endpoint, MSI 00 Capabilities: [d0] MSI-X: Enable+ Count=32 Masked- Capabilities: [e0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [f8] Power Management version 3 Capabilities: [100] Vendor Specific Information: ID=1556 Rev=1 Len=008 <?> Capabilities: [108] Latency Tolerance Reporting Capabilities: [110] L1 PM Substates Capabilities: [200] Advanced Error Reporting Capabilities: [300] #19 Kernel driver in use: nvme Kernel modules: nvme localhost:~ # smartctl -a /dev/nvme0n1 [...] === START OF INFORMATION SECTION === Model Number: Micron_2200_MTFDHBA256TCK [...] Firmware Version: P1MU003 PCI Vendor/Subsystem ID: 0x1344 IEEE OUI Identifier: 0x00a075 Controller ID: 0 Number of Namespaces: 1 Namespace 1 Size/Capacity: 256.060.514.304 [256 GB] Namespace 1 Formatted LBA Size: 512 Namespace 1 IEEE EUI-64: 00a075 012cd592d5 [...] -- You are receiving this mail because: You are the assignee for the bug.

1 16

[kernel-bugs] [Bug 1173294] New: iwlwifi: TX on unused queue 5 WARNING: tx.c:2346 iwl_trans_pcie_tx+0xa1e/0x1150
by bugzilla_noreply＠suse.com 17 Jan '22

17 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1173294 Bug ID: 1173294 Summary: iwlwifi: TX on unused queue 5 WARNING: tx.c:2346 iwl_trans_pcie_tx+0xa1e/0x1150 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ddiss(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This looks similar to: https://bugzilla.kernel.org/show_bug.cgi?id=204643 I hit the following WARNING while playing with network manager's new activate hotspot UI functionality and then disabling all radio (nmcli radio wifi off): [ 1157.323257] wlan1: deauthenticating from 34:31:XX:XX:XX:XX by local choice (Reason: 3=DEAUTH_LEAVING) [ 1157.323301] ------------[ cut here ]------------ [ 1157.323302] TX on unused queue 5 [ 1157.323343] WARNING: CPU: 3 PID: 6784 at ../drivers/net/wireless/intel/iwlwifi/pcie/tx.c:2346 iwl_trans_pcie_tx+0xa1e/0x1150 [iwlwifi] [ 1157.323344] Modules linked in: tun ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 ebtable_nat ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptablet [ 1157.323376] snd_hda_core dell_smm_hwmon fat kvm snd_hwdep dell_wmi dell_smbios irqbypass iwlwifi dcdbas joydev snd_pcm snd_timer sparse_keymap mei_me cfg80211 dell_wmi_d] [ 1157.323412] CPU: 3 PID: 6784 Comm: kworker/3:1 Not tainted 5.3.18-lp152.19-default #1 openSUSE Leap 15.2 (unreleased) [ 1157.323413] Hardware name: Dell Inc. Latitude E7450/0YGN55, BIOS A21 05/16/2019 [ 1157.323434] Workqueue: events cfg80211_rfkill_sync_work [cfg80211] [ 1157.323444] RIP: 0010:iwl_trans_pcie_tx+0xa1e/0x1150 [iwlwifi] [ 1157.323447] Code: 80 3d 2b 65 03 00 00 b8 ea ff ff ff 0f 85 25 f8 ff ff 89 ce 48 c7 c7 49 6e d8 c0 89 04 24 c6 05 0d 65 03 00 01 e8 42 94 33 e1 <0f> 0b 8b 04 24 e9 03 f8 c [ 1157.323448] RSP: 0018:ffff9f66404bf7f0 EFLAGS: 00010282 [ 1157.323449] RAX: 0000000000000000 RBX: 0000000000000005 RCX: 0000000000000006 [ 1157.323450] RDX: 0000000000000007 RSI: 0000000000000096 RDI: ffff93915e399a10 [ 1157.323451] RBP: ffff939155e59e28 R08: 000000000000065e R09: 0000000000000001 [ 1157.323452] R10: 0000000000000005 R11: 0000000000000001 R12: ffff9390f1cc4b00 [ 1157.323453] R13: 0000000000000005 R14: 0000000000000037 R15: ffff9391566683e8 [ 1157.323454] FS: 0000000000000000(0000) GS:ffff93915e380000(0000) knlGS:0000000000000000 [ 1157.323455] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 1157.323456] CR2: 00007f8e2af0a000 CR3: 00000002ba00a005 CR4: 00000000003606e0 [ 1157.323457] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 1157.323458] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 1157.323459] Call Trace: [ 1157.323473] ? iwl_mvm_set_tx_cmd+0x1a2/0x480 [iwlmvm] [ 1157.323483] ? iwl_mvm_get_tx_rate.isra.21+0x44/0xe0 [iwlmvm] [ 1157.323491] ? iwl_mvm_get_tx_ant+0x43/0x80 [iwlmvm] [ 1157.323499] ? iwl_mvm_set_tx_params+0x11f/0x4e0 [iwlmvm] [ 1157.323507] iwl_mvm_tx_mpdu+0x207/0x600 [iwlmvm] [ 1157.323516] iwl_mvm_tx_skb_sta+0x1ed/0x480 [iwlmvm] [ 1157.323524] iwl_mvm_tx_skb+0x17/0x40 [iwlmvm] [ 1157.323532] iwl_mvm_mac_itxq_xmit+0x7a/0xf0 [iwlmvm] [ 1157.323559] ieee80211_queue_skb+0x2da/0x420 [mac80211] [ 1157.323582] ieee80211_tx+0xd9/0x130 [mac80211] [ 1157.323604] __ieee80211_tx_skb_tid_band+0x58/0x70 [mac80211] [ 1157.323627] ieee80211_send_deauth_disassoc+0xfd/0x130 [mac80211] [ 1157.323649] ieee80211_set_disassoc+0x3a0/0x5e0 [mac80211] [ 1157.323679] ieee80211_mgd_deauth+0x113/0x230 [mac80211] [ 1157.323701] cfg80211_mlme_deauth+0xaf/0x1c0 [cfg80211] [ 1157.323720] cfg80211_mlme_down+0x7b/0x90 [cfg80211] [ 1157.323739] cfg80211_disconnect+0x11f/0x1d0 [cfg80211] [ 1157.323754] cfg80211_leave+0x26/0x40 [cfg80211] [ 1157.323767] cfg80211_netdev_notifier_call+0x258/0x5b0 [cfg80211] [ 1157.323774] ? iwl_mvm_set_tim+0x50/0x50 [iwlmvm] [ 1157.323794] ? __iterate_interfaces+0x78/0x110 [mac80211] [ 1157.323800] ? iwl_mvm_set_tim+0x50/0x50 [iwlmvm] [ 1157.323817] ? __iterate_interfaces+0x78/0x110 [mac80211] [ 1157.323831] ? ieee80211_iterate_active_interfaces_atomic+0xd/0x10 [mac80211] [ 1157.323838] ? iwl_mvm_recalc_multicast+0x45/0x70 [iwlmvm] [ 1157.323841] ? rtnl_is_locked+0x11/0x20 [ 1157.323843] ? inetdev_event+0x46/0x5c0 [ 1157.323850] ? iwl_mvm_configure_filter+0x61/0x80 [iwlmvm] [ 1157.323853] notifier_call_chain+0x47/0x70 [ 1157.323855] __dev_close_many+0x5f/0x110 [ 1157.323857] dev_close_many+0x7c/0x120 [ 1157.323859] dev_close.part.104+0x3e/0x70 [ 1157.323874] cfg80211_shutdown_all_interfaces+0x6d/0xc0 [cfg80211] [ 1157.323886] cfg80211_rfkill_sync_work+0x29/0x30 [cfg80211] [ 1157.323889] process_one_work+0x1f4/0x3e0 [ 1157.323892] worker_thread+0x2d/0x3e0 [ 1157.323894] ? process_one_work+0x3e0/0x3e0 [ 1157.323895] kthread+0x10d/0x130 [ 1157.323897] ? kthread_park+0xa0/0xa0 [ 1157.323899] ret_from_fork+0x35/0x40 [ 1157.323902] ---[ end trace 3217541a75ee82c3 ]--- I've not been able to reproduce it so far, but will update when/if I get a clear procedure. -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 1193142] New: usb mouse and usb keyboard not recognized by sddm
by bugzilla_noreply＠suse.com 13 Jan '22

13 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1193142 Bug ID: 1193142 Summary: usb mouse and usb keyboard not recognized by sddm Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: PC OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jdd(a)dodin.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- since a week or so, I have no more working usb mouse and keyboard (separate, wired usb ones) on my Leap 15.3. ASUS laptop N550JK. The curious thing is that if I first boot an old 15.1 install, mouse and keyboard works, and if I just reboot on 15.3 (not power off), mouse and keyboard start working in 15.3. So on the morning I have to first start 15.1 (no need to login), and reboot on 15.3. odd. of course the two devices used to work since ages and still works after the double boot. Looks like some thing on the device is not correctly initialized (firmware?) * bug on last kernel, 5.3.18-59.34-default * no bug on kernel 5.3.18-58.10-default I didn't test all the kernels between these two -- You are receiving this mail because: You are the assignee for the bug.

1 10