February 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1193139] New: [x86_64, 32-bit] mpx support broken
by bugzilla_noreply＠suse.com 07 May '22

07 May '22

https://bugzilla.suse.com/show_bug.cgi?id=1193139 Bug ID: 1193139 Summary: [x86_64, 32-bit] mpx support broken Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: tdevries(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Consider test-case mpx-out-of-bounds.c ( https://01.org/blogs/2016/intel-mpx-linux ): ... $ cat mpx-out-of-bounds.c #include <string.h> #include <stdio.h> #include <stdlib.h> #define noinline __attribute__((noinline)) char dog[] = "dog"; char password[] = "secr3t"; noinline char dog_letter(int nr) { return dog[nr]; } int main(int argc, char **argv) { int max = sizeof(dog); int i; if (argc >= 2) max = atoi(argv[1]); for (i = 0; i < max; i++) printf("dog[%d]: '%c'\n", i, dog_letter(i)); return 0; } ... With -m64: ... $ gcc -Wall -o mpx-out-of-bounds mpx-out-of-bounds.c -mmpx -fcheck-pointer-bounds $ ./mpx-out-of-bounds 10 dog[0]: 'd' dog[1]: 'o' dog[2]: 'g' dog[3]: '' Saw a #BR! status 1 at 0x400634 dog[4]: 's' Saw a #BR! status 1 at 0x400634 dog[5]: 'e' Saw a #BR! status 1 at 0x400634 dog[6]: 'c' Saw a #BR! status 1 at 0x400634 dog[7]: 'r' Saw a #BR! status 1 at 0x400634 dog[8]: '3' Saw a #BR! status 1 at 0x400634 dog[9]: 't' ... With -m32: ... $ gcc -m32 -Wall -o mpx-out-of-bounds mpx-out-of-bounds.c -mmpx -fcheck-pointer-bounds $ ./mpx-out-of-bounds 10 2>&1 | more Saw a #BR! status 4157798670 at 0x8048492 Unexpected status with bound exception: 4157798670 Saw a #BR! status 4157798670 at 0x8048492 Unexpected status with bound exception: 4157798670 Saw a #BR! status 4157798670 at 0x8048492 Unexpected status with bound exception: 4157798670 Saw a #BR! status 4157798670 at 0x8048492 Unexpected status with bound exception: 4157798670 Saw a #BR! status 4157798670 at 0x8048492 Unexpected status with bound exception: 4157798670 Saw a #BR! status 4157798670 at 0x8048492 Unexpected status with bound exception: 4157798670 Saw a #BR! status 4157798670 at 0x8048492 Unexpected status with bound exception: 4157798670 Saw a #BR! status 4157798670 at 0x8048492 Unexpected status with bound exception: 4157798670 Saw a #BR! status 4157798670 at 0x8048492 Unexpected status with bound exception: 4157798670 Saw a #BR! status 4157798670 at 0x8048492 Unexpected status with bound exception: 4157798670 Saw a #BR! status 4157798670 at 0x8048492 Unexpected status with bound exception: 4157798670 <etc> ... From what I understand, the problem starts the moment a first mpx instruction is executed, which should trigger an exception that is caught by the kernel to allocate some related tables. -- You are receiving this mail because: You are the assignee for the bug.

1 31

[Bug 1193648] New: mt7921e network card not initializing correctly
by bugzilla_noreply＠suse.com 02 May '22

