December 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[kernel-bugs] [Bug 1177288] New: Raspberry pi3 (model b) crashes with network gadget
by bugzilla_noreply＠suse.com 03 Jul '22

03 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1177288 Bug ID: 1177288 Summary: Raspberry pi3 (model b) crashes with network gadget 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: coolo(a)suse.com QA Contact: qa-bugs(a)suse.de CC: guillaume.gardet(a)arm.com, nsaenzjulienne(a)suse.com Found By: --- Blocker: --- I use the official Leap 15.2 Jeos image on a pi3b and have a USB network device attached to it (a very special one, https://www.fibrecode.com/fc602-usb-oabr-broadr-reach-100base-t1-stick.html) and it crashes the kernel pretty reliably with the following crash dump. [ 86.184109] usb 1-1.3: USB disconnect, device number 5 [ 86.184427] cdc_ether 1-1.3:1.0 eth2: unregister 'cdc_ether' usb-3f980000.usb-1.3, CDC Ethernet Device [ 99.795717] usb 1-1.3: new high-speed USB device number 7 using dwc2 [ 99.926758] usb 1-1.3: New USB device found, idVendor=152a, idProduct=857b, bcdDevice= 2.24 [ 99.926780] usb 1-1.3: New USB device strings: Mfr=2, Product=1, SerialNumber=3 [ 99.926788] usb 1-1.3: Product: FibreCode FC602 Stick [ 99.926796] usb 1-1.3: Manufacturer: FibreCode [ 99.926804] usb 1-1.3: SerialNumber: FC01330000018a69 [ 99.930380] cdc_ether 1-1.3:1.0 eth1: register 'cdc_ether' at usb-3f980000.usb-1.3, CDC Ethernet Device, fc:c2:3d:1f:7f:ad [ 99.949857] cdc_ether 1-1.3:1.0 eth2: renamed from eth1 [ 740.880346] dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 7 - ChHltd set, but reason is unknown [ 740.880360] dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04400001 [ 741.461843] dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 1 - ChHltd set, but reason is unknown [ 741.461858] dwc2 3f980000.usb: hcint 0x00000002, intsts 0x06400001 [ 741.880374] dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 5 - ChHltd set, but reason is unknown [ 741.880386] dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04400001 [ 741.880395] dwc2 3f980000.usb: dwc2_update_urb_state_abn(): trimming xfer length [ 741.880573] WARNING: CPU: 0 PID: 0 at ../drivers/usb/dwc2/hcd.c:2683 dwc2_assign_and_init_hc+0x664/0xa10 [dwc2] [ 741.880578] Modules linked in: af_packet iscsi_ibft iscsi_boot_sysfs vc4 drm_kms_helper drm btsdio snd_soc_core bluetooth snd_compress snd_bcm2835(C) nls_iso8859_1 ac97_bus nls_cp437 snd_pcm_dmaengine ecdh_generic snd_pcm bcm2835_v4l2(C) ecc vfat v4l2_common snd_timer fat videobuf2_vmalloc brcmfmac videobuf2_memops videobuf2_v4l2 snd videobuf2_common videodev mc brcmutil cpufreq_dt soundcore fb_sys_fops cfg80211 syscopyarea sysfillrect microchip sysimgblt rfkill ftdi_sio cdc_ether usbnet lan78xx usbserial mii raspberrypi_hwmon bcm2835_thermal raspberrypi_cpufreq vchiq(C) bcm2835_rng bcm2835_wdt crct10dif_ce uio_pdrv_genirq uio leds_gpio ext4 mbcache jbd2 mmc_block dwc2 udc_core usbcore sdhci_iproc sdhci_pltfm sdhci bcm2835 gpio_raspberrypi_exp mmc_core clk_raspberrypi i2c_bcm2835 bcm2835_dma fixed phy_generic dm_mirror dm_region_hash dm_log sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua scsi_mod efivarfs [ 741.880754] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G C 5.3.18-lp152.36-default #1 openSUSE Leap 15.2 (unreleased) [ 741.880759] Hardware name: raspberrypi rpi/rpi, BIOS 2020.01 06/02/2020 [ 741.880765] pstate: 60000085 (nZCv daIf -PAN -UAO) [ 741.880799] pc : dwc2_assign_and_init_hc+0x664/0xa10 [dwc2] [ 741.880834] lr : dwc2_hcd_select_transactions+0x104/0x1a0 [dwc2] [ 741.880838] sp : ffff000010003c60 [ 741.880842] x29: ffff000010003c60 x28: ffff3bd997683dc0 [ 741.880849] x27: ffffa6ec7c4c4000 x26: ffff3bd997679000 [ 741.880857] x25: 0000000000000008 x24: ffffa6ec7c6a55e0 [ 741.880864] x23: ffffa6ec6bbc5080 x22: ffffa6ec77d12830 [ 741.880871] x21: ffffa6ec79871600 x20: ffffa6ec7c6a5080 [ 741.880878] x19: ffffa6ec6bbc50c8 x18: ffffffffffffffff [ 741.880885] x17: 0000000000000001 x16: 0000000000000007 [ 741.880891] x15: ffff3bd997679708 x14: ffff3bd9978cfa28 [ 741.880898] x13: ffff3bd9978cf67e x12: ffff3bd9976a2000 [ 741.880905] x11: 0000000000000000 x10: ffff3bd9978ce000 [ 741.880912] x9 : 0000000000000000 x8 : 0000000000000003 [ 741.880919] x7 : 0000000000000176 x6 : ffff3bd9978cec90 [ 741.880925] x5 : 0000000000000001 x4 : ffffa6ec79871698 [ 741.880932] x3 : 0000000000000000 x2 : 00000000000005ee [ 741.880939] x1 : 0000000000000000 x0 : 0000000000000002 [ 741.880946] Call trace: [ 741.880984] dwc2_assign_and_init_hc+0x664/0xa10 [dwc2] [ 741.881018] dwc2_hcd_select_transactions+0x104/0x1a0 [dwc2] [ 741.881052] dwc2_release_channel+0xfc/0x280 [dwc2] [ 741.881087] dwc2_halt_channel+0xac/0x158 [dwc2] [ 741.881121] dwc2_hc_n_intr+0x860/0x8c0 [dwc2] [ 741.881155] dwc2_handle_hcd_intr+0x38c/0x450 [dwc2] [ 741.881188] _dwc2_hcd_irq+0x20/0x30 [dwc2] [ 741.881278] usb_hcd_irq+0x3c/0x60 [usbcore] [ 741.881291] __handle_irq_event_percpu+0x74/0x268 [ 741.881299] handle_irq_event_percpu+0x40/0x98 [ 741.881307] handle_irq_event+0x50/0xa8 [ 741.881314] handle_level_irq+0xd4/0x178 [ 741.881321] generic_handle_irq+0x34/0x50 [ 741.881332] bcm2836_chained_handle_irq+0x4c/0x70 [ 741.881339] generic_handle_irq+0x34/0x50 [ 741.881346] __handle_domain_irq+0x68/0xc0 [ 741.881354] bcm2836_arm_irqchip_handle_irq+0x78/0xe0 [ 741.881360] el1_irq+0xcc/0x180 [ 741.881369] arch_cpu_idle+0x40/0x1c0 [ 741.881377] default_idle_call+0x24/0x44 [ 741.881385] do_idle+0x1dc/0x2c0 [ 741.881392] cpu_startup_entry+0x28/0x30 [ 741.881400] rest_init+0xc4/0xd0 [ 741.881409] arch_call_rest_init+0x14/0x1c [ 741.881414] start_kernel+0x4e8/0x51c [ 741.881419] ---[ end trace 29007ab7897c5716 ]--- [ 742.880425] dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 7 - ChHltd set, but reason is unknown [ 742.880437] dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04600001 [ 742.880445] dwc2 3f980000.usb: dwc2_update_urb_state_abn(): trimming xfer length [ 743.880453] dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 3 - ChHltd set, but reason is unknown [ 743.880465] dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04600001 [ 743.880474] dwc2 3f980000.usb: dwc2_update_urb_state_abn(): trimming xfer length [ 744.880491] dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 4 - ChHltd set, but reason is unknown [ 744.880505] dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04600001 [ 744.880514] dwc2 3f980000.usb: dwc2_update_urb_state_abn(): trimming xfer length [ 745.880537] dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 6 - ChHltd set, but reason is unknown [ 745.880549] dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04600001 [ 745.880557] dwc2 3f980000.usb: dwc2_update_urb_state_abn(): trimming xfer length [ 746.880564] dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 5 - ChHltd set, but reason is unknown [ 746.880576] dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04600001 [ 746.880585] dwc2 3f980000.usb: dwc2_update_urb_state_abn(): trimming xfer length [ 747.880601] dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 1 - ChHltd set, but reason is unknown [ 747.880612] dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04600001 [ 747.880621] dwc2 3f980000.usb: dwc2_update_urb_state_abn(): trimming xfer length [ 748.880641] dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 6 - ChHltd set, but reason is unknown [ 748.880654] dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04600009 [ 748.880664] dwc2 3f980000.usb: dwc2_update_urb_state_abn(): trimming xfer length [ 749.880675] dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 1 - ChHltd set, but reason is unknown [ 749.880686] dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04600001 [ 749.880695] dwc2 3f980000.usb: dwc2_update_urb_state_abn(): trimming xfer length [ 750.880718] dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 4 - ChHltd set, but reason is unknown -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1193652] New: Logitech mouse and keyboard stop working on the latest kernel.
by bugzilla_noreply＠suse.com 22 Jun '22

22 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 Bug ID: 1193652 Summary: Logitech mouse and keyboard stop working on the latest kernel. 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: benthomasgeorge7899(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 854509 --> http://bugzilla.opensuse.org/attachment.cgi?id=854509&action=edit Logs of the said issue The mouse and keyboard stopped working randomly first while working. Later on reboot it works fine with bios and grub encryption password but within minutes the kernel is loaded it disconnects the keyboard and mouse. Possible reasons have been checked for- 1. Issue is not cause due to tlp 2. Issue not caused due to autosuspend of usb. Both the mouse and keyboard and mouse are working fine on the previous kernel 5.15.5-1. Rollback to the previous kernel has solved the issue. -- You are receiving this mail because: You are the assignee for the bug.

1 57

[Bug 1190190] New: kmod: manpage of modprobe.d not correctly rendered
by bugzilla_noreply＠suse.com 21 Jun '22

21 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1190190 Bug ID: 1190190 Summary: kmod: manpage of modprobe.d not correctly rendered 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: sebix+novell.com(a)sebix.at QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The manpage of modprobe.d looks broken: man modprobe.d | head MODPROBE.D(5) modprobe.d MODPROBE.D(5) .SH "NAME" modprobe.d - Configuration directory for modprobe .SH "SYNOPSIS" .PP /lib/modprobe.d/*.conf .PP /usr/lib/modprobe.d/*.conf The corresponding package `kmod` does not have a bugowner assigned in OBS, so I chose none. Using TW 20210831. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1191322] New: Optimize building initrd when updating system
by bugzilla_noreply＠suse.com 10 Jun '22

10 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1191322 Bug ID: 1191322 Summary: Optimize building initrd when updating system Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: All OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When installing updates, dracut is called multiple times to update the initrds of all kernels, for example when lvm2 is updated or when the kernel is updated. It would be better if the initrds were updated once at the end of the transaction (as Fedora does it, for example). Despite of that when keeping older kernels, there may be reasons _not_ to update the initrds of the older kernels: First, some may be removed on next boot anyway, and second, more important: If the idea of older kernels (and initrds) is to have a failback in case the new kernel, initrd or and binaries inside are broken (and thus fail to boot), it seems preferable to have the proven old kernel and initrd. -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 1184804] New: move kernel out of /boot
by bugzilla_noreply＠suse.com 24 May '22

24 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1184804 Bug ID: 1184804 Summary: move kernel out of /boot 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: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- One of the motivations for UsrMerge is to have all read-only parts of the operating system in /usr. The kernel packages install files in /boot though which isn't in line with that idea. Having the kernel installed via rpm in /boot also causes issues with eg snapshots if /boot is on a separate partition. So it make sense to store the rpm provided parts of the kernel packages where the rest of the OS is and manage /boot separately. Looking at Fedora they install files like vmlinuz that used to be named /boot/$name-$kver as (/usr)/lib/modules/$kver/$name instead. They include /boot/$name-$kver as %ghost. -- You are receiving this mail because: You are the assignee for the bug.

1 28

[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 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