March 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[kernel-bugs] [Bug 1173819] New: 'BUG: workqueue lockup' on ThunderX2 machines with kernel 4.12.14 in OBS
by bugzilla_noreply＠suse.com 22 Oct '21

22 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1173819 Bug ID: 1173819 Summary: 'BUG: workqueue lockup' on ThunderX2 machines with kernel 4.12.14 in OBS Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de CC: adrian.schroeter(a)suse.com, afaerber(a)suse.com, dmueller(a)suse.com Found By: --- Blocker: --- obs-arm-7, -8 and -9 are often down in OBS these days due to kernel issues. One issue is a workqueue lockup: BUG: workqueue lockup - pool cpus=59 node=0 flags=0x0 nice=0 stuck for 92265s! -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1182318] New: Superfluous mkinitrd / dracut calls at kernel post scriptlet
by bugzilla_noreply＠suse.com 12 Aug '21

12 Aug '21

https://bugzilla.suse.com/show_bug.cgi?id=1182318 Bug ID: 1182318 Summary: Superfluous mkinitrd / dracut calls at kernel post scriptlet 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: tiwai(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The current kernel rpm scriptlets have some room for optimization. Most notably, the initrd creation and boot loader setup are called at %post, and those can be postponed to %posttrans instead. The problem of multiple initrd creations and boot loader setups becomes more significant when another package touching initrd (e.g. coreutils) is installed together, or when the split kernel (kernel-default-extra) is installed together. As the initrd and the bootloeader setup are triggered in %post from both kernel-default and kernel-default-extra while the re-creation of the all initrd is triggered by another package update, this will end up two more extra calls that are superfluous. In addition to the above, the pre.sh script contains a few almost superfluous checks no one really cares. We may clean them up, too. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[kernel-bugs] [Bug 1175105] New: mdadm doesn't except partition for --add because of "dirt" in that partition of a fresh gpt table
by bugzilla_noreply＠suse.com 03 Aug '21

03 Aug '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1175105 Bug ID: 1175105 Summary: mdadm doesn't except partition for --add because of "dirt" in that partition of a fresh gpt table Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ralf(a)czekalla.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I'm about to migrate an important central private nextcloud server to 15.2. I'm use RAID1 for all my partitions and benefit from that with easy made clones with the help of mdadm by growing the number of raid-devices and adding a refreshed SSD with a new gpt partition table and cloned partitions descriptions. This worked for most of the six partitions but one. (It's not the first installation I transform with this idea. Did these processes already several times) This faulty one showed weird error messages I couldn't find a real good reason for, like ... ...on console: # mdadm --verbose /dev/md2 --add /dev/sdc5 mdadm: add new device failed for /dev/sdc5 as 4: Invalid argument # mdadm -E /dev/sdc5 /dev/sdc5: Magic : a92b4efc Version : 1.0 Feature Map : 0x9 Array UUID : 94bbbcd3:ad4d1b0b:dcd4d548:1af16050 Name : any:2 Creation Time : Fri Feb 2 20:09:03 2018 Raid Level : raid1 Raid Devices : 3 Avail Dev Size : 83892192 sectors (40.00 GiB 42.95 GB) Array Size : 41945984 KiB (40.00 GiB 42.95 GB) Used Dev Size : 83891968 sectors (40.00 GiB 42.95 GB) Super Offset : 83892208 sectors Unused Space : before=0 sectors, after=224 sectors State : active Device UUID : c9e17312:0069d580:42782958:8817e0f7 Internal Bitmap : -16 sectors from superblock Update Time : Mon Aug 10 18:09:21 2020 Bad Block Log : 512 entries available at offset -8 sectors - bad blocks present. Checksum : 7b5d72a - correct Events : 0 Device Role : spare Array State : AA. ('A' == active, '.' == missing, 'R' == replacing) First I was blinded by the "bad blocks present", but all devices checked out perfectly healthy in smart and also extended device scans didn't show any problems. Took me several hours to get through all this. dmesg: md: sdc5 does not have a valid v1.0 superblock, not importing! md: md_import_device returned -22 Also tried to --zero-superblock the partition of course. No change of behavior and still the above error message in dmesg remained. At the end I found a surprising hint on serverfault.com (https://serverfault.com/questions/696392/how-to-add-disk-back-to-raid-and-r…) from Oct. 2015 with a similar behavior that suggested to clean-up of the partition first with dd writing zeros (dd if=/dev/zero of=/dev/sdc5 status=progress) and try again later to add the last seemingly faulty partition. And long story short, this really worked. Somehow mdadm - and md behind - is choking on some dirt inside of partition blocks from old content before the disk/ssd was wiped with a new gpt partition table. (Of course with SSDs you try to prevent unnecessary writes and wiping every block of a disk first) I'm using md device type 1.0 here (in contrast to the serverfault.com case), where the RAID/md setup data is stored at the end of the partition. I had to wipe exactly this area at the end of the partition to add it afterwards successfully. Of course, no effect when doing this at the beginning of the partition (mentioned in the serverfault.com case) where md type 1.2 stores the md setup data. I think after 5 years this might need a clean up in mdadm or md device management. At least the error message should suggest to clean the partition first instead of this error message in dmesg. Also the --zero-superblock should wipe out the dirt beneath the superblock and not seemingly let some stuff leak here. Thanks Ralf -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1183598] New: kernel bug when plugging USB audio device
by bugzilla_noreply＠suse.com 11 Jul '21

11 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1183598 Bug ID: 1183598 Summary: kernel bug when plugging USB audio device Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: nmoreychaisemartin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When plugging my headphones (Senheiser PXC 550) to my workstation (or booting with it plugged), snd_usb_audio triggers a BUG: [ 17.298229] BUG: kernel NULL pointer dereference, address: 0000000000000012 [ 17.298232] #PF: supervisor read access in kernel mode [ 17.298233] #PF: error_code(0x0000) - not-present page [ 17.298234] PGD 0 P4D 0 [ 17.298236] Oops: 0000 [#1] SMP PTI [ 17.298238] CPU: 6 PID: 548 Comm: systemd-udevd Tainted: G N 5.3.18-51-default #1 SLE15-SP3 [ 17.298239] Hardware name: Dell Inc. Precision Tower 5810/0HHV7N, BIOS A34 10/19/2020 [ 17.298253] RIP: 0010:usb_audio_probe+0x28a/0xcf0 [snd_usb_audio] [ 17.298254] Code: 04 48 89 df e8 77 7b 01 00 84 c0 0f 84 6f 06 00 00 4d 85 ed 74 14 41 80 7d 14 00 74 0d 48 8b 74 24 08 48 89 df e8 06 9f 01 00 <41> 0f b7 45 12 48 8b 74 24 08 66 89 83 9c 00 00 00 48 63 03 48 89 [ 17.298256] RSP: 0018:ffffbbff404fba98 EFLAGS: 00010246 [ 17.298257] RAX: 0000000000000000 RBX: ffffa04340aef8b8 RCX: 0000000000000000 [ 17.298258] RDX: ffffa04349cf8088 RSI: 0000000000000000 RDI: ffffa04348a2b988 [ 17.298259] RBP: ffffffffc10cff40 R08: ffffa04349cf8508 R09: 0000000000800000 [ 17.298259] R10: ffffbbff404fba98 R11: 00000000000323e0 R12: ffffffffc10cff40 [ 17.298260] R13: 0000000000000000 R14: ffffa04343c4b8a0 R15: ffffa04340aef97c [ 17.298261] FS: 00007feda983b380(0000) GS:ffffa0434fb80000(0000) knlGS:0000000000000000 [ 17.298262] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 17.298263] CR2: 0000000000000012 CR3: 0000000808b86006 CR4: 00000000001706e0 [ 17.298264] Call Trace: [ 17.298270] ? ktime_get_mono_fast_ns+0x53/0xa0 [ 17.298282] usb_probe_interface+0x13c/0x2f0 [usbcore] [ 17.298285] really_probe+0xef/0x430 [ 17.298287] driver_probe_device+0x110/0x120 [ 17.298288] device_driver_attach+0x4f/0x60 [ 17.298290] __driver_attach+0x51/0x130 [ 17.298291] ? device_driver_attach+0x60/0x60 [ 17.298293] bus_for_each_dev+0x76/0xc0 [ 17.298294] bus_add_driver+0x144/0x220 [ 17.298296] driver_register+0x5b/0xf0 [ 17.298302] usb_register_driver+0x7c/0x140 [usbcore] [ 17.298303] ? 0xffffffffc10e1000 [ 17.298306] do_one_initcall+0x46/0x1f4 [ 17.298308] ? kmem_cache_alloc_trace+0x18f/0x270 [ 17.298309] ? do_init_module+0x22/0x22f [ 17.298311] do_init_module+0x5b/0x22f [ 17.298313] load_module+0x1d81/0x2320 [ 17.298316] ? __do_sys_init_module+0x160/0x190 [ 17.298319] ? _cond_resched+0x15/0x40 [ 17.298320] __do_sys_init_module+0x160/0x190 [ 17.298323] do_syscall_64+0x5b/0x1e0 [ 17.298325] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 17.298326] RIP: 0033:0x7feda86726da [ 17.298328] Code: 48 8b 0d b9 c7 2c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 86 c7 2c 00 f7 d8 64 89 01 48 [ 17.298329] RSP: 002b:00007ffdd2e89b28 EFLAGS: 00000246 ORIG_RAX: 00000000000000af [ 17.298330] RAX: ffffffffffffffda RBX: 00005596f8340db0 RCX: 00007feda86726da [ 17.298331] RDX: 00007feda8fd1f9d RSI: 000000000008dbe0 RDI: 00007fed9fd01010 [ 17.298332] RBP: 00007feda8fd1f9d R08: 0000000000000003 R09: 00007fed9fd01000 [ 17.298332] R10: 0000000000000004 R11: 0000000000000246 R12: 00007fed9fd01010 [ 17.298333] R13: 00005596f809d5e0 R14: 00005596f80968f0 R15: 00005596f834c320 [ 17.298334] Modules linked in: pcspkr snd_hda_codec snd_hda_core mxm_wmi(NN) snd_usb_audio(+) pcc_cpufreq(-) snd_soc_core snd_usbmidi_lib snd_hwdep snd_rawmidi joydev i2c_i801 lpc_ich snd_compress snd_seq_device mc snd_pcm_dmaengine snd_pcm snd_timer snd soundcore mei_me e1000e mei button fuse configfs btrfs libcrc32c xor hid_generic usbhid raid6_pq sr_mod sd_mod cdrom t10_pi amdgpu iommu_v2 gpu_sched i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops xhci_pci cec xhci_hcd rc_core ahci drm crc32c_intel ehci_pci libahci ehci_hcd ata_generic libata usbcore wmi sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua scsi_mod [ 17.298352] Supported: No, Unsupported modules are loaded [ 17.298354] CR2: 0000000000000012 [ 17.298355] ---[ end trace 363a4962d4d49222 ]--- [ 17.298361] RIP: 0010:usb_audio_probe+0x28a/0xcf0 [snd_usb_audio] [ 17.298362] Code: 04 48 89 df e8 77 7b 01 00 84 c0 0f 84 6f 06 00 00 4d 85 ed 74 14 41 80 7d 14 00 74 0d 48 8b 74 24 08 48 89 df e8 06 9f 01 00 <41> 0f b7 45 12 48 8b 74 24 08 66 89 83 9c 00 00 00 48 63 03 48 89 [ 17.298363] RSP: 0018:ffffbbff404fba98 EFLAGS: 00010246 [ 17.298364] RAX: 0000000000000000 RBX: ffffa04340aef8b8 RCX: 0000000000000000 [ 17.298365] RDX: ffffa04349cf8088 RSI: 0000000000000000 RDI: ffffa04348a2b988 [ 17.298365] RBP: ffffffffc10cff40 R08: ffffa04349cf8508 R09: 0000000000800000 [ 17.298366] R10: ffffbbff404fba98 R11: 00000000000323e0 R12: ffffffffc10cff40 [ 17.298367] R13: 0000000000000000 R14: ffffa04343c4b8a0 R15: ffffa04340aef97c [ 17.298368] FS: 00007feda983b380(0000) GS:ffffa0434fb80000(0000) knlGS:0000000000000000 [ 17.298369] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 17.298369] CR2: 0000000000000012 CR3: 0000000808b86006 CR4: 00000000001706e0 [(master) nmorey@portia:master]$ rpm -q kernel-default-5.3.18-51.2 kernel-default-5.3.18-51.2.x86_64 [(master) nmorey@portia:master]$ uname -a Linux portia 5.3.18-51-default #1 SMP Wed Mar 10 15:14:00 UTC 2021 (5219769) x86_64 x86_64 x86_64 GNU/Linux Systems seems working after that otherwise apart from: - No USB output device available - lsusb just get stuck -- You are receiving this mail because: You are the assignee for the bug.

1 17

[Bug 1183843] New: iSCSI server reboots when accessing exported DVD drive
by bugzilla_noreply＠suse.com 11 Jul '21

11 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1183843 Bug ID: 1183843 Summary: iSCSI server reboots when accessing exported DVD drive Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jgross(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I've exported a DVD drive via iSCSI on a server running latest openSUSE 15.2: targetcli ls o- / ..................................................................... [...] o- backstores .......................................................... [...] | o- block .............................................. [Storage Objects: 0] | o- fileio ............................................. [Storage Objects: 0] | o- pscsi .............................................. [Storage Objects: 1] | | o- dvd_backend ...................................... [/dev/sr0 activated] | | o- alua ............................................... [ALUA Groups: 0] | o- ramdisk ............................................ [Storage Objects: 0] | o- rbd ................................................ [Storage Objects: 0] o- iscsi ........................................................ [Targets: 1] | o- iqn.2003-01.org.linux-iscsi.server.x8664:sn.ddcce514ffbd ...... [TPGs: 1] | o- tpg1 .............................................. [gen-acls, no-auth] | o- acls ...................................................... [ACLs: 0] | o- luns ...................................................... [LUNs: 1] | | o- lun0 ........................ [pscsi/dvd_backend (/dev/sr0) (None)] | o- portals ................................................ [Portals: 1] | o- 0.0.0.0:3260 ................................................. [OK] o- loopback ..................................................... [Targets: 0] o- vhost ........................................................ [Targets: 0] o- xen-pvscsi ................................................... [Targets: 0] On client side I can see the drive: lsscsi [2:0:0:0] disk ATA WDC WD20SPZX-75U 1A01 /dev/sda [3:0:0:0] cd/dvd HL-DT-ST DVD+-RW GU90N A1C3 /dev/sr0 When trying to use it (e.g. via vlc or trying to do "mount /dev/sr0 /mnt") the server just reboots after the DVD drive spinning up without any message on the console. -- You are receiving this mail because: You are the assignee for the bug.

1 16

[Bug 1183839] New: kernel 5.11.{4,6} RIP: 0010:kobject_put+0x19/0x1d0 on Dell Precision M7510
by bugzilla_noreply＠suse.com 07 Jul '21

07 Jul '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1183839 Bug ID: 1183839 Summary: kernel 5.11.{4,6} RIP: 0010:kobject_put+0x19/0x1d0 on Dell Precision M7510 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: bruno(a)ioda-net.ch QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- As asked in https://bugzilla.opensuse.org/show_bug.cgi?id=1182377 I open a new bug since a new RIP appear. See attachements for more information about the hardware (On this system bios is up to date to last revision Dell has offered) As the bios allow it, only the nvidia gpu is used by disabling intel gpu part. All mass storage are fully encrypted and opened during grub2 operation This crash start to be seen on 5.11.4 Extract of the captured crash Mar 20 16:15:19 qt-kt kernel: CPU: 6 PID: 739 Comm: systemd-udevd Not tainted 5.11.6-1-default #1 openSUSE Tumbleweed Mar 20 16:15:19 qt-kt kernel: Hardware name: Dell Inc. Precision 7510/0YH43H, BIOS 1.21.3 08/04/2020 Mar 20 16:15:19 qt-kt kernel: RIP: 0010:kobject_put+0x19/0x1d0 Mar 20 16:15:19 qt-kt kernel: iwlwifi 0000:02:00.0: loaded firmware version 36.ad812ee0.0 8000C-36.ucode op_mode iwlmvm Mar 20 16:15:19 qt-kt kernel: pstore: Efi pstore disabled, enforce via pstore.backend=efi Mar 20 16:15:19 qt-kt kernel: pstore: On a broken BIOS, this can severely harm your system Mar 20 16:15:19 qt-kt kernel: pstore: Only enable efi based pstore when you know what you are doing Mar 20 16:15:19 qt-kt kernel: Bluetooth: HCI device and connection manager initialized Mar 20 16:15:19 qt-kt kernel: Code: 48 c7 c7 08 34 86 92 e8 35 b6 fe ff eb d6 0f 1f 00 48 85 ff 0f 84 b4 00 00 00 41 56 41 55 41 54 55 48 89 fd 53 bb ff ff ff ff <f6> 45 3c 01 0f 84 80 00 00 00 48 8d 7d 38 89 d8 f0 0f c1 45 38 83 Mar 20 16:15:19 qt-kt kernel: usb 2-2: Qualcomm USB modem converter now attached to ttyUSB1 Mar 20 16:15:19 qt-kt kernel: Bluetooth: HCI socket layer initialized Mar 20 16:15:19 qt-kt kernel: RSP: 0018:ffffacd6c07fbd98 EFLAGS: 00010202 Mar 20 16:15:19 qt-kt kernel: RAX: 0000000000000000 RBX: 00000000ffffffff RCX: 0000000000000000 Mar 20 16:15:19 qt-kt kernel: RDX: 0000000000000001 RSI: 0000000000000000 RDI: 1cc78e3ae6c3a8ae Mar 20 16:15:19 qt-kt kernel: RBP: 1cc78e3ae6c3a8ae R08: ffff8f77f8fe8900 R09: ffff8f74c01f1e58 Mar 20 16:15:19 qt-kt kernel: R10: 000000000000001f R11: ffff8f74c4a89488 R12: 1cc78e3ae6c3a8ae Mar 20 16:15:19 qt-kt kernel: R13: 0000000000007ea3 R14: ffffacd6c07fbe80 R15: 0000000000010000 Mar 20 16:15:19 qt-kt kernel: FS: 00007f984fb7b940(0000) GS:ffff8f8404580000(0000) knlGS:0000000000000000 Mar 20 16:15:19 qt-kt kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 20 16:15:19 qt-kt kernel: CR2: 000055e078f036a8 CR3: 00000001037d0004 CR4: 00000000003706e0 Mar 20 16:15:19 qt-kt kernel: Bluetooth: L2CAP socket layer initialized Mar 20 16:15:19 qt-kt kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Mar 20 16:15:19 qt-kt kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Mar 20 16:15:19 qt-kt kernel: Call Trace: Mar 20 16:15:19 qt-kt kernel: kset_unregister+0x25/0x40 Mar 20 16:15:19 qt-kt kernel: ? 0xffffffffc0ea2000 Mar 20 16:15:19 qt-kt kernel: qcserial 2-2:1.3: Qualcomm USB modem converter detected Mar 20 16:15:19 qt-kt kernel: sysman_init+0x20a/0x1000 [dell_wmi_sysman] Mar 20 16:15:19 qt-kt kernel: do_one_initcall+0x44/0x1d0 Mar 20 16:15:19 qt-kt kernel: ? kmem_cache_alloc_trace+0xfe/0x250 Mar 20 16:15:19 qt-kt kernel: do_init_module+0x5c/0x270 Mar 20 16:15:19 qt-kt kernel: __do_sys_init_module+0x13b/0x1c0 Mar 20 16:15:19 qt-kt kernel: do_syscall_64+0x33/0x80 Mar 20 16:15:19 qt-kt kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Mar 20 16:15:19 qt-kt kernel: RIP: 0033:0x7f98507ee15e Mar 20 16:15:19 qt-kt kernel: Code: 48 8b 0d 15 1d 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e2 1c 0c 00 f7 d8 64 89 01 48 Mar 20 16:15:19 qt-kt kernel: RSP: 002b:00007ffede5cf4c8 EFLAGS: 00000246 ORIG_RAX: 00000000000000af Mar 20 16:15:19 qt-kt kernel: RAX: ffffffffffffffda RBX: 000055e078640d00 RCX: 00007f98507ee15e Mar 20 16:15:19 qt-kt kernel: RDX: 00007f985090e3a3 RSI: 0000000000017ea3 RDI: 000055e078651b70 Mar 20 16:15:19 qt-kt kernel: RBP: 000055e078651b70 R08: 000055e078640140 R09: 0000000000000003 Mar 20 16:15:19 qt-kt kernel: R10: 000055e5264348e0 R11: 0000000000000246 R12: 00007f985090e3a3 Mar 20 16:15:19 qt-kt kernel: R13: 000055e07844d070 R14: 0000000000000000 R15: 000055e078645d60 Mar 20 16:15:19 qt-kt kernel: Modules linked in: dell_wmi_sysman(+) sparse_keymap efi_pstore dell_wmi_descriptor intel_wmi_thunderbolt wmi_bmof mxm_wmi cdc_ether qcserial(+) bluetooth(+) iwlwifi snd_usbmidi_lib usb_wwan usbnet fjes(-) videodev snd_rawmidi mii usbserial snd_seq_device i2c_i801 joydev mc cfg80211 ecdh_generic mei_me e1000e(+) i2c_smbus ecc processor_thermal_device mei intel_pch_thermal thermal processor_thermal_rfim parport_pc processor_thermal_mbox int3403_thermal processor_thermal_rapl tiny_power_button parport intel_rapl_common dell_smo8800 int3402_thermal intel_soc_dts_iosf int340x_thermal_zone int3400_thermal dell_rbtn button acpi_pad rfkill acpi_thermal_rel ie31200_edac ac nls_iso8859_1 nls_cp437 vfat fat drm fuse configfs hid_logitech_hidpp hid_logitech_dj dm_crypt uas hid_generic usb_storage usbhid rtsx_pci_sdmmc mmc_core nvme crct10dif_pclmul xhci_pci crc32_pclmul xhci_pci_renesas ghash_clmulni_intel xhci_hcd aesni_intel glue_helper crypto_simd cryptd nvme_core serio_raw usbcore Mar 20 16:15:19 qt-kt kernel: rtsx_pci battery video wmi btrfs blake2b_generic libcrc32c crc32c_intel xor raid6_pq dm_mirror dm_region_hash dm_log snd_hda_intel snd_intel_dspcfg soundwire_intel soundwire_generic_allocation snd_soc_core snd_compress snd_pcm_dmaengine soundwire_cadence soundwire_bus snd_hda_codec snd_hwdep snd_hda_core snd_pcm snd_timer snd soundcore l2tp_ppp l2tp_netlink l2tp_core ip6_udp_tunnel udp_tunnel pppox ppp_generic slhc sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua br_netfilter bridge stp llc msr efivarfs Mar 20 16:15:19 qt-kt kernel: ---[ end trace c28276df22413bc9 ]--- -- You are receiving this mail because: You are the assignee for the bug.

1 16

[kernel-bugs] [Bug 1176351] New: Audio device: Intel Corporation Device 02c8: not detected
by bugzilla_noreply＠suse.com 22 Jun '21

22 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1176351 Bug ID: 1176351 Summary: Audio device: Intel Corporation Device 02c8: not detected 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: gp(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I've got a new notebook, Intel chipsets only, where everythings works - except for audio. It appears the audio chip/sound card are not detected by the kernel or initialized. lspci -v has: 00:1f.3 Audio device: Intel Corporation Device 02c8 (prog-if 80) Subsystem: Lenovo Device 22be Flags: fast devsel, IRQ 16, IOMMU group 13 Memory at ea33c000 (64-bit, non-prefetchable) [size=16K] Memory at ea000000 (64-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [80] Vendor Specific Information: Len=14 <?> Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+ Kernel modules: snd_hda_intel, snd_soc_skl, snd_sof_pci # lsmod | grep snd snd 114688 1 thinkpad_acpi soundcore 16384 1 snd # cat /proc/asound/cards --- no soundcards --- # dmesg | grep audio [ 18.072024] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040380 [ 18.072026] sof-audio-pci 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver [ 18.072036] sof-audio-pci 0000:00:1f.3: enabling device (0004 -> 0006) [ 18.072179] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040380 [ 18.072267] sof-audio-pci 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 18.078993] sof-audio-pci 0000:00:1f.3: use msi interrupt mode [ 18.109492] sof-audio-pci 0000:00:1f.3: hda codecs found, mask 5 [ 18.109493] sof-audio-pci 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now [ 18.109497] sof-audio-pci 0000:00:1f.3: DMICs detected in NHLT tables: 4 [ 18.109521] sof-audio-pci 0000:00:1f.3: Direct firmware load for intel/sof/sof-cml.ri failed with error -2 [ 18.109522] sof-audio-pci 0000:00:1f.3: error: request firmware intel/sof/sof-cml.ri failed err: -2 [ 18.109524] sof-audio-pci 0000:00:1f.3: error: failed to load DSP firmware -2 [ 18.110449] sof-audio-pci 0000:00:1f.3: error: sof_probe_work failed err: -2 [ 220.595600] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040380 [ 220.595605] sof-audio-pci 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver [ 220.595786] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040380 [ 220.595899] sof-audio-pci 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 220.601386] sof-audio-pci 0000:00:1f.3: use msi interrupt mode [ 220.630638] sof-audio-pci 0000:00:1f.3: hda codecs found, mask 5 [ 220.630640] sof-audio-pci 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now [ 220.630644] sof-audio-pci 0000:00:1f.3: DMICs detected in NHLT tables: 4 [ 220.630664] sof-audio-pci 0000:00:1f.3: Direct firmware load for intel/sof/sof-cml.ri failed with error -2 [ 220.630666] sof-audio-pci 0000:00:1f.3: error: request firmware intel/sof/sof-cml.ri failed err: -2 [ 220.630669] sof-audio-pci 0000:00:1f.3: error: failed to load DSP firmware -2 [ 220.631004] sof-audio-pci 0000:00:1f.3: error: sof_probe_work failed err: -2 -- You are receiving this mail because: You are the assignee for the bug.

1 15

[Bug 1180058] New: Please don't create /boot/do_purge_kernels on initial install
by bugzilla_noreply＠suse.com 22 Jun '21

22 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1180058 Bug ID: 1180058 Summary: Please don't create /boot/do_purge_kernels on initial install 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: dcermak(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Currently the %post scriptlet of the kernel creates /boot/do_purge_kernels to trigger zypper's kernel purging. Could this be modified so that it only creates this file on upgrades and *not* on fresh installations? Currently this will cause zypper to try to purge old kernels on fresh installations. While that is short, it can cause noticeable delays until zypper can be used again, especially in resource constrained systems. Could the creation of this file be adjusted so that it is only created on upgrades and not on new installations? -- You are receiving this mail because: You are the assignee for the bug.

1 15

[Bug 1180917] New: kernel BUG at mm/huge_memory.c:2144!
by bugzilla_noreply＠suse.com 18 Jun '21

18 Jun '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1180917 Bug ID: 1180917 Summary: kernel BUG at mm/huge_memory.c:2144! Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: azouhr(a)opensuse.org QA Contact: qa-bugs(a)suse.de CC: ihno(a)suse.com, ro(a)suse.de, sarah.kriesch(a)ibm.com Found By: --- Blocker: --- Recently, a number of packages fails to build and instead hangs with the command cc1plus. In a recent build, I found a kernel trace in a hanging worker: [ 608s] [ 596.875979] kernel BUG at mm/huge_memory.c:2144! [ 608s] [ 596.876290] monitor event: 0040 ilc:2 [#1] SMP [ 608s] [ 596.876374] Modules linked in: sha256_s390 sha_common overlay sd_mod t10_pi nls_iso8859_1 nls_cp437 vfat fat virtio_rng rng_core virtio_blk xfs btrfs blake2b_generic xor raid6_pq libcrc32c crc32_vx_s390 reiserfs squashfs fuse dm_snapshot dm_bufio dm_crypt dm_mod binfmt_misc loop sg scsi_mod [ 608s] [ 596.876666] CPU: 1 PID: 2660 Comm: cc1plus Not tainted 5.10.5-1-default #1 openSUSE Tumbleweed [ 608s] [ 596.876750] Hardware name: IBM 2964 N63 400 (KVM/Linux) [ 608s] [ 596.876797] Krnl PSW : 0704e00180000000 00000000e33fb9ea (__split_huge_pmd+0x62a/0xc30) [ 608s] [ 596.877158] R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3 [ 608s] [ 596.877328] Krnl GPRS: 0000000000000000 00000000b2b40215 0000000003c91000 fffffffffffff800 [ 608s] [ 596.877408] 0000000081691a00 00000000f2440237 00000000000000c0 0000000000000000 [ 608s] [ 596.877493] 0000000081691800 000003d083c91030 0000000086d81d48 000003ff71a40000 [ 608s] [ 596.877567] 0000000086c1c000 00000000e47c4268 00000000e33fb748 000003e003ef3a80 [ 608s] [ 596.877652] Krnl Code: 00000000e33fb9de: a71f0400 cghi %r1,1024 [ 608s] [ 596.877652] 00000000e33fb9e2: a784ff18 brc 8,00000000e33fb812 [ 608s] [ 596.877652] #00000000e33fb9e6: af000000 mc 0,0 [ 608s] [ 596.877652] >00000000e33fb9ea: a55b0602 oill %r5,1538 [ 608s] [ 596.877652] 00000000e33fb9ee: a7f4ff06 brc 15,00000000e33fb7fa [ 608s] [ 596.877652] 00000000e33fb9f2: e32010080004 lg %r2,8(%r1) [ 608s] [ 596.877652] 00000000e33fb9f8: a7210001 tmll %r2,1 [ 608s] [ 596.877652] 00000000e33fb9fc: a77401f1 brc 7,00000000e33fbdde [ 608s] [ 596.878162] Call Trace: [ 608s] [ 596.878190] [<00000000e33fb9ea>] __split_huge_pmd+0x62a/0xc30 [ 608s] [ 596.878257] ([<00000000e33fb6ca>] __split_huge_pmd+0x30a/0xc30) [ 608s] [ 596.878327] [<00000000e3379116>] zap_p4d_range+0x246/0xbb0 [ 608s] [ 596.878396] [<00000000e33808f6>] zap_page_range+0x1a6/0x2e0 [ 608s] [ 596.878458] [<00000000e33b2e14>] do_madvise.part.0+0x844/0xc70 [ 608s] [ 596.879153] [<00000000e33b32a8>] __s390x_sys_madvise+0x68/0x80 [ 608s] [ 596.879247] [<00000000e3c676bc>] system_call+0xe0/0x2ac [ 608s] [ 596.879347] Last Breaking-Event-Address: [ 608s] [ 596.879390] [<00000000e33fb9b2>] __split_huge_pmd+0x5f2/0xc30 [ 608s] [ 596.879465] ---[ end trace 50ad5147a244f7d2 ]--- I don't know if this is related boo#1163684 -- You are receiving this mail because: You are the assignee for the bug.

1 3

[kernel-bugs] [Bug 1177009] New: Leap 15.2 stopped working in KVM with ovmf-ia32 firmware
by bugzilla_noreply＠suse.com 16 Jun '21

16 Jun '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1177009 Bug ID: 1177009 Summary: Leap 15.2 stopped working in KVM with ovmf-ia32 firmware Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: nwr10cst-oslnx(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0 Build Identifier: I'm reporting as a kernel bug, but it might be a bug elsewhere. And yes, I know that this is not a supported configuration. Situation: I have both Leap 15.2 and Tumbleweed installed side by side in a KVM virtual machine, using 32-bit efi for booting. Both Leap and Tumbleweed are 64-bit. I originally setup this VM under Leap 15.0 (as KVM host machine). Everything had been working well. However, I recently tried to boot the Leap 15.2 system in that VM, and it failed to boot. I see the kernel and initrd being loaded. And then there is a reset and I get back to the boot screen. However, Tumbleweed continues to boot without a problem on that virtual machine. I am booting with "grub2-i386-efi", which is installed for both Tumbleweed and for Leap 15.2. This does not appear to be a grub2 problem, because the kernel and initrd are being loaded. Before today, I most recently booted Leap 15.2 on Sept 22, and I updated it at that time. I then rebooted (successfully) to check after the update. I have not been able to boot since, until my workaround today. The KVM host is also running Leap 15.2, and I did apply some updates since Sept 22. My guess is that one of those updates affected how the virtualization is working. I have a similar install of Leap 15.2 on an external USB drive, and I have that setup so that it can boot with legacy BIOS, with 64-bit efi and with 32-bit efi. Testing with that, it also fails to boot the same virtual machine with 32-bit efi, bit it successfully boots with either legacy BIOS or with 64-bit efi. So it looks as if whatever is going wrong has to do with communication between the kernel and the 32-bit efi firmware. Booting the virtual machine to Tumbleweed, then setting up for rescue/chroot, I have installed kernel 5.8.11-1.gf4bb27a-default from the stable kernels repo. And now Leap 15.2 does boot successfully with that kernel. It does not boot with any of the 5.3.x kernels for Leap 15.2 that I have tested. Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug.

1 21