02 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1193648 Bug ID: 1193648 Summary: mt7921e network card not initializing correctly Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: otni.ledelay(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: Community User Blocker: --- Created attachment 854506 --> http://bugzilla.opensuse.org/attachment.cgi?id=854506&action=edit output of 'journalctl --system --dmesg --boot 0' I am dual booting win10 and TW on a new laptop, trying to slowly migrate to Linux. I haven't however been able to get my WiFi working on Linux. ## I have tried: - Disabling fast boot and Windows hibernation - Several boot parameters: * pcie_aspm=force This did result in my wifi card almost working the first time I ran with it. See journal2.txt for the results of that, what happened seems similar to what's described here: https://www.spinics.net/lists/linux-wireless/msg218339.html It didn't work the second time I tried it. * pcie_aspm=off Didn't solve the problem, again identical results to journal.txt (but without the "can't disable ASPM" warning) * acpi_osi='Windows 2021' Didn't solve the problem. * acpi=off Broke a bunch of other things but didn't solve the problem. There was one time after a long time of not using my laptop that my wifi did seem to work, journal attached as journal3.txt ## System information: 212:~ # tumbleweed installed 20211206 212:~ # uname -svrio Linux 5.15.6-1-default #1 SMP Wed Dec 1 08:32:12 UTC 2021 (c2ce213) x86_64 GNU/Linux 212:~ # lspci -s 0000:02:00.0 -v 02:00.0 Network controller: MEDIATEK Corp. Device 7961 Subsystem: AzureWave Device 4680 Physical Slot: 0-1 Flags: fast devsel, IRQ 89, IOMMU group 9 Memory at ff20300000 (64-bit, prefetchable) [size=1M] Memory at ff20400000 (64-bit, prefetchable) [size=16K] Memory at ff20404000 (64-bit, prefetchable) [size=4K] Capabilities: [80] Express Endpoint, MSI 00 Capabilities: [e0] MSI: Enable- Count=1/32 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 Kernel modules: mt7921e 212:~ # lshw -C network *-network UNCLAIMED description: Network controller product: MEDIATEK Corp. vendor: MEDIATEK Corp. physical id: 0 bus info: pci@0000:02:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm cap_list configuration: latency=0 resources: iomemory:ff0-fef iomemory:ff0-fef iomemory:ff0-fef memory:ff20300000-ff203fffff memory:ff20400000-ff20403fff memory:ff20404000-ff20404fff *-network description: Ethernet interface physical id: 9 bus info: usb@1:1 logical name: enp4s0f3u1 serial: 3e:06:0b:1a:15:ec capabilities: ethernet physical configuration: autonegotiation=off broadcast=yes driver=rndis_host driverversion=5.15.6-1-default duplex=half firmware=RNDIS device ip=192.168.248.106 link=yes multicast=yes port=twisted pair (The second one is my phone using USB tethering to provide my laptop with internet, the problem is also present when my phone is not connected.) 212:~ # rfkill list all 0: asus-wlan: Wireless LAN Soft blocked: no Hard blocked: no 1: asus-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 2: hci0: Bluetooth Soft blocked: no Hard blocked: no 212:~ # dmesg -l err [ 2.446661] sp5100-tco sp5100-tco: Watchdog hardware is disabled [ 4.927198] mt7921e 0000:02:00.0: ASIC revision: 79610010 [ 18.152314] Bluetooth: hci0: Failed to read MSFT supported features (-110) 212:~ # dmesg | grep mt7921e [ 4.926736] mt7921e 0000:02:00.0: enabling device (0000 -> 0002) [ 4.927096] mt7921e 0000:02:00.0: disabling ASPM L1 [ 4.927099] mt7921e 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control [ 4.927198] mt7921e 0000:02:00.0: ASIC revision: 79610010 [ 6.020425] mt7921e: probe of 0000:02:00.0 failed with error -110 212:~ # journalctl --system --dmesg --boot 0 > journal.txt 212:~ # journalctl --system --dmesg --boot -8 > journal2.txt 212:~ # journalctl --system --dmesg --boot -18 > journal3.txt -- You are receiving this mail because: You are the assignee for the bug.

1 14

[Bug 1193374] New: [kernel 5.15.3][zpci] not initialized/supported: => lspci -v / lspci -k lists no PCI devices
by bugzilla_noreply＠suse.com 29 Apr '22

29 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1193374 Bug ID: 1193374 Summary: [kernel 5.15.3][zpci] not initialized/supported: => lspci -v / lspci -k lists no PCI devices Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: holger.rauch(a)posteo.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/98.0.4743.0 Safari/537.36 Build Identifier: a bug search for "zpci" yielded no results, so I decided to file this as a new bug. Regarding the actual details: please see "steps to reproduce" below (to me it *seems* the missing PCI devices are a secondary error due to the missing zpci initialization, which in turn is due to the missing CPU facilities). Please also note that I haven't tried any other kernel releases besides the default kernel shipped with OpenSUSE Tumbleweed (which, at the time of this writing is 5.15.3) Interesting questions in this regard: 1. Are other CPU facilities missing, too (besides the two mentioned ones "69" and "71")? 2. Is there something like a reference list of all CPU facilities that "normally" are/should be supported? TIA for any additional help/info. Reproducible: Always Steps to Reproduce: 1. lspci -v / lspci -k => no devices listed (but interestingly, the exit status of both commands is zero) 2. sudo dmesg | grep zpci => zpci: PCI is not supported because CPU facilities 69 or 71 are not available 3. grep facilities /proc/cpuinfo => facilities : 0 1 2 3 4 6 7 8 9 10 12 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 30 31 32 33 34 35 36 37 38 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 57 58 59 60 61 73 74 75 76 77 80 81 82 128 129 130 131 133 134 135 146 147 148 150 151 152 155 156 168 => both CPU facilities indeed seem to be missing (note that the next facility number after "61" is "73") Actual Results: no PCI devices Expected Results: The "lspci" command should list some PCI devices uname -v => #1 SMP Fri Nov 19 08:35:39 UTC 2021 (404f576) The machine I tested this on is part of the LinuxONE Community Cloud. -- You are receiving this mail because: You are the assignee for the bug.

1 17

[Bug 1194943] New: cert related kernel build breakages in 5.17 merge window
by bugzilla_noreply＠suse.com 26 Apr '22

26 Apr '22

https://bugzilla.suse.com/show_bug.cgi?id=1194943 Bug ID: 1194943 Summary: cert related kernel build breakages in 5.17 merge window 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: mkubecek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The upcoming 5.17-rc1 breaks build in two different ways: 1. When building locally with "osc build" (i.e. signing key is not provided), the build fails with error like > certs/extract-cert certs/signing_key.x509 > Usage: extract-cert <source> <dest> > make[2]: *** [/home/mike/work/git/kernel-upstream/certs/Makefile:78: certs/signing_key.x509] Error 2 > make[1]: *** [/home/mike/work/git/kernel-upstream/Makefile:1831: certs] Error 2 > make[1]: Leaving directory '/srv/ram/kobj' > make: *** [Makefile:219: __sub-make] Error 2 After mainline commit b8c96a6b466c ("certs: simplify $(srctree)/ handling and remove config_filename macro"), make executes extract-cert with only one argument due to an unquoted empty string. (Easier way to reproduce this is to run sequence-patch.sh, change CONFIG_MODULE_SIG_KEY to an empty string like our kernel-*.spec do and run "make all" or "make certs"). As the trick with empty CONFIG_MODULE_SIG_KEY (used since bug 1187167) is recommended by (upstream) Documentation/kbuild/reproducible-builds.rst, I also reported this to upstream in https://lore.kernel.org/all/20220120094606.2skuyb26yjlnu66q@lion.mk-sys.cz/ 2. When building in OBS, builds after mainline commit e06a61a89ccd ("certs: use if_changed to re-generate the key when the key type is changed") fail in a different way: > [ 42s] make[1]: *** Deleting file 'certs/signing_key.pem' > [ 42s] GENKEY certs/signing_key.pem > [ 42s] Generating a RSA private key > [ 42s] ..........................................................+++++ > [ 42s] ..................+++++ > [ 42s] writing new private key to 'certs/signing_key.pem' > [ 42s] ----- > [ 42s] unable to find 'distinguished_name' in config > [ 42s] problems making Certificate Request > [ 42s] 140680883695552:error:0E06D06C:configuration file routines:NCONF_get_string:no value:crypto/conf/conf_lib.c:273:group=req name=distinguished_name > [ 42s] make[1]: *** [../certs/Makefile:57: certs/signing_key.pem] Error 1 > [ 42s] make: *** [../Makefile:1845: certs] Error 2 > [ 42s] make: *** Waiting for unfinished jobs.... IIUC the problem here is that after rewriting the rule for signing_key.pem to if_changed based version, the rule is always invoked first time as there is no "previous command line" so that the trick introduced in kernel-source commit 6eb6cd2106c2 for bug 983634 (providing our key/certificate under default name and touching certs/x509.genkey to prevent regenerating it no longer works. (The empty certs/x509.genkey is empty created by touch is not valid for openssl.) This can be observed in home:mkubecek:rc0 OBS project at the moment. It can be also reproduced locally with "osc build" by adding a key/certificate file as _projectcert.crt to the directory generated by tar-up.sh (e.g a randomly generated one from a simple "make all" build of expanded tree). I'm not sure if I understand the reason why we do this correctly. Does it still make sense to enforce using the default key/certificate file path when a key/certificate is supplied if we replace CONFIG_MODULE_SIG_KEY with empty string for builds where a key/certificate is not supplied? -- You are receiving this mail because: You are the assignee for the bug.

1 15

[Bug 1195857] New: System suspend stopped working because of wifi
by bugzilla_noreply＠suse.com 24 Apr '22

24 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1195857 Bug ID: 1195857 Summary: System suspend stopped working because of wifi 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: cy6erGn0m(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After upgrading tumbleweed, system suspend stopped working because of failing to enter PM state. dmesg excerpt: [44812.779354] brcmfmac 0000:02:00.0: brcmf_pcie_pm_enter_D3: Timeout on response for entering D3 substate [44812.779365] PM: pci_pm_suspend(): brcmf_pcie_pm_enter_D3+0x0/0x140 [brcmfmac] returns -5 [44812.779468] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x160 returns -5 [44812.779486] brcmfmac 0000:02:00.0: PM: failed to suspend async: error -5 [44812.779642] PM: Some devices failed to suspend, or early wake event detected sudo lshw -C Network *-network description: Wireless interface product: BCM43602 802.11ac Wireless LAN SoC vendor: Broadcom Inc. and subsidiaries physical id: 0 bus info: pci@0000:02:00.0 logical name: wlp2s0 version: 01 serial: 40:49:0f:fe:d3:4b width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=brcmfmac driverversion=7.35.177.61 firmware=01-ea662a8c ip=192.168.0.2 latency=0 multicast=yes wireless=IEEE 802.11 resources: irq:136 memory:dd800000-dd807fff memory:dd400000-dd7fffff More related kernel logs at the beginning: dmesg | grep brcmfmac [ 4.290886] usbcore: registered new interface driver brcmfmac [ 4.290936] brcmfmac 0000:02:00.0: enabling device (0000 -> 0002) [ 4.399941] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43602-pcie for chip BCM43602/1 [ 4.400915] brcmfmac 0000:02:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.Dell Inc.-XPS 15 9550.bin failed with error -2 [ 4.443495] brcmfmac 0000:02:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.Dell Inc.-XPS 15 9550.txt failed with error -2 [ 4.443518] brcmfmac 0000:02:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2 [ 4.965032] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43602-pcie for chip BCM43602/1 [ 4.965053] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available [ 4.965653] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43602/1 wl0: Nov 10 2015 06:38:10 version 7.35.177.61 (r598657) FWID 01-ea662a8c locate 'brcm/brcmfmac43602' /usr/lib/firmware/brcm/brcmfmac43602-pcie.ap.bin.xz /usr/lib/firmware/brcm/brcmfmac43602-pcie.bin.xz What I don't get is why does it try to load "brcm/brcmfmac43602-pcie.Dell Inc.-XPS 15 9550.bin" that is of course missing? -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1195588] New: Tumbleweed with kernel 5.16 won't boot on Toshiba portege z830
by bugzilla_noreply＠suse.com 21 Apr '22

21 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1195588 Bug ID: 1195588 Summary: Tumbleweed with kernel 5.16 won't boot on Toshiba portege z830 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: al98murru(a)hotmail.it QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 855910 --> http://bugzilla.opensuse.org/attachment.cgi?id=855910&action=edit output of lshw command on my laptop After the update of the kernel update (from 5.14) on tumbleweed my laptop won't boot. I was suggested to update the bios to fix, which I am trying to do. When I try to boot, the machine freezes and from these errors in a loop, both with and without Acpi: 1671 ACPI Error: Abarting method SB.PC10.SATO PRTO. GTF due to previous error (AE NOT FOUND) (20210930/paparse-5231 1671 atal.00: exception Enask 6x6 Sct 0x10006000 SErr 8x8 action 6x6 frozen 31.05702511 31.05869531 31.85869511 7671 atal.00: failed command: READ FPDMA QUEUED 167] atal.00: cnid 60/08:00:00:00:00 00:00:00:00:00/40 tag 30 ncq dima 4096 in T673 res 40/00:00:00:00:00 00:00:00:00:00 00 Emask 8x4 (timeout) 31.86328111 32.18231211 T671 ata1.00: status: (DRDY > T671 ACPI BIOS Error (hug): Could not resolve symbol SB.PCIO.SATO.PRTO. SDD.GTF01, AE NOT FOUND (20210930-psargs-330) 1671 ACPI Error: Aborting nethod SB.PC10.SATO.PRTO. SDD due to previous error (AE NOT FOUND) (20210930/psparse-529) T671 ACPI BIOS Error (hug): Could not resolve symbol ISB.PC10.SATO.PRTO. GTF.GTF01, AE NOT FOUND (20210930/psargs-330) 1671 ACPI Error: Aborting method SB.PC10.SATO.PRTO. GTF due to previous error (AE_HOT_FOUND) (20210930/psparse-529) 1673 ACPI BIOS Error (bug): Could not resolve symbol ISB.PCIO.SATO.PRTO. SDD.GTF01. AE NOT FOUND (20210930/psargs-330) 1671 ACPI Error: Aborting method SB.PC10.SATO.PRTO. SDD due to previous error (AE_NOT_FOUND) (28210930/psparse-529) 1671 ACPI BIOS Error (bug): Could not resolve symbol ISB.PCIO.SATO.PRTO. GTF.GTFO), AE HOT FOUND (20210936/psargs-330) 7671 ACPI Error: Aborting method SB.PCIO.SATO.PRTO. GTF due to previous error (AE NOT FOUND) (20210930/psparse-529) I leave attached the output of the lshw command obtained by MxLinux live. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1193601] New: Kernel log jumps to the middle of the screen
by bugzilla_noreply＠suse.com 17 Apr '22

17 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1193601 Bug ID: 1193601 Summary: Kernel log jumps to the middle of the screen Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: opendreas(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 854451 --> http://bugzilla.opensuse.org/attachment.cgi?id=854451&action=edit Kernel log Kernel log jumps at boot to the middle of the screen. This issue is not present on Leap 15.3, but it is on Tumbleweed. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1189791] New: btrfs filesystem corruptions with HyperPAV
by bugzilla_noreply＠suse.com 06 Apr '22

06 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1189791 Bug ID: 1189791 Summary: btrfs filesystem corruptions with HyperPAV 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: ada.lovelace(a)gmx.de Found By: --- Blocker: --- For a proof of concept, I created a machine with 22 3390-54 Disks attached to a single btrfs, cylinder 0 excluded as minidisks. This happened in certain junks of disks (at least 4 at a time). After adding devices, I always did a rebalance of the btrfs. When I added disk 15-18, I also enabled hyperpav (without cylinder 0 on the base devices) as available as feature for z/VM 7.2 (feature also has been added to z/VM). The definition looks like this in the directory: COMMAND DEFINE HYPERPAVALIAS 01C0 FOR BASE 0100 I also added alias devices at addresses 01C1-01C7. However, later on when copying data from that disk, I found quite a number of corruptions within btrfs. After a while the server even crashed, and is now running without hyperpav. Corruptions that already happened are obviously still there, but besides that, the system works without the hangs I experienced before. By chance (don't think that would be the issue), the first disk with corruptions is the 16th disk in the system (including the system disk). And while thinking about this, the disk with number 100 has not been enabled on the system, although all disks are defined to the same control unit. HyperPAV has been used during rebalance of the last 8 disks because dasdstat displayed workload on the PAV device. # btrfs device stats /srv | grep corruption_errs [/dev/dasdb1].corruption_errs 0 [/dev/dasdc1].corruption_errs 0 [/dev/dasdd1].corruption_errs 0 [/dev/dasde1].corruption_errs 0 [/dev/dasdk1].corruption_errs 0 [/dev/dasdj1].corruption_errs 0 [/dev/dasdh1].corruption_errs 0 [/dev/dasdm1].corruption_errs 0 [/dev/dasdf1].corruption_errs 0 [/dev/dasdg1].corruption_errs 0 [/dev/dasdl1].corruption_errs 0 [/dev/dasdi1].corruption_errs 0 [/dev/dasdn1].corruption_errs 0 [/dev/dasdo1].corruption_errs 0 [/dev/dasdp1].corruption_errs 331 [/dev/dasdq1].corruption_errs 303 [/dev/dasds1].corruption_errs 302 [/dev/dasdv1].corruption_errs 399 [/dev/dasdr1].corruption_errs 356 [/dev/dasdt1].corruption_errs 206 [/dev/dasdw1].corruption_errs 279 [/dev/dasdu1].corruption_errs 218 # dmesg | tail [ 6616.004750] BTRFS warning (device dasdb1): csum failed root 5 ino 40234 off 1818624 csum 0x8941f998 expected csum 0x99cae683 mirror 1 [ 6616.004755] BTRFS error (device dasdb1): bdev /dev/dasdv1 errs: wr 0, rd 0, flush 0, corrupt 401, gen 0 [ 6616.005008] BTRFS warning (device dasdb1): csum failed root 5 ino 40234 off 3637248 csum 0x8941f998 expected csum 0xe55a18c7 mirror 1 [ 6616.005013] BTRFS error (device dasdb1): bdev /dev/dasdv1 errs: wr 0, rd 0, flush 0, corrupt 402, gen 0 [ 6616.005238] BTRFS warning (device dasdb1): csum failed root 5 ino 40234 off 1818624 csum 0x8941f998 expected csum 0x99cae683 mirror 1 [ 6616.005244] BTRFS error (device dasdb1): bdev /dev/dasdv1 errs: wr 0, rd 0, flush 0, corrupt 403, gen 0 [ 6616.005513] BTRFS warning (device dasdb1): csum failed root 5 ino 40234 off 1818624 csum 0x8941f998 expected csum 0x99cae683 mirror 1 [ 6616.005565] BTRFS error (device dasdb1): bdev /dev/dasdv1 errs: wr 0, rd 0, flush 0, corrupt 404, gen 0 [ 6616.882699] BTRFS warning (device dasdb1): csum failed root 5 ino 40224 off 10055680 csum 0x8941f998 expected csum 0x26222530 mirror 1 [ 6616.882715] BTRFS error (device dasdb1): bdev /dev/dasdu1 errs: wr 0, rd 0, flush 0, corrupt 249, gen 0 # uname -a Linux zlxusr1020 5.12.12-1-default #1 SMP Fri Jun 18 11:07:46 UTC 2021 (0e46a2c) s390x s390x s390x GNU/Linux -- You are receiving this mail because: You are the assignee for the bug.

1 13

[Bug 1195892] New: Kernel oops in nvme_ctrl_dhchap_ctrl_secret_show when running dracut / building initrd
by bugzilla_noreply＠suse.com 22 Mar '22

22 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1195892 Bug ID: 1195892 Summary: Kernel oops in nvme_ctrl_dhchap_ctrl_secret_show when running dracut / building initrd Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: aarch64 OS: openSUSE Leap 15.4 Status: NEW Severity: Major 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 856120 --> http://bugzilla.opensuse.org/attachment.cgi?id=856120&action=edit Output from dracut showing kernel oops + full system dmesg When running dracut on my system (Traverse Ten64, NXP LS1088 / aarch64) on Leap 15.4 Alpha, the following kernel oops occurs: $ uname -a Linux localhost 5.14.21-150400.5-default #1 SMP PREEMPT Wed Jan 19 16:17:31 UTC 2022 (b9720b9) aarch64 aarch64 aarch64 GNU/Linux $ rpm -q --whatprovides /boot/Image-5.14.21-150400.5-default kernel-default-5.14.21-150400.5.1.aarch64 $ dracut --force dracut: Executing: /usr/bin/dracut --force ... dracut: *** Including module: systemd-initrd *** dracut: *** Including module: i18n *** dracut: *** Including module: btrfs *** dracut: *** Including module: kernel-modules *** [ 259.903101][ T5336] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000068 [ 259.912610][ T5336] Mem abort info: [ 259.916095][ T5336] ESR = 0x96000004 [ 259.919840][ T5336] EC = 0x25: DABT (current EL), IL = 32 bits [ 259.925858][ T5336] SET = 0, FnV = 0 [ 259.929604][ T5336] EA = 0, S1PTW = 0 [ 259.933465][ T5336] FSC = 0x04: level 0 translation fault [ 259.939036][ T5336] Data abort info: [ 259.942617][ T5336] ISV = 0, ISS = 0x00000004 [ 259.947147][ T5336] CM = 0, WnR = 0 [ 259.950805][ T5336] user pgtable: 4k pages, 48-bit VAs, pgdp=000000808896d000 [ 259.957951][ T5336] [0000000000000068] pgd=0000000000000000, p4d=0000000000000000 [ 259.965453][ T5336] Internal error: Oops: 96000004 [#1] PREEMPT SMP ... [ 260.046059][ T5336] Supported: No, Unsupported modules are loaded [ 260.052153][ T5336] CPU: 1 PID: 5336 Comm: udevadm Tainted: G N 5.14.21-150400.5-default #1 SLE15-SP4 35bfd82ffbb186e93de22cb9e43b0b86d1845c87 [ 260.066422][ T5336] Hardware name: traverse ten64/ten64, BIOS 2020.07-rc1-g488778dc 11/22/2021 [ 260.075036][ T5336] pstate: 40000005 (nZcv daif -PAN -UAO -TCO BTYPE=--) [ 260.081738][ T5336] pc : nvme_ctrl_dhchap_ctrl_secret_show+0x20/0x80 [nvme_core] [ 260.089178][ T5336] lr : dev_attr_show+0x2c/0x80 [ 260.093799][ T5336] sp : ffff8000154339c0 [ 260.097805][ T5336] x29: ffff8000154339c0 x28: 0000000000000001 x27: 0000000000400cc0 [ 260.105642][ T5336] x26: 000000007ffff000 x25: ffff77624a0fd308 x24: 0000000000000000 [ 260.113481][ T5336] x23: ffffc393389bfff8 x22: ffff776246259400 x21: ffff7762417d5398 [ 260.121318][ T5336] x20: ffff77624a0fd2d0 x19: ffffc392ca8b0b58 x18: 0000000000000000 [ 260.129156][ T5336] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000 [ 260.136993][ T5336] x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000 [ 260.144831][ T5336] x11: 0000000000000000 x10: 0000000000000000 x9 : ffffc3933839fd6c [ 260.152669][ T5336] x8 : ffff77624a064000 x7 : 0000000000000000 x6 : 000000000000003f [ 260.160508][ T5336] x5 : 0000000000000040 x4 : ffffc392ca897800 x3 : ffffc3933839fd40 [ 260.168345][ T5336] x2 : ffff77624a063000 x1 : 0000000000000000 x0 : ffff77624a063000 [ 260.176185][ T5336] Call trace: [ 260.179322][ T5336] nvme_ctrl_dhchap_ctrl_secret_show+0x20/0x80 [nvme_core 6cc2f3568e41e8e1acd389e82779138699caf2d4] [ 260.189971][ T5336] dev_attr_show+0x2c/0x80 [ 260.194242][ T5336] sysfs_kf_seq_show+0x98/0x180 [ 260.198949][ T5336] kernfs_seq_show+0x34/0x40 [ 260.203393][ T5336] seq_read_iter+0xe8/0x480 [ 260.207751][ T5336] kernfs_fop_read_iter+0x14c/0x200 [ 260.212804][ T5336] new_sync_read+0xf8/0x1c0 [ 260.217162][ T5336] vfs_read+0x1ec/0x200 [ 260.221171][ T5336] ksys_read+0x74/0x140 [ 260.225180][ T5336] __arm64_sys_read+0x20/0x40 [ 260.229712][ T5336] invoke_syscall+0x74/0x100 [ 260.234159][ T5336] el0_svc_common+0x9c/0x1c0 [ 260.238603][ T5336] do_el0_svc+0x30/0xc0 [ 260.242612][ T5336] el0_svc+0x24/0x40 [ 260.246363][ T5336] el0t_64_sync_handler+0x94/0xc0 [ 260.251242][ T5336] el0t_64_sync+0x198/0x19c [ 260.255602][ T5336] Code: 910003fd f9403c01 aa0203e0 f945dc21 (f9403422) [ 260.262392][ T5336] ---[ end trace f65fe9e6406342ac ]--- I have tried on two separate systems with two different SSDs: 1) Western Digital WDC CL SN520 SDAPMUW-128G-1022 2) Samsung MZVLB256HBHQ-00000 (also known as PM981a) Dracut does complete, but the resulting initrd fails hangs at: Welcome to openSUSE Leap 15.4 Alpha dracut-055+suse.183.g7d569585-150400.1.7 (Initramfs)! ... [ OK ] Finished dracut pre-udev hook. Starting Rule-based Manage��for Device Events and Files... [ OK ] Started Rule-based Manager for Device Events and Files. Starting Coldplug All udev Devices... [ OK ] Finished Coldplug All udev Devices. [ OK ] Reached target System Initialization. [ OK ] Reached target Basic System. Starting dracut initqueue hook... (hangs here for a few minutes) [ 158.234725] dracut-initqueue[456]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks: [ 158.280363] dracut-initqueue[456]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fdisk\x2fby-uuid\x2fAF98-0018.sh: "[ -e "/dev/disk/by-uuid/AF98-0018" ]" [ 158.320251] dracut-initqueue[456]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fdisk\x2fby-uuid\x2fae1c1277-cbc0-4d89-b5ab-0d052727aa5a.sh: "if ! grep -q After=remote-fs-pre.target /run/systemd/generator/systemd-cryptsetup(a)*.service 2>/dev/null; then [ 158.370198] dracut-initqueue[456]: [ -e "/dev/disk/by-uuid/ae1c1277-cbc0-4d89-b5ab-0d052727aa5a" ] [ 158.400173] dracut-initqueue[456]: fi" [ 158.430087] dracut-initqueue[456]: Warning: dracut-initqueue: starting timeout scripts [ 158.873928] dracut-initqueue[456]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks: (the above repeats constantly, presumably the wrong root device was referenced in the initrd) The issue does not occur when the system is booted (as in / on) from a non-NVMe device (e.g USB), even if there is an NVMe device installed in the system. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1184767] New: Several firmwares missing when installing MicroOS
by bugzilla_noreply＠suse.com 16 Mar '22

16 Mar '22

https://bugzilla.suse.com/show_bug.cgi?id=1184767 Bug ID: 1184767 Summary: Several firmwares missing when installing MicroOS 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: dfaggioli(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After finishing installing MicroOS on my laptop, I have this in dmesg: dario@Palanthas-eth:~> dmesg |grep firmware [ 0.073533] Spectre V2 : Enabling Restricted Speculation for firmware calls [ 2.964996] i915 0000:00:02.0: Direct firmware load for i915/kbl_dmc_ver1_04.bin failed with error -2 [ 2.964998] i915 0000:00:02.0: [drm] Failed to load DMC firmware i915/kbl_dmc_ver1_04.bin. Disabling runtime power management. [ 2.964999] i915 0000:00:02.0: [drm] DMC firmware homepage: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git… [ 66.877346] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ 66.928640] r8152 4-1.4:1.0: Direct firmware load for rtl_nic/rtl8153a-3.fw failed with error -2 [ 66.928646] r8152 4-1.4:1.0: unable to load firmware patch rtl_nic/rtl8153a-3.fw (-2) [ 67.153449] bluetooth hci0: Direct firmware load for qca/rampatch_usb_00000302.bin failed with error -2 [ 67.906512] ath10k_pci 0000:3a:00.0: Failed to find firmware-N.bin (N between 2 and 6) from ath10k/QCA6174/hw3.0: -2 [ 67.906552] ath10k_pci 0000:3a:00.0: could not fetch firmware files (-2) And WiFi and Bluetooth are not working. All the firmware related messages go away if I install the following packages: - kernel-firmware-iwlwifi - kernel-firmware-realtek - kernel-firmware-i915 - kernel-firmware-bluetooth - kernel-firmware-ath10k The message about regulatory.db goes away if I install the crda package This is related to bug 1184403 with the only difference that there the missing firmware is in kernel-firmware-iwlwifi. Also, it looks like this shouldn't happen, according to bug 1174521, as it's marked as fixed, but the problem seems to still be there -- You are receiving this mail because: You are the assignee for the bug.

1 3