August 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1188934] New: bluetooth not automatically powered on
by bugzilla_noreply＠suse.com 22 Jul '22

22 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1188934 Bug ID: 1188934 Summary: bluetooth not automatically powered on 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: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- There is yet another way to make bluetooth devices unusable. The beluetooth adapter is by default powered off, and has to be manually powered on to be able to connect devices. [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady [bluetooth]# power on [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady Failed to set power on: org.bluez.Error.Failed [DEL] Controller 00:E0:3C:87:B8:03 naga [default] [NEW] Controller 00:E0:3C:87:B8:03 naga [default] [CHG] Controller 00:E0:3C:87:B8:03 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb [CHG] Controller 00:E0:3C:87:B8:03 UUIDs: 0000111f-0000-1000-8000-00805f9b34fb [CHG] Controller 00:E0:3C:87:B8:03 UUIDs: 00001200-0000-1000-8000-00805f9b34fb [CHG] Controller 00:E0:3C:87:B8:03 UUIDs: 00001112-0000-1000-8000-00805f9b34fb [CHG] Controller 00:E0:3C:87:B8:03 UUIDs: 00001108-0000-1000-8000-00805f9b34fb [CHG] Controller 00:E0:3C:87:B8:03 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb [CHG] Controller 00:E0:3C:87:B8:03 UUIDs: 00001800-0000-1000-8000-00805f9b34fb [CHG] Controller 00:E0:3C:87:B8:03 UUIDs: 0000110a-0000-1000-8000-00805f9b34fb [CHG] Controller 00:E0:3C:87:B8:03 UUIDs: 00001801-0000-1000-8000-00805f9b34fb [CHG] Controller 00:E0:3C:87:B8:03 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb [CHG] Controller 00:E0:3C:87:B8:03 UUIDs: 0000180a-0000-1000-8000-00805f9b34fb [bluetooth]# power on [CHG] Controller 00:E0:3C:87:B8:03 Class: 0x006c010c Changing power on succeeded [CHG] Controller 00:E0:3C:87:B8:03 Powered: yes [bluetooth]# scan on Discovery started I think that it's quite clear you wanted your adapter powered on if you tried to scan for devices. The Linux kernel got automatic power management ages ago. Can't that apply to bluetooth as well? -- You are receiving this mail because: You are the assignee for the bug.

1 1

[kernel-bugs] [Bug 1174622] New: System not reconnecting to WLAN after suspend/resume
by bugzilla_noreply＠suse.com 22 Jul '22

22 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1174622 Bug ID: 1174622 Summary: System not reconnecting to WLAN after suspend/resume Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: holgi(a)suse.com QA Contact: qa-bugs(a)suse.de CC: tiwai(a)suse.com Found By: Development Blocker: --- Created attachment 840122 --> https://bugzilla.suse.com/attachment.cgi?id=840122&action=edit Output of hwinfo --netcard System with NetworkManger is connected to a wifi network. After suspend and resume later, it is not able to reconnect to the same wifi network. After a reboot, system is connecting to the same wifi network without any problems. -- You are receiving this mail because: You are the assignee for the bug.

1 27

[kernel-bugs] [Bug 1174868] New: Upgrade to LEAP 15.2 makes Thinkpad 480s sometimes completely freezes, 20°C warmer and journal is trimmed
by bugzilla_noreply＠suse.com 20 Jul '22

20 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1174868 Bug ID: 1174868 Summary: Upgrade to LEAP 15.2 makes Thinkpad 480s sometimes completely freezes, 20°C warmer and journal is trimmed 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: markus.zimmermann(a)symflower.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- One of our machines here a Thinkpad T480s on openSUSE 15.2 kernel 5.3.18-lp152.33-default. In general this machine was upgraded from LEAP 15.1 to 15.2 and then the problems started to show. The CPU is constantly hotter while working. by 20°C. This machine now freezes sometimes completely. The machine is then - not pingable - no keyboard interaction works - lid close/open does nothng - no mouse interaction works - the notebook is really warm - When a freeze happens also a trim of the journal happens... e.g. we loose the whole journal for the day. - We SSH'ed into the machine and watched via "htop", "journal -f" and "sensors". WHen the machine freezes, there is no significant load via htop seeable, there are no interesting logs in journal and sensors shows that it is simply hotter. Interestingly, we upgraded another machine before (also a Thinkpad T480s) and this does not have any problems. We are btw on the latest firmwares using fwupdmgr. What should we try? How can we debug it? -- You are receiving this mail because: You are the assignee for the bug.

1 20

[kernel-bugs] [Bug 1177800] New: [Ten64] getsysinfo caused kernel error (synchronous external abort)
by bugzilla_noreply＠suse.com 08 Jul '22

08 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1177800 Bug ID: 1177800 Summary: [Ten64] getsysinfo caused kernel error (synchronous external abort) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: afaerber(a)suse.com QA Contact: qa-bugs(a)suse.de CC: matt(a)traverse.com.au, snwint(a)suse.com, yousaf.kaukab(a)suse.com Found By: --- Blocker: --- Running `getsysinfo` (via ssh) on Tumbleweed 20201011 with kernel-default 5.9.0 from Kernel:HEAD repository caused a kernel error, with ssh getting stuck and reconnections failing. Serial login still worked. zehn:~ # getsysinfo /proc/bus/input /proc/cpuinfo /proc/device-tree /proc/devices /proc/fb /proc/filesystems /proc/interrupts /proc/iomem /proc/ioports /proc/meminfo /proc/modules /proc/net/dev /proc/partitions /proc/scsi /proc/tty /proc/version /sys /usr/sbin/getsysinfo: line 23: 2761 Segmentation fault cp -x -a --parents "$i" "$dir/$host" 2> /dev/null /var/lib/hardware/udi /proc/mounts System data written to: /tmp/zehn.tar.gz zehn:~ # [ 544.956478] Internal error: synchronous external abort: 96000210 [#1] SMP [ 544.963295] Modules linked in: af_packet ip6t_REJECT nf_reject_ipv6 ip6t_rpfilter xt_tcpudp ipt_REJECT nf_reject_ipv4 xt_conntrack ebtable_nat ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_raw iptable_security iscsi_ibft iscsi_boot_sysfs ip_set nfnetlink ebtable_filter ebtables rfkill ip6table_filter ip6_tables iptable_filter ip_tables x_tables fsl_dpaa2_ptp ptp_qoriq fsl_dpaa2_eth phylink xgmac_mdio hid_generic fsl_mc_dpio usbhid cdc_acm i2c_mux_pca954x i2c_mux tpm_i2c_atmel spi_fsl_qspi qoriq_thermal leds_gpio optee tee uio_pdrv_genirq uio qoriq_cpufreq nls_iso8859_1 nls_cp437 vfat fat drm xhci_plat_hcd xhci_hcd usbcore caam_jr mmc_block libdes authenc caamhash_desc caamalg_desc crypto_engine rtc_ds1307 mp886x aes_ce_blk crypto_simd cryptd aes_ce_cipher crct10dif_ce ghash_ce sha2_ce sha256_arm64 sha1_ce dpaa2_console nvme nvme_core dwc3 sdhci_of_esdhc caam sdhci_pltfm ulpi [ 544.963547] error sdhci udc_core roles mmc_core i2c_imx btrfs blake2b_generic libcrc32c xor xor_neon raid6_pq sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua [ 545.066303] CPU: 0 PID: 2761 Comm: cp Not tainted 5.9.0-1.g11733e1-default #1 openSUSE Tumbleweed (unreleased) [ 545.076303] Hardware name: traverse ten64/ten64, BIOS 2020.07-rc1-g1d4a3d9d5c 07/28/2020 [ 545.084393] pstate: 60000085 (nZCv daIf -PAN -UAO BTYPE=--) [ 545.089967] pc : dw_pcie_read+0x48/0xc0 [ 545.093799] lr : dw_pcie_access_other_conf.isra.0+0xc4/0x120 [ 545.099452] sp : ffff800012203bf0 [ 545.102759] x29: ffff800012203bf0 x28: 0000000000000400 [ 545.108067] x27: ffff00833e683400 x26: ffff008348240000 [ 545.113375] x25: ffff800010085000 x24: 0000000000000000 [ 545.118683] x23: ffff00834b239880 x22: ffff800012203cc4 [ 545.123991] x21: 0000000000000004 x20: 0000000000000400 [ 545.129299] x19: ffff00834b2398a8 x18: 0000000000000000 [ 545.134607] x17: 0000000000000000 x16: ffffafadaf1be170 [ 545.139915] x15: 0000000000000000 x14: 0000000000000000 [ 545.145222] x13: 0000000000000000 x12: 0000000000000040 [ 545.150530] x11: ffff00834bd8c920 x10: 0000000000000000 [ 545.155837] x9 : ffffafadaf12e8f4 x8 : 0000000002080000 [ 545.161145] x7 : 0000000000000000 x6 : ffff800010f00000 [ 545.166452] x5 : 0000000000000000 x4 : 0000000000000908 [ 545.171759] x3 : 0000000000000003 x2 : ffff800012203cc4 [ 545.177066] x1 : 0000000000000004 x0 : ffff800010085400 [ 545.182374] Call trace: [ 545.184816] dw_pcie_read+0x48/0xc0 [ 545.188298] dw_pcie_rd_conf+0x11c/0x150 [ 545.192217] pci_user_read_config_dword+0xa8/0x190 [ 545.197004] pci_read_config+0x1f8/0x264 [ 545.200923] sysfs_kf_bin_read+0x78/0xa0 [ 545.204840] kernfs_file_direct_read+0x90/0x220 [ 545.209365] kernfs_fop_read+0x44/0x50 [ 545.213111] vfs_read+0xb8/0x1e4 [ 545.216334] ksys_read+0x78/0x110 [ 545.219643] __arm64_sys_read+0x28/0x34 [ 545.223476] el0_svc_common.constprop.0+0x84/0x230 [ 545.228261] do_el0_svc+0x30/0xa0 [ 545.231572] el0_svc+0x18/0x50 [ 545.234621] el0_sync_handler+0x90/0x254 [ 545.238538] el0_sync+0x158/0x180 [ 545.241849] Code: 528010e0 d50323bf b900005f d65f03c0 (b9400001) [ 545.247941] ---[ end trace 68383e7eecaae870 ]--- -- You are receiving this mail because: You are the assignee for the bug.

1 5

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

[Bug 1180316] New: [Build 20201222] openQA test fails in kdump_and_crash
by bugzilla_noreply＠suse.com 15 Mar '22

15 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1180316 Bug ID: 1180316 Summary: [Build 20201222] openQA test fails in kdump_and_crash Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1523048/modules/kdum p_and_crash/steps/58 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos-extra@64bit_virtio-2G fails in [kdump_and_crash](https://openqa.opensuse.org/tests/1523048/modules/kdump_an… After the update to kernel 5.10, kdump_and_crash fails crash: cannot determine length of symbol: log_end ## Test suite description Same as jeos, plus some more tests. ## Reproducible Fails since (at least) Build [20190311](https://openqa.opensuse.org/tests/877894) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1184782] New: Emergency mode during boot with "mount(2) system call failed: Cannot allocate memory"
by bugzilla_noreply＠suse.com 11 Mar '22

11 Mar '22

https://bugzilla.suse.com/show_bug.cgi?id=1184782 Bug ID: 1184782 Summary: Emergency mode during boot with "mount(2) system call failed: Cannot allocate memory" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Just had this problem when starting my workstation this morning. May or may not be related to bug 1184779, which I encountered simultaneously. > [ 105.589905] apollon systemd[1]: Mounting /var/spool... > [ 105.610706] apollon systemd[1]: Mounting /var/tmp... > [ 105.612009] apollon systemd[1]: Starting File System Check on /dev/disk/by-label/git... > ... > [ 105.626645] apollon mount[1975]: mount: /var/tmp: mount(2) system call failed: Cannot allocate memory. > [ 105.636377] apollon systemd[1]: Finished Load/Save Screen Backlight Brightness of leds:dell::kbd_backlight. > [ 105.638474] apollon systemd[1]: Mounted /.snapshots. > [ 105.640099] apollon systemd[1]: Mounted /boot/efi. > ... > [ 105.666824] apollon systemd[1]: Failed to mount /var/tmp. > [ 105.668645] apollon systemd[1]: Dependency failed for Local File Systems. > [ 105.668705] apollon systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'. After entering emergency mode, I simply typed "mount /var/tmp", and had no issue. Bug 1184779 persisted though (see there). /var/tmp is just a btrfs subvolume. # btrfs subvol list / ID 257 gen 930369 top level 5 path @ ID 258 gen 1432317 top level 257 path @/.snapshots ID 260 gen 1427487 top level 257 path @/boot/grub2/x86_64-efi ID 261 gen 1432361 top level 257 path @/opt ID 262 gen 1427487 top level 257 path @/srv ID 263 gen 18 top level 257 path @/tmp ID 264 gen 1432300 top level 257 path @/usr/local ID 265 gen 1432339 top level 257 path @/var/cache ID 266 gen 1427487 top level 257 path @/var/crash ID 267 gen 1427487 top level 257 path @/var/lib/mailman ID 268 gen 1427487 top level 257 path @/var/lib/mariadb ID 269 gen 1427487 top level 257 path @/var/lib/mysql ID 270 gen 1427487 top level 257 path @/var/lib/named ID 271 gen 1427487 top level 257 path @/var/lib/pgsql ID 272 gen 1432392 top level 257 path @/var/log ID 273 gen 1427487 top level 257 path @/var/opt ID 274 gen 1432391 top level 257 path @/var/spool ID 275 gen 1432366 top level 257 path @/var/tmp ID 276 gen 1427487 top level 257 path @/var/lib/machines ID 1650 gen 1432304 top level 257 path @/var/lib/systemd/coredump ID 1893 gen 1432387 top level 258 path @/.snapshots/1113/snapshot ID 2158 gen 1418255 top level 258 path @/.snapshots/1271/snapshot ID 2159 gen 1424575 top level 258 path @/.snapshots/1272/snapshot ID 2163 gen 1427385 top level 258 path @/.snapshots/1273/snapshot ID 2164 gen 1429845 top level 258 path @/.snapshots/1274/snapshot ID 2165 gen 1429883 top level 258 path @/.snapshots/1275/snapshot ID 2166 gen 1429959 top level 258 path @/.snapshots/1276/snapshot ID 2167 gen 1429963 top level 258 path @/.snapshots/1277/snapshot It's listed in fstab like any other subvols. > UUID=ad544c37-37f9-44a4-9798-d29d3cb5db44 /var/tmp btrfs subvol=@/var/tmp 0 0 > UUID=ad544c37-37f9-44a4-9798-d29d3cb5db44 /.snapshots btrfs subvol=(a)/.snapshots 0 0 > UUID=ad544c37-37f9-44a4-9798-d29d3cb5db44 /var/lib/machines btrfs subvol=@/var/lib/machines 0 0 Full boot log is attached. systemd-246.13-1.1.x86_64 kernel-default-5.11.11-1.2.x86_64 libmount1-2.36.2-1.3.x86_64 util-linux-2.36.2-1.3.x86_64 The system has 8BiB RAM. It seems highly unlikely that the system went out of memory this early during boot. After boot and graphical user login, mem usage is like this: # free total used free shared buff/cache available Mem: 7897336 3457336 642880 767688 3797120 3305920 Swap: 8383484 23040 8360444 -- You are receiving this mail because: You are the assignee for the bug.

1 2