May 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1198565] New: 5.17.2-1-default shows ACPI BIOS Errors - 5.17.1-1-default did not.
by bugzilla_noreply＠suse.com 19 Jul '22

19 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1198565 Bug ID: 1198565 Summary: 5.17.2-1-default shows ACPI BIOS Errors - 5.17.1-1-default did not. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Minor Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: daniel.becker(a)quippy.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 858213 --> http://bugzilla.opensuse.org/attachment.cgi?id=858213&action=edit acpidump > acpidump.raw After latest update to kernel 5.17.2-1 today, boot shows ACPI BIOS Errors: Apr 18 13:33:20 ****** kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330) Apr 18 13:33:20 ****** kernel: ACPI Error: Aborting method \_SB.PR01._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529) Apr 18 13:33:20 ****** kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330) Apr 18 13:33:20 ****** kernel: ACPI Error: Aborting method \_SB.PR02._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529) Apr 18 13:33:20 ****** kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330) Apr 18 13:33:20 ****** kernel: ACPI Error: Aborting method \_SB.PR03._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529) Apr 18 13:33:20 ****** kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330) Apr 18 13:33:20 ****** kernel: ACPI Error: Aborting method \_SB.PR04._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529) Apr 18 13:33:20 ****** kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330) Apr 18 13:33:20 ****** kernel: ACPI Error: Aborting method \_SB.PR05._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529) Previous 5.17.1-1-default did not show these. I added "acpidump > acpidump.raw" to this error report. uname -a shows: Linux quippy 5.17.2-1-default #1 SMP PREEMPT Sat Apr 9 06:30:15 UTC 2022 (b49cf22) x86_64 x86_64 x86_64 GNU/Linux Does not seem to be a show stopper, but something changed and could be wrong now so someone might want to look into this. -- You are receiving this mail because: You are the assignee for the bug.

1 28

[Bug 1199355] New: aarch64 oopses on raspberry pi4 KVM host (OBS worker)
by bugzilla_noreply＠suse.com 13 Jul '22

13 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1199355 Bug ID: 1199355 Summary: aarch64 oopses on raspberry pi4 KVM host (OBS worker) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: seife(a)novell.slipkontur.de QA Contact: qa-bugs(a)suse.de CC: guillaume.gardet(a)arm.com Found By: --- Blocker: --- I have two raspberry pi 4 OBS workers for packman build service running, both with 8GB RAM. One of them (configured to run one build worker with 4 jobs/7,5GB RAM) recently started crashing. First I guessed it was related to overclocking, but reducing the overclocking did not change anything. It always crashes towards the end of a rather long, big build job (kodi), with the following Oops message: [ 8891.760241] Unable to handle kernel access to user memory outside uaccess routines at virtual address 0000000000000134 [ 8891.771989] Mem abort info: [ 8891.775574] ESR = 0x96000004 [ 8891.779609] EC = 0x25: DABT (current EL), IL = 32 bits [ 8891.785850] SET = 0, FnV = 0 [ 8891.789772] EA = 0, S1PTW = 0 [ 8891.793819] FSC = 0x04: level 0 translation fault [ 8891.799591] Data abort info: [ 8891.803330] ISV = 0, ISS = 0x00000004 [ 8891.808174] CM = 0, WnR = 0 [ 8891.811900] user pgtable: 4k pages, 48-bit VAs, pgdp=000000015e6f2000 [ 8891.819194] [0000000000000134] pgd=0000000000000000, p4d=0000000000000000 [ 8891.826833] Internal error: Oops: 96000004 [#1] SMP [ 8891.832496] Modules linked in: loop tun af_packet iscsi_ibft iscsi_boot_sysfs nls_iso8859_1 xfs nls_cp437 vfat fat btsdio bluetooth libcrc32c ecdh_generic cpufreq_dt brcmfmac broadcom brcmutil bcm_phy_lib cfg80211 rfkill bcm2711_thermal raspberrypi_cpufreq iproc_rng200 genet mdio_bcm_unimac leds_gpio uio_pdrv_genirq uio nvmem_rmem efi_pstore drm fuse ip_tables x_tables ext4 mbcache jbd2 uas usb_storage xhci_pci xhci_pci_renesas xhci_hcd usbcore usb_common raspberrypi_hwmon crct10dif_ce gpio_raspberrypi_exp clk_raspberrypi bcm2835_wdt bcm2835_dma virt_dma sdhci_iproc sdhci_pltfm sdhci mmc_core gpio_regulator pcie_brcmstb phy_generic fixed sg efivarfs [ 8891.891666] CPU: 0 PID: 6193 Comm: qemu-system-aar Not tainted 5.17.4-1-default #1 openSUSE Tumbleweed 3c702964721983dd61af41a493a0755b03b09b96 [ 8891.905435] Hardware name: Unknown Unknown Product/Unknown Product, BIOS 2022.04 04/01/2022 [ 8891.914612] pstate: 00400005 (nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 8891.922381] pc : blk_mq_submit_bio+0x178/0x680 [ 8891.927612] lr : blk_mq_submit_bio+0x15c/0x680 [ 8891.932830] sp : ffff800009d62d90 [ 8891.936894] x29: ffff800009d62d90 x28: fffffcd369257208 x27: fffffcd369257200 [ 8891.944844] x26: ffff800009d63128 x25: 0000000000000001 x24: ffffa8dc6edaaae0 [ 8891.952793] x23: 0000000000000000 x22: ffff34da90f7c8e0 x21: ffff34da8680c1a0 [ 8891.960740] x20: ffff34da90fbf300 x19: ffff34da86849000 x18: 0000000000000003 [ 8891.968686] x17: 0000000000000001 x16: ffffa8dc6edd8840 x15: 0000000000000003 [ 8891.976631] x14: 0000000000000000 x13: 0000000000000038 x12: 0000000000000000 [ 8891.984578] x11: 0000000000000040 x10: 0000000000001b60 x9 : ffffa8dc6f0228c0 [ 8891.992526] x8 : ffff34da80917b00 x7 : 0000000000000000 x6 : 0000000000000001 [ 8892.000472] x5 : 00000000410fd080 x4 : 0000000000000000 x3 : ffff8bff0e894000 [ 8892.008419] x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000004000001 [ 8892.016366] Call trace: [ 8892.019549] blk_mq_submit_bio+0x178/0x680 [ 8892.024417] __submit_bio+0x118/0x180 [ 8892.028843] submit_bio_noacct+0x1ec/0x240 [ 8892.033707] submit_bio+0x64/0x140 [ 8892.037864] __swap_writepage+0x1b4/0x4a0 [ 8892.042641] swap_writepage+0x50/0x114 [ 8892.047150] pageout+0x104/0x340 [ 8892.051133] shrink_page_list+0x6b0/0xe84 [ 8892.055909] shrink_lruvec+0x584/0xb40 [ 8892.060419] shrink_node+0x3e8/0x774 [ 8892.064756] do_try_to_free_pages+0xec/0x580 [ 8892.069796] try_to_free_pages+0x118/0x210 [ 8892.074660] __alloc_pages+0x4a8/0xd04 [ 8892.079172] alloc_pages+0xb8/0x16c [ 8892.083425] folio_alloc+0x28/0x64 [ 8892.087583] filemap_alloc_folio+0xd8/0xf0 [ 8892.092447] page_cache_ra_unbounded+0xac/0x220 [ 8892.097751] ondemand_readahead+0x12c/0x2b0 [ 8892.102701] page_cache_async_ra+0xc4/0xe0 [ 8892.107565] filemap_get_pages+0x4b8/0x684 [ 8892.112430] filemap_read+0xc4/0x30c [ 8892.116763] generic_file_read_iter+0x114/0x1b0 [ 8892.122068] xfs_file_buffered_read+0xb4/0xe0 [xfs cbfa202397a50e39d50211b94f5332ed2c6954f4] [ 8892.131638] xfs_file_read_iter+0xa8/0x124 [xfs cbfa202397a50e39d50211b94f5332ed2c6954f4] [ 8892.140936] io_read+0xe4/0x3dc [ 8892.144834] io_issue_sqe+0x218/0x1aa0 [ 8892.149346] io_submit_sqes+0x28c/0x15f4 [ 8892.154033] __arm64_sys_io_uring_enter+0x4f0/0x76c [ 8892.159689] invoke_syscall+0x78/0x100 [ 8892.164202] el0_svc_common.constprop.0+0x180/0x184 [ 8892.169859] do_el0_svc+0x34/0x9c [ 8892.173931] el0_svc+0x30/0x100 [ 8892.177830] el0t_64_sync_handler+0xa4/0x130 [ 8892.182871] el0t_64_sync+0x1a4/0x1a8 [ 8892.187300] Code: 37c00060 72001c1f 1a9f17e1 f9400a62 (79426842) [ 8892.194187] ---[ end trace 0000000000000000 ]--- After that, I most of the time can still log in to the box via ssh, examine dmesg etc, but no writing to storage is possible anymore (sync, ... all hangs). Usually, I then reboot the box via "echo b > /proc/syrq-trigger" The raspberry pi 4 is running off a USB3-connected SATA ssd, it has a good passive-cooling case (CPU temperature always below 70�C) and the original raspberry pi USB-C power supply. Running up to date tumbleweed/ARM Another raspberry pi 4 8GB, set up tu run two workers with 2 jobs / 3,7GB each does run fine without crashes or issues. -- You are receiving this mail because: You are the assignee for the bug.

1 29

[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 1199211] New: set buildflags exclude on kernel devel project so that branched projects have proper build disables
by bugzilla_noreply＠suse.com 27 Jun '22

27 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1199211 Bug ID: 1199211 Summary: set buildflags exclude on kernel devel project so that branched projects have proper build disables 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: dmueller(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Kernel:stable has an optimized build setup where the kernel-binaries flavor (kernel-default, debug and so on) are only build-enabled for the "standard"/"ports" repositories, not for the "QA repositories. This makes sense to me and is sensible to optimize rebuild performance on the build service. however, when I do branch kernel-source, a full project is replicated under my OBS home project, and that one has build flags enabled for all the repositories. So with other words the branch projects have a lot more packages to build than the main project. This is because build disables are not inheriting over branches, they get reset. After a chat with the OBS folks, these two options are there: * set a OBS:BranchSkipRepositories attribute on the project. that means that new project branches will entirely have the given repositories skipped when creating a branch. I personally think that isn't the desired behavior, as it would means things like kernel-obs-build etc are not properly tested * add a BuildFlags: excludebuild:$packagename to the prjconf. this inherits to all derived projects, also existing ones, and makes the disabled-flags setting obsolete. I have tested the following configuration successfully. There might be a script somewhere that needs to be adapted to generate this project config. otherwise I think manually maintaining it for now is fine also. %if "%_repository" == "QA" || "%_repository" == "QA_ports" || "%_repository" == "QA_ARM" || "%_repository" == "QA_PPC" || "%_repository" == "QA_RISCV" || "%_repository" == "QA_S390" BuildFlags: excludebuild:dtb-aarch64 BuildFlags: excludebuild:dtb-armv6l BuildFlags: excludebuild:dtb-armv7l BuildFlags: excludebuild:dtb-riscv64 BuildFlags: excludebuild:kernel-64kb BuildFlags: excludebuild:kernel-debug BuildFlags: excludebuild:kernel-default BuildFlags: excludebuild:kernel-docs BuildFlags: excludebuild:kernel-firmware BuildFlags: excludebuild:kernel-firmware:compressed BuildFlags: excludebuild:kernel-kvmsmall BuildFlags: excludebuild:kernel-lpae BuildFlags: excludebuild:kernel-pae BuildFlags: excludebuild:kernel-source BuildFlags: excludebuild:kernel-syms BuildFlags: excludebuild:kernel-syzkaller BuildFlags: excludebuild:kernel-vanilla BuildFlags: excludebuild:kernel-zfcpdump BuildFlags: excludebuild:pesign-obs-integration BuildFlags: excludebuild:qlogic-rules BuildFlags: excludebuild:systemtap %endif %if "%_repository" == "standard" || "%_repository" == "ports" || "%_repository" == "PPC" || "%_repository" == "RISCV" || "%_repository" == "S390" BuildFlags: excludebuild:kernel-obs-build BuildFlags: excludebuild:kernel-obs-qa %endif -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1199901] New: [RPi4] Camera module not detected
by bugzilla_noreply＠suse.com 22 Jun '22

22 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1199901 Bug ID: 1199901 Summary: [RPi4] Camera module 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: dheidler(a)suse.com QA Contact: qa-bugs(a)suse.de CC: afaerber(a)suse.com, guillaume.gardet(a)opensuse.org, ivan.ivanov(a)suse.com, m.szczepaniak.000(a)gmail.com Found By: --- Blocker: --- Created attachment 859212 --> https://bugzilla.suse.com/attachment.cgi?id=859212&action=edit dmesg I'm using a raspberry Pi 4B and followed the steps at https://en.opensuse.org/HCL:Raspberry_Pi_Camera_Modules to get the camera module https://www.berrybase.de/raspberry-pi/raspberry-pi-computer/kameras/raspber… working. It is connected to the camera header, raspberrypi-firmware-extra-pi4 and raspberrypi-firmware-extra is installed. Updated /boot/efi/config.txt ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ # Default gpu_mem value is 76 for 1GB (or greater) and 64 for less. Min 16 - Max 512 MB # See: https://www.raspberrypi.com/documentation/computers/config_txt.html#gpu_mem # We don't need that much memory reserved for it, because we drive most hardware # from Linux, not the VPU OS #gpu_mem=32 # start_x is used to enable the camera module (and must be set here - boo#1192047) # and requires to install raspberrypi-firmware-extra or raspberrypi-firmware-extra-pi4 # start_x=1 start_x=1 # gpu_mem needs to be increased when start_x is used, 128 is the minimum there # gpu_mem=128 gpu_mem=128 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I rebooted but I don't get a /dev/video* device -- You are receiving this mail because: You are the assignee for the bug.

1 15

[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 1199322] New: btrfs lock ups
by bugzilla_noreply＠suse.com 20 Jun '22

20 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1199322 Bug ID: 1199322 Summary: btrfs lock ups Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jnelson-suse(a)jamponi.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I've been having some trouble with btrfs. The symptom is that I have higher than normal wait state but with no tasks using CPU. Using `echo w > /proc/sysrq-trigger` there is a common theme: May 08 09:40:44 turnip kernel: task:btrfs-transacti state:D stack: 0 pid: 841 ppid: 2 flags:0x80004000 May 08 09:40:44 turnip kernel: Call Trace: May 08 09:40:44 turnip kernel: __schedule+0x2ff/0x760 May 08 09:40:44 turnip kernel: ? bit_wait+0x50/0x50 May 08 09:40:44 turnip kernel: schedule+0x2f/0xa0 May 08 09:40:44 turnip kernel: io_schedule+0x12/0x40 May 08 09:40:44 turnip kernel: bit_wait_io+0xd/0x50 May 08 09:40:44 turnip kernel: __wait_on_bit+0x2c/0x90 May 08 09:40:44 turnip kernel: out_of_line_wait_on_bit+0x91/0xb0 May 08 09:40:44 turnip kernel: ? init_wait_var_entry+0x50/0x50 May 08 09:40:44 turnip kernel: write_all_supers+0x278/0xa00 [btrfs] May 08 09:40:44 turnip kernel: ? btrfs_commit_transaction+0x790/0xa60 [btrfs] May 08 09:40:44 turnip kernel: btrfs_commit_transaction+0x790/0xa60 [btrfs] May 08 09:40:44 turnip kernel: ? start_transaction+0xc5/0x540 [btrfs] May 08 09:40:44 turnip kernel: transaction_kthread+0x148/0x160 [btrfs] May 08 09:40:44 turnip kernel: ? btrfs_cleanup_transaction+0x5c0/0x5c0 [btrfs] May 08 09:40:44 turnip kernel: kthread+0x10d/0x130 May 08 09:40:44 turnip kernel: ? kthread_park+0xa0/0xa0 May 08 09:40:44 turnip kernel: ret_from_fork+0x35/0x40 I tried to use `btrfs check` (offline) and it complains of free space mis-matches, so I zero the v2 free space and then when I try to zero the v1 free space: turnip:~ # btrfs check -p --clear-space-cache v1 /dev/disk/by-uuid/ea5898b2-3e9f-4a4b-ae54-5e3e1d13c3ff Opening filesystem to check... Checking filesystem on /dev/disk/by-uuid/ea5898b2-3e9f-4a4b-ae54-5e3e1d13c3ff UUID: ea5898b2-3e9f-4a4b-ae54-5e3e1d13c3ff Failed to find [401685020672, 168, 16384] btrfs unable to find ref byte nr 401685037056 parent 0 root 2 owner 0 offset 0 transaction.c:195: btrfs_commit_transaction: BUG_ON `ret` triggered, value -5 btrfs(+0x51f99)[0x560c29c5df99] btrfs(btrfs_commit_transaction+0x1ae)[0x560c29c5e58e] btrfs(btrfs_clear_free_space_cache+0xdc)[0x560c29c510bc] btrfs(+0x157fa)[0x560c29c217fa] btrfs(cmd_check+0x103a)[0x560c29c73cca] btrfs(main+0x8e)[0x560c29c2b08e] /lib64/libc.so.6(__libc_start_main+0xef)[0x7feccb3382bd] btrfs(_start+0x2a)[0x560c29c2b28a] Aborted (core dumped) turnip:~ # Currently running a basic 'check'. Kernel is latest. I regularly run scrub/etc. via btrfsmaintenance -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1199922] New: Wifi connection drops then system crashes
by bugzilla_noreply＠suse.com 17 Jun '22

17 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1199922 Bug ID: 1199922 Summary: Wifi connection drops then system crashes 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: graeme.w.murray(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- under normal network load, wifi connection drops and then system crashes -- You are receiving this mail because: You are the assignee for the bug.

1 9