January 2024 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1210791] New: KMP builds fails with ld: cannot find arch/s390/lib/expoline/expoline.o
by bugzilla_noreply＠suse.com 27 Feb '24

27 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1210791 Bug ID: 1210791 Summary: KMP builds fails with ld: cannot find arch/s390/lib/expoline/expoline.o Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ptesarik(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Out-of-tree kernel modules can no longer be built for openSUSE:Factory:zSystems. See See https://build.opensuse.org/build/Kernel:kdump/openSUSE_Factory_zSystems/s39… [ 783s] + make -C /usr/src/linux-obj/s390x/default modules M=/home/abuild/rpmbuild/BUILD/crash-8.0.2/kbuild/default [ 783s] CC [M] /home/abuild/rpmbuild/BUILD/crash-8.0.2/kbuild/default/crash.o [ 784s] MODPOST /home/abuild/rpmbuild/BUILD/crash-8.0.2/kbuild/default/Module.symvers [ 784s] CC [M] /home/abuild/rpmbuild/BUILD/crash-8.0.2/kbuild/default/crash.mod.o [ 784s] LD [M] /home/abuild/rpmbuild/BUILD/crash-8.0.2/kbuild/default/crash.ko [ 784s] ld: cannot find arch/s390/lib/expoline/expoline.o: No such file or directory [ 784s] make[1]: *** [/usr/src/linux-6.2.12-1/scripts/Makefile.modfinal:61: /home/abuild/rpmbuild/BUILD/crash-8.0.2/kbuild/default/crash.ko] Error 1 [ 784s] make: *** [../../../linux-6.2.12-1/Makefile:1953: modules] Error 2 [ 784s] error: Bad exit status from /var/tmp/rpm-tmp.6wzRBp (%build) -- You are receiving this mail because: You are the assignee for the bug.

1 17

[Bug 1214133] New: bluetooth disabled after update to 20230808, firmware load for mediatek/BT_RAM_CODE_MT7922_1_1_hdr.bin failes
by bugzilla_noreply＠suse.com 25 Feb '24

25 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1214133 Bug ID: 1214133 Summary: bluetooth disabled after update to 20230808, firmware load for mediatek/BT_RAM_CODE_MT7922_1_1_hdr.bin failes 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: hofmann(a)shiphrah.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868726 --> https://bugzilla.suse.com/attachment.cgi?id=868726&action=edit dmesg on TW 20230808 After update to Tumbleweed 20230808 bluetooth is disabled and can not be enabled again. dmesg | grep luetooth (on TW 20230806) [ 6.098671] Bluetooth: Core ver 2.22 [ 6.098681] Bluetooth: HCI device and connection manager initialized [ 6.098683] Bluetooth: HCI socket layer initialized [ 6.098684] Bluetooth: L2CAP socket layer initialized [ 6.098685] Bluetooth: SCO socket layer initialized [ 26.836464] Bluetooth: hci0: Device setup in 20228164 usecs [ 26.836469] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported. [ 27.115864] Bluetooth: hci0: AOSP extensions version v1.00 [ 27.115870] Bluetooth: hci0: AOSP quality report is supported dmesg | grep luetooth (on TW 20230808) [ 4.355787] Bluetooth: Core ver 2.22 [ 4.355794] Bluetooth: HCI device and connection manager initialized [ 4.355797] Bluetooth: HCI socket layer initialized [ 4.355798] Bluetooth: L2CAP socket layer initialized [ 4.355799] Bluetooth: SCO socket layer initialized [ 4.368031] bluetooth hci0: Direct firmware load for mediatek/BT_RAM_CODE_MT7922_1_1_hdr.bin failed with error -2 [ 4.368034] Bluetooth: hci0: Failed to load firmware file (-2) [ 4.368045] Bluetooth: hci0: Failed to set up firmware (-2) [ 4.368053] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported. [ 4.438485] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 4.438487] Bluetooth: BNEP filters: protocol multicast [ 4.438489] Bluetooth: BNEP socket layer initialized unfortunately I can not say if it was working in TW 20230807 -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1213757] New: All processes that try to communicate with NETLINK socket hang up if running hostapd on Raspberry Pi
by bugzilla_noreply＠suse.com 20 Feb '24

20 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1213757 Bug ID: 1213757 Summary: All processes that try to communicate with NETLINK socket hang up if running hostapd on Raspberry Pi Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: aarch64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dheidler(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868483 --> https://bugzilla.suse.com/attachment.cgi?id=868483&action=edit strace of hanging "ip a" The issue appears a few (~5) minutes after hostapd is started. Jul 28 12:47:40 openqa-piworker systemd[1]: Started Hostapd IEEE 802.11 AP, IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator. Jul 28 12:47:40 openqa-piworker hostapd[15307]: Configuration file: /etc/hostapd.conf Jul 28 12:47:40 openqa-piworker kernel: br0: port 1(wlan0) entered blocking state Jul 28 12:47:40 openqa-piworker kernel: br0: port 1(wlan0) entered disabled state Jul 28 12:47:40 openqa-piworker kernel: device wlan0 entered promiscuous mode Jul 28 12:47:40 openqa-piworker hostapd[15307]: wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE Jul 28 12:47:41 openqa-piworker dbus-daemon[629]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service' requested by ':1.31' (uid=0 pid=730 comm="/usr/sbin/wickedd --systemd --foreground ") Jul 28 12:47:41 openqa-piworker systemd[1]: Starting WPA Supplicant daemon... Jul 28 12:47:41 openqa-piworker dbus-daemon[629]: [system] Successfully activated service 'fi.w1.wpa_supplicant1' Jul 28 12:47:41 openqa-piworker systemd[1]: Started WPA Supplicant daemon. Jul 28 12:47:45 openqa-piworker hostapd[15307]: wlan0: Could not connect to kernel driver Jul 28 12:47:45 openqa-piworker hostapd[15307]: Using interface wlan0 with hwaddr e4:5f:01:bb:63:41 and ssid "openQA-worker" Jul 28 12:47:45 openqa-piworker kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Jul 28 12:47:45 openqa-piworker kernel: br0: port 1(wlan0) entered blocking state Jul 28 12:47:45 openqa-piworker kernel: br0: port 1(wlan0) entered forwarding state Jul 28 12:47:45 openqa-piworker hostapd[15307]: wlan0: interface state COUNTRY_UPDATE->ENABLED Jul 28 12:47:45 openqa-piworker hostapd[15307]: wlan0: AP-ENABLED openqa-piworker:~ # cat /etc/sysconfig/network/ifcfg-br0 IPADDR='192.168.7.1/24' BOOTPROTO='static' STARTMODE='auto' BRIDGE='yes' BRIDGE_PORTS='' BRIDGE_STP='off' BRIDGE_FORWARDDELAY='15' ZONE=dmz openqa-piworker:~ # cat /etc/hostapd.conf interface=wlan0 bridge=br0 ssid=openQA-worker wpa_passphrase=0foobar12345 driver=nl80211 country_code=DE hw_mode=g channel=7 # Bit field: bit0 = WPA, bit1 = WPA2, 3=both wpa=2 # Bit field: 1=wpa, 2=wep, 3=both auth_algs=1 wpa_pairwise=CCMP wpa_key_mgmt=WPA-PSK logger_stdout=-1 logger_stdout_level=2 openqa-piworker:~ # systemctl cat hostapd.service # /usr/lib/systemd/system/hostapd.service [Unit] Description=Hostapd IEEE 802.11 AP, IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator After=network.target [Service] ExecStart=/usr/sbin/hostapd /etc/hostapd.conf ExecReload=/bin/kill -HUP $MAINPID [Install] WantedBy=multi-user.target # /etc/systemd/system/hostapd.service.d/override.conf # Ensure that wlan0 is up before starting hostapd (otherwise hostapd will not add wlan0 to the bridge) [Unit] BindsTo=sys-subsystem-net-devices-wlan0.device After=sys-subsystem-net-devices-wlan0.device -- You are receiving this mail because: You are the assignee for the bug.

1 32

[Bug 1219222] New: Disable CONFIG_USELIB
by bugzilla_noreply＠suse.com 13 Feb '24

13 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1219222 Bug ID: 1219222 Summary: Disable CONFIG_USELIB 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: jack(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- uselib(2) system call is generally deprecated and was last needed with libc5. Recently there were also issues with this syscall and path-based LSMs [1] so from security POV it makes sense to disable CONFIG_USELIB if we don't need it. [1] https://lore.kernel.org/all/20240124192228.work.788-kees@kernel.org -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 1218948] New: kernel:[ 3380.214840][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 112s! [kworker/0:2:156]
by bugzilla_noreply＠suse.com 07 Feb '24

07 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1218948 Bug ID: 1218948 Summary: kernel:[ 3380.214840][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 112s! [kworker/0:2:156] Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: chris(a)computersalat.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello kernel support, looks like a kernel module has some problems. I am continiously getting these watchdog messages on the console: Message from syslogd@tfrs-01 at Jan 18 12:24:04 ... kernel:[ 3380.214840][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 112s! [kworker/0:2:156] Message from syslogd@tfrs-01 at Jan 18 12:24:34 ... kernel:[ 3410.230328][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 140s! [kworker/0:2:156] Message from syslogd@tfrs-01 at Jan 18 12:25:04 ... kernel:[ 3440.311352][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 168s! [kworker/0:2:156] --- snip End --- This is what I see in /var/log/messages: 2024-01-18T12:18:44.564626+00:00 tfrs-01 kernel: [ 3060.657363][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 142s! [kworker/0:2:156] 2024-01-18T12:18:44.564635+00:00 tfrs-01 kernel: [ 3060.657366][ C0] Modules linked in: usbhid af_packet iscsi_ibft iscsi_boot_sysfs dmi_sysfs msr snd_hda_codec_realtek intel_rapl_msr intel_rapl_common intel _uncore_frequency intel_uncore_frequency_common intel_pmc_core x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_generic nvme ucsi_acpi coretemp ledtrig_audio kvm_intel hp_wmi sparse_keymap iTCO_wdt nls_iso88 59_1 nls_cp437 mei_pxp mei_hdcp(N) mei_wdt typec_ucsi snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_d sp snd_sof snd_sof_utils snd_soc_hdac_hda snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_hda_ext_core snd_soc_core intel_pmc_bxt vfat mei_me nvme_core typec iTCO_vendor_support snd_compress platform_pr ofile kvm fat snd_pcm_dmaengine e1000e mfd_core nvme_common wmi_bmof roles irqbypass rfkill mei pcspkr snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec snd_hda_core snd_hwdep snd_pcm 2024-01-18T12:18:44.564636+00:00 tfrs-01 kernel: [ 3060.657381][ C0] snd_timer snd soundcore i2c_i801 i2c_smbus button thermal acpi_tad(N) acpi_pad fuse configfs efi_pstore(N) ip_tables x_tables ext4 crc16 mbcache jbd2 raid1 md_mod sd_mod t10_pi sr_mod crc64_rocksoft_generic cdrom crc64_rocksoft crc64 i915 i2c_algo_bit drm_buddy drm_display_helper crc32_pclmul crc32c_intel drm_kms_helper ghash_clmulni_intel xhci_pci syscopyarea sysfillrect xhci_pci_renesas sysimgblt fb_sys_fops cec xhci_hcd rc_core ttm ahci aesni_intel drm libahci usbcore libata crypto_simd cryptd serio_raw wmi video sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua scsi_mod efivarfs 2024-01-18T12:18:44.564636+00:00 tfrs-01 kernel: [ 3060.657394][ C0] Supported: No, Unsupported modules are loaded 2024-01-18T12:18:44.564637+00:00 tfrs-01 kernel: [ 3060.657395][ C0] CPU: 0 PID: 156 Comm: kworker/0:2 Tainted: G W L N 5.14.21-150500.55.39-default #1 SLE15-SP5 534d850193522c220e62d98d0494b02a0dde2443 2024-01-18T12:18:44.564640+00:00 tfrs-01 kernel: [ 3060.657396][ C0] Hardware name: HP HP Elite Tower 600 G9 Desktop PC/8950, BIOS U01 Ver. 02.12.02 11/28/2023 2024-01-18T12:18:44.564640+00:00 tfrs-01 kernel: [ 3060.657396][ C0] Workqueue: events output_poll_execute [drm_kms_helper] 2024-01-18T12:18:44.564641+00:00 tfrs-01 kernel: [ 3060.657401][ C0] RIP: 0010:intel_dmc_load_program.part.10+0x75/0x320 [i915] 2024-01-18T12:18:44.564641+00:00 tfrs-01 kernel: [ 3060.657440][ C0] Code: 48 8d bd 48 0e 00 00 49 89 ec 8b 51 04 31 c0 85 d2 74 1f 48 8b 51 08 89 c6 8b 34 b2 8b 11 8d 14 82 48 03 95 e8 07 00 00 89 32 <83> c0 01 3b 41 04 72 e1 48 81 c1 c0 00 00 00 48 39 f9 75 cc 65 ff 2024-01-18T12:18:44.564641+00:00 tfrs-01 kernel: [ 3060.657441][ C0] RSP: 0018:ffffa498c065fb08 EFLAGS: 00000286 2024-01-18T12:18:44.564641+00:00 tfrs-01 kernel: [ 3060.657442][ C0] RAX: 0000000000000927 RBX: 0000000000000001 RCX: ffff952ed20a0a88 2024-01-18T12:18:44.564642+00:00 tfrs-01 kernel: [ 3060.657443][ C0] RDX: ffffa498c168249c RSI: 0000000000000010 RDI: ffff952ed20a0e48 2024-01-18T12:18:44.564642+00:00 tfrs-01 kernel: [ 3060.657443][ C0] RBP: ffff952ed20a0000 R08: 0000000000000000 R09: 0000000000000001 2024-01-18T12:18:44.564642+00:00 tfrs-01 kernel: [ 3060.657444][ C0] R10: ffffa498c065f9d0 R11: ffffa498c065f8f8 R12: ffff952ed20a0000 2024-01-18T12:18:44.564643+00:00 tfrs-01 kernel: [ 3060.657444][ C0] R13: 0000000000000006 R14: 0000000000000002 R15: ffffffffc0d967a0 2024-01-18T12:18:44.564643+00:00 tfrs-01 kernel: [ 3060.657445][ C0] FS: 0000000000000000(0000) GS:ffff953dff400000(0000) knlGS:0000000000000000 2024-01-18T12:18:44.564643+00:00 tfrs-01 kernel: [ 3060.657445][ C0] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 2024-01-18T12:18:44.564644+00:00 tfrs-01 kernel: [ 3060.657446][ C0] CR2: 00007ffd1a37bee6 CR3: 0000000456210000 CR4: 0000000000750ef0 2024-01-18T12:18:44.564644+00:00 tfrs-01 kernel: [ 3060.657446][ C0] PKRU: 55555554 2024-01-18T12:18:44.564644+00:00 tfrs-01 kernel: [ 3060.657446][ C0] Call Trace: 2024-01-18T12:18:44.564644+00:00 tfrs-01 kernel: [ 3060.657447][ C0] <TASK> 2024-01-18T12:18:44.564645+00:00 tfrs-01 kernel: [ 3060.657447][ C0] icl_display_core_init+0x2e3/0x6d0 [i915 78bbb16e393a51161506d14678c82dbe7746ab4e] 2024-01-18T12:18:44.564645+00:00 tfrs-01 kernel: [ 3060.657485][ C0] intel_display_power_resume+0x6b/0xa0 [i915 78bbb16e393a51161506d14678c82dbe7746ab4e] 2024-01-18T12:18:44.564645+00:00 tfrs-01 kernel: [ 3060.657522][ C0] intel_runtime_resume+0x7f/0x1e0 [i915 78bbb16e393a51161506d14678c82dbe7746ab4e] 2024-01-18T12:18:44.564646+00:00 tfrs-01 kernel: [ 3060.657543][ C0] pci_pm_runtime_resume+0x76/0xb0 2024-01-18T12:18:44.564646+00:00 tfrs-01 kernel: [ 3060.657545][ C0] ? pci_pm_default_resume+0x30/0x30 2024-01-18T12:18:44.564646+00:00 tfrs-01 kernel: [ 3060.657546][ C0] __rpm_callback+0x43/0x120 2024-01-18T12:18:44.564647+00:00 tfrs-01 kernel: [ 3060.657547][ C0] rpm_callback+0x5d/0x70 2024-01-18T12:18:44.564647+00:00 tfrs-01 kernel: [ 3060.657548][ C0] ? pci_pm_default_resume+0x30/0x30 2024-01-18T12:18:44.564647+00:00 tfrs-01 kernel: [ 3060.657549][ C0] rpm_resume+0x4c0/0x770 2024-01-18T12:18:44.564647+00:00 tfrs-01 kernel: [ 3060.657550][ C0] ? pci_bus_read_config_dword+0x41/0x70 2024-01-18T12:18:44.564648+00:00 tfrs-01 kernel: [ 3060.657551][ C0] __pm_runtime_resume+0x47/0x80 2024-01-18T12:18:44.564648+00:00 tfrs-01 kernel: [ 3060.657552][ C0] __intel_runtime_pm_get+0x1e/0x90 [i915 78bbb16e393a51161506d14678c82dbe7746ab4e] 2024-01-18T12:18:44.564648+00:00 tfrs-01 kernel: [ 3060.657577][ C0] intel_display_power_get+0x24/0x60 [i915 78bbb16e393a51161506d14678c82dbe7746ab4e] 2024-01-18T12:18:44.564649+00:00 tfrs-01 kernel: [ 3060.657614][ C0] intel_digital_port_connected+0x3a/0xa0 [i915 78bbb16e393a51161506d14678c82dbe7746ab4e] 2024-01-18T12:18:44.564649+00:00 tfrs-01 kernel: [ 3060.657645][ C0] intel_dp_detect+0x2c8/0x660 [i915 78bbb16e393a51161506d14678c82dbe7746ab4e] 2024-01-18T12:18:44.564649+00:00 tfrs-01 kernel: [ 3060.657675][ C0] ? newidle_balance+0x2f0/0x440 2024-01-18T12:18:44.564649+00:00 tfrs-01 kernel: [ 3060.657676][ C0] drm_helper_probe_detect_ctx+0x6a/0xf0 [drm_kms_helper 27a7978049953ab8be9c7870f7a6b929411f05a2] 2024-01-18T12:18:44.564650+00:00 tfrs-01 kernel: [ 3060.657682][ C0] output_poll_execute+0x116/0x1f0 [drm_kms_helper 27a7978049953ab8be9c7870f7a6b929411f05a2] 2024-01-18T12:18:44.564650+00:00 tfrs-01 kernel: [ 3060.657686][ C0] process_one_work+0x264/0x440 2024-01-18T12:18:44.564650+00:00 tfrs-01 kernel: [ 3060.657688][ C0] worker_thread+0x2d/0x3c0 2024-01-18T12:18:44.564650+00:00 tfrs-01 kernel: [ 3060.657689][ C0] ? process_one_work+0x440/0x440 2024-01-18T12:18:44.564651+00:00 tfrs-01 kernel: [ 3060.657690][ C0] kthread+0x154/0x180 2024-01-18T12:18:44.564651+00:00 tfrs-01 kernel: [ 3060.657691][ C0] ? set_kthread_struct+0x50/0x50 2024-01-18T12:18:44.564651+00:00 tfrs-01 kernel: [ 3060.657692][ C0] ret_from_fork+0x1f/0x30 2024-01-18T12:18:44.564652+00:00 tfrs-01 kernel: [ 3060.657694][ C0] </TASK> --- snip END --- Is there any chance to get this fixed somehow ? Thank you Kind Regards Christian -- You are receiving this mail because: You are the assignee for the bug.

1 30

[Bug 1219056] New: ASUS Expertbook B5302F - system doesn't sleep properly, no s0 residency in s2idle
by bugzilla_noreply＠suse.com 05 Feb '24

05 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1219056 Bug ID: 1219056 Summary: ASUS Expertbook B5302F - system doesn't sleep properly, no s0 residency in s2idle 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: davor.virag(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:121.0) Gecko/20100101 Firefox/121.0 Build Identifier: I'm using Intel's S0ixSelftestTool (https://github.com/intel/S0ixSelftestTool/) as I was getting seemingly high battery drain in sleep. According to the logs, it can get the CPU into PC10 state, but the logs state: "Your system supports S0ix substates, but did not achieve the shallowest s0i2.0" I have tried "powertop --calibrate" and "powertop --auto-tune", but the s0 self-etst logs still look the same Reproducible: Always Steps to Reproduce: 1. Run "s0ix-selftest-tool.sh -s" 2. Check for s0 residency Actual Results: CPU Core C7 residency after S2idle is: 98.34 GFX RC6 residency after S2idle is: CPU Package C-state 2 residency after S2idle is: 2.79 CPU Package C-state 3 residency after S2idle is: 2.26 CPU Package C-state 8 residency after S2idle is: 0.21 CPU Package C-state 9 residency after S2idle is: 1.33 CPU Package C-state 10 residency after S2idle is: 88.21 S0ix residency after S2idle is: 0.00 Your system supports S0ix substates, but did not achieve the shallowest s0i2.0 Here is the S0ix substates status: Substate Residency S0i2.0 0 S0i3.0 0 (...) Did not detect the potential blockers from substate_requirements, need to check substate_status_registers file for the advanced debug. (...) Your system south port controller power gating state is OK after 30 seconds runtime check. Expected Results: Residency in one of the s0 states -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1219242] New: [Build 20240125] openQA test fails in fallocate06
by bugzilla_noreply＠suse.com 02 Feb '24

02 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1219242 Bug ID: 1219242 Summary: [Build 20240125] openQA test fails in fallocate06 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3895229/modules/fall ocate06/steps/6 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ana.guerrero(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation There wasn't a kernel update today but this LTP test started failing in different workers: ----snip---- # wait_serial expected: qr/### TEST fallocate06 COMPLETE >>> \d+\./u # Result: tst_device.c:293: TWARN: Failed to create test_dev.img: ENOSPC (28) tst_device.c:354: TBROK: Failed to acquire device HINT: You _MAY_ be missing kernel fixes: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?… https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?… Summary: passed 0 failed 0 broken 1 skipped 0 warnings 1 ### TEST fallocate06 COMPLETE >>> 6. ----snip---- openQA test in scenario opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos-ltp-syscalls@uefi_virtio-2G fails in [fallocate06](https://openqa.opensuse.org/tests/3895229/modules/fallocate06/… ## Test suite description ## Reproducible Fails since (at least) Build [20240123](https://openqa.opensuse.org/tests/3888826) ## Expected result Last good: [20240122](https://openqa.opensuse.org/tests/3886452) (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 1

[Bug 1219275] New: user interface slow (regression)
by bugzilla_noreply＠suse.com 31 Jan '24

31 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219275 Bug ID: 1219275 Summary: user interface slow (regression) 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: aschnell(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- With the latest kernel-default 6.7.1-1.1 the user interface is slower than before with 6.6.11-1.1. E.g. I can clearly see how windows are redrawn (e.g. content of xterm). I can pinpoint this to the kernel since booting the old kernel resolves the problem. System information: Intel(R) Xeon(R) W-2123 CPU @ 3.60GHz 32 GiB RAM NVIDIA Corporation GP107GL [Quadro P600] (rev a1) using nouveau -- You are receiving this mail because: You are the assignee for the bug.

1 13

[Bug 1219361] New: Kernel 6.7.1-2.1 module conflict during update
by bugzilla_noreply＠suse.com 31 Jan '24

31 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219361 Bug ID: 1219361 Summary: Kernel 6.7.1-2.1 module conflict during update 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: db(a)mail25.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 872326 --> https://bugzilla.suse.com/attachment.cgi?id=872326&action=edit zypper logs Ran `zypper dup` today and got errors about conflicting kernel module files. The following 2 packages are going to be upgraded: openSUSE-release openSUSE-release-appliance-custom The following product is going to be upgraded: openSUSE Tumbleweed 20240126-0 -> 20240128-0 The following 2 packages are going to be reinstalled: kernel-default-6.7.1-2.1 kernel-default-devel-6.7.1-2.1 Was there a packaging error or is something messed up on my system? I already have kernel-default-6.7.1-2.1 installed but zypper seems to see the one installed as different from the one in the repo: > sudo zypper se -s kernel-default Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository ---+-----------------------------+---------+----------------+--------+----------------------------- i+ | kernel-default | package | 6.7.1-2.1 | x86_64 | (System Packages) i+ | kernel-default | package | 6.7.1-1.1 | x86_64 | (System Packages) v | kernel-default | package | 6.7.1-2.1 | x86_64 | openSUSE-Tumbleweed-Main-OSS Attached zypper logs. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1219284] increased ram usage after upgrading from 6.6.x to 6.7.x
by bugzilla_noreply＠suse.com 30 Jan '24

30 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219284 https://bugzilla.suse.com/show_bug.cgi?id=1219284#c16 --- Comment #16 from Michal Hocko <mhocko(a)suse.com> --- (In reply to Daniel Wagner from comment #14) > Ah Thorsten Leemhuise corrected himself, it seems to be > > 4ef9ad19e17676 ("mm: huge_memory: don't force huge page alignment on 32 > bit") > > but according some testing by the Arch folks it is not a complete fix. Nope, this only affects 32b apps on 64b systems. And it mostly breaks ASLR (see bug 1218800. This should be already in stable kernel branch -- You are receiving this mail because: You are the assignee for the bug.

1 0