October 2024 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1231268] [Build 20241001] openQA test fails in cve-2017-17806
by bugzilla_noreply＠suse.com 04 Oct '24

04 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231268 https://bugzilla.suse.com/show_bug.cgi?id=1231268#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Avinesh Kumar from comment #1) > > git show ce212d2afca47acd366a2e74c76fe82c31f785ab > commit ce212d2afca47acd366a2e74c76fe82c31f785ab > Author: Herbert Xu <herbert(a)gondor.apana.org.au> > Date: Tue Sep 10 17:30:24 2024 +0800 > > crypto: n2 - Set err to EINVAL if snprintf fails for hmac > > Return EINVAL if the snprintf check fails when constructing the > algorithm names. > > Fixes: 8c20982caca4 ("crypto: n2 - Silence gcc format-truncation false > positive warnings") > Reported-by: kernel test robot <lkp(a)intel.com> > Reported-by: Dan Carpenter <dan.carpenter(a)linaro.org> > Closes: https://lore.kernel.org/r/202409090726.TP0WfY7p-lkp@intel.com/ > Signed-off-by: Herbert Xu <herbert(a)gondor.apana.org.au> > > diff --git a/drivers/crypto/n2_core.c b/drivers/crypto/n2_core.c > index 251e088a53df..b11545cc5cb7 100644 > --- a/drivers/crypto/n2_core.c > +++ b/drivers/crypto/n2_core.c > @@ -1353,6 +1353,7 @@ static int __n2_register_one_hmac(struct n2_ahash_alg > *n2ahash) > ahash->setkey = n2_hmac_async_setkey; > > base = &ahash->halg.base; > + err = -EINVAL; > if (snprintf(base->cra_name, CRYPTO_MAX_ALG_NAME, "hmac(%s)", > p->child_alg) >= CRYPTO_MAX_ALG_NAME) > goto out_free_p; > _______________ > > > this commit might be related which went in 6.12-rc1 is related. Hm, this driver is for Niagara2 on Sparc64, hence it must be irrelevant. But there can be other crypto changes that return -EINVAL. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1230835] Lenovo Trackpoint doesn't work with Kernel 6.4.0-150600.312.g1e42d2f-default from SLE 15 SP6
by bugzilla_noreply＠suse.com 03 Oct '24

03 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230835 https://bugzilla.suse.com/show_bug.cgi?id=1230835#c4 Peer Heinlein <p.heinlein(a)heinlein-support.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(p.heinlein@heinle | |in-support.de) | --- Comment #4 from Peer Heinlein <p.heinlein(a)heinlein-support.de> --- It's working for me with the latest kernel. Looks like it's fixed. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231268] New: [Build 20241001] openQA test fails in cve-2017-17806
by bugzilla_noreply＠suse.com 03 Oct '24

03 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231268 Bug ID: 1231268 Summary: [Build 20241001] openQA test fails in cve-2017-17806 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/4526310/modules/cve- 2017-17806/steps/8 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: avinesh.kumar(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-ltp_cve_kotd@64bit fails in [cve-2017-17806](https://openqa.opensuse.org/tests/4526310/modules/cve-2017-… ltp test: https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/cryp… /* * Regression test for commit af3ff8045bbf ("crypto: hmac - require that the * underlying hash algorithm is unkeyed"), or CVE-2017-17806. This test * verifies that the hmac template cannot be nested inside itself. */ ## Reproducible Fails since Build [20241001](https://openqa.opensuse.org/tests/4526310) (openSUSE Tumbleweed 20241001 - Kernel 6.12.0-rc1-1.gfcf4d55-default) ## Expected result Last good: [20240930](https://openqa.opensuse.org/tests/4523252) (openSUSE Tumbleweed 20240930 - Kernel 6.11.0-3.g746ccde-default) ## 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 1230418] [REGRESSION] laptop refuses to go to sleep and starts stuttering when battery is full
by bugzilla_noreply＠suse.com 03 Oct '24

03 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230418 https://bugzilla.suse.com/show_bug.cgi?id=1230418#c13 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #13 from Takashi Iwai <tiwai(a)suse.com> --- It's hard to say what prevents suspending. You can test the direct suspend by echo mem > /sys/power/state as root user. This skips the whole user-space side hooks and checks and triggers the kernel suspend. If this works, it means something in user-space causes the problem. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1230893] MCE on HP ProBook laptop
by bugzilla_noreply＠suse.com 03 Oct '24

03 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230893 https://bugzilla.suse.com/show_bug.cgi?id=1230893#c2 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Kernel panic/kernel crash |MCE on HP ProBook laptop |on HP ProBook laptop | CC| |jslaby(a)suse.com --- Comment #2 from Jiri Slaby <jslaby(a)suse.com> --- FTR, you received an mce: > mce: [Hardware Error]: CPU 1: Machine Check Exception: 5 Bank 3: ba00000000020179 > mce: [Hardware Error]: RIP !INEXACT! 33:<00007f7ab5d3509a> > mce: [Hardware Error]: TSC 36516fb17ef MISC 174285 > mce: [Hardware Error]: PROCESSOR 0:806c1 TIME 1726834185 SOCKET 0 APIC 2 microcode b8 > mce: [Hardware Error]: Run the above through 'mcelog --ascii' > mce: [Hardware Error]: Machine check: Processor context corrupt > Kernel panic - not syncing: Fatal machine check -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1213783] Failure to boot after upgrade or from a live usb with latest iso.
by bugzilla_noreply＠suse.com 03 Oct '24

03 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1213783 https://bugzilla.suse.com/show_bug.cgi?id=1213783#c8 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |jslaby(a)suse.com Resolution|--- |NORESPONSE --- Comment #8 from Jiri Slaby <jslaby(a)suse.com> --- As soon as you provide the requested info, feel free to reopen. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1230629] New: Lenovo T14 Gen 5 (Intel Meteor Lake) immediately wakes up from suspend
by bugzilla_noreply＠suse.com 02 Oct '24

02 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230629 Bug ID: 1230629 Summary: Lenovo T14 Gen 5 (Intel Meteor Lake) immediately wakes up from suspend Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: shundhammer(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 877385 --> https://bugzilla.suse.com/attachment.cgi?id=877385&action=edit Tarball with system logs, hwinfo, packages info, BIOS screenshots My brand new Lenovo ThinkPad T14 Gen 5 (Intel Core 5 Ultra 125U with Meteor Lake chipset) immediately wakes up again when I try to suspend it to RAM, and there are some errors in the logs: sudo systemctl suspend ...screen goes black... ...screen flickers... ...power LED blinks... ...screen comes back again... ...network status icon shows disconnected... ...network reconnects... -> the machine is back awake as if nothing ever happened. This happens with the current Slowroll kernel and with the current Tumbleweed kernel. It does work with a Xubuntu 22.04.01 LTS live ISO with the older 6.8 kernel, though: - kernel-default-6.10.9-1.1.x86_64 (Tumbleweed) -> wakes up immediately - kernel-default-6.10.8-1.1.x86_64 (Slowroll) -> wakes up immediately - kernel 6.8.? (Xubuntu 22.04.01 live ISO) -> suspends as expected, resumes as expected >> inxi >> >> CPU: 12-core (2-mt/10-st) Intel Core Ultra 5 125U (-MST AMCP-) >> speed/min/max: 400/400/4300:3600:2100 MHz Kernel: 6.10.9-1-default x86_64 >> Up: 0h 7m Mem: 1.08/15.12 GiB (7.1%) Storage: 953.87 GiB (12.2% used) >> Procs: 361 Shell: Zsh inxi: 3.3.36 I already did update the (UEFI) BIOS to the latest one, reset the BIOS settings to factory defaults, and updated the kernel-firmware packages to the latest one from Tumbleweed; none of that helped. For more system info, please see the attached tarball: Lenovo-T14-suspend-bug ├── BIOS-screenshots │ ├── T14-BIOS-01-Main.jpg │ ├── T14-BIOS-02-Power-Settings.jpg │ └── T17-BIOS-03-Power-On.jpg ├── hardware │ ├── hwinfo.log │ ├── inxi-full.log │ ├── inxi.log │ └── inxi-machine.log ├── messages │ ├── dmesg-after-suspend.log │ ├── dmesg-before-suspend.log │ ├── dmesg.diff │ ├── journalctl-b-after-suspend.log │ ├── journalctl-b-before-suspend.log │ └── journalctl-b.diff └── packages ├── rpm-qa-last.txt └── zypp-history.log journalctl -b diff before and after the suspend: >> Sep 17 10:35:22 meteor systemd-logind[976]: The system will suspend now! >> Sep 17 10:35:22 meteor ModemManager[1079]: <info> [sleep-monitor-systemd] system is about to suspend >> Sep 17 10:35:22 meteor NetworkManager[1089]: <info> [1726562122.7931] manager: sleep: sleep requested (sleeping: no enabled: yes) >> Sep 17 10:35:22 meteor NetworkManager[1089]: <info> [1726562122.7932] device (p2p-dev-wlp0s20f3): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', sys-iface-state: 'managed') >> Sep 17 10:35:22 meteor NetworkManager[1089]: <info> [1726562122.7938] manager: NetworkManager state is now ASLEEP >> Sep 17 10:35:22 meteor NetworkManager[1089]: <info> [1726562122.7940] device (wlp0s20f3): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed') >> Sep 17 10:35:22 meteor sudo[2349]: pam_unix(sudo:session): session closed for user root >> Sep 17 10:35:22 meteor systemd[1]: Starting Network Manager Script Dispatcher Service... >> Sep 17 10:35:22 meteor systemd[1]: Started Network Manager Script Dispatcher Service. >> Sep 17 10:35:22 meteor kernel: wlp0s20f3: deauthenticating from c8:0e:14:46:50:44 by local choice (Reason: 3=DEAUTH_LEAVING) >> Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.0377] device (wlp0s20f3): supplicant interface state: completed -> disconnected >> Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.0379] device (wlp0s20f3): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed') >> Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.0384] dhcp4 (wlp0s20f3): canceled DHCP transaction >> Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.0384] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds) >> Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.0384] dhcp4 (wlp0s20f3): state changed no lease >> Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.0386] dhcp6 (wlp0s20f3): canceled DHCP transaction >> Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.0386] dhcp6 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds) >> Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.0386] dhcp6 (wlp0s20f3): state changed no lease >> Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.0819] device (wlp0s20f3): set-hw-addr: set MAC address to D6:6B:75:DD:7E:C9 (scanning) >> Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.1987] device (wlp0s20f3): supplicant interface state: disconnected -> interface_disabled >> Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.1988] device (wlp0s20f3): supplicant interface state: interface_disabled -> disconnected >> Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.1991] device (wlp0s20f3): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', sys-iface-state: 'managed') >> Sep 17 10:35:23 meteor chronyd[1208]: Removed source fd00::ca0e:14ff:fe46:503e >> Sep 17 10:35:23 meteor chronyd[1208]: Source 192.168.178.1 offline >> Sep 17 10:35:23 meteor chronyd[1208]: Can't synchronise: no selectable sources >> Sep 17 10:35:23 meteor chronyd[1208]: Source 85.215.189.120 offline >> Sep 17 10:35:23 meteor dns-dnsmasq.sh[2368]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit >> Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.3482] device (wlp0s20f3): set-hw-addr: reset MAC address to 28:A0:6B:33:40:FA (unmanage) >> Sep 17 10:35:23 meteor systemd[1]: Reached target Sleep. >> Sep 17 10:35:23 meteor systemd[1]: Starting System Suspend... >> Sep 17 10:35:23 meteor dns-dnsmasq.sh[2384]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit >> Sep 17 10:35:23 meteor systemd-sleep[2378]: User sessions remain unfrozen (add $SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=1 to override), >> Sep 17 10:35:23 meteor systemd-sleep[2378]: relying on kernel to perform the freeze. >> Sep 17 10:35:23 meteor systemd-sleep[2378]: This is a temporary downstream workaround for https://github.com/systemd/systemd/issues/33083. >> Sep 17 10:35:23 meteor systemd-sleep[2392]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend >> Sep 17 10:35:23 meteor systemd-sleep[2378]: Performing sleep operation 'suspend'... >> Sep 17 10:35:23 meteor kernel: PM: suspend entry (s2idle) >> Sep 17 10:35:23 meteor kernel: Filesystems sync: 0.002 seconds >> Sep 17 10:35:24 meteor kernel: Freezing user space processes >> Sep 17 10:35:24 meteor kernel: Freezing user space processes completed (elapsed 0.001 seconds) >> Sep 17 10:35:24 meteor kernel: OOM killer disabled. >> Sep 17 10:35:24 meteor kernel: Freezing remaining freezable tasks >> Sep 17 10:35:24 meteor kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds) >> Sep 17 10:35:24 meteor kernel: printk: Suspending console(s) (use no_console_suspend to debug) >> Sep 17 10:35:24 meteor kernel: e1000e: EEE TX LPI TIMER: 00000011 >> Sep 17 10:35:24 meteor kernel: e1000e 0000:00:1f.6: PM: pci_pm_suspend(): e1000e_pm_suspend [e1000e] returns -2 >> Sep 17 10:35:24 meteor kernel: e1000e 0000:00:1f.6: PM: dpm_run_callback(): pci_pm_suspend returns -2 >> Sep 17 10:35:24 meteor kernel: e1000e 0000:00:1f.6: PM: failed to suspend async: error -2 >> Sep 17 10:35:24 meteor kernel: PM: Some devices failed to suspend, or early wake event detected >> Sep 17 10:35:24 meteor kernel: i915 0000:00:02.0: [drm] GT0: GuC firmware i915/mtl_guc_70.bin version 70.29.2 >> Sep 17 10:35:24 meteor kernel: iwlwifi 0000:00:14.3: WRT: Invalid buffer destination >> Sep 17 10:35:24 meteor kernel: i915 0000:00:02.0: [drm] GT0: GUC: submission enabled >> Sep 17 10:35:24 meteor kernel: i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled >> Sep 17 10:35:24 meteor kernel: i915 0000:00:02.0: [drm] GT0: GUC: RC enabled >> Sep 17 10:35:24 meteor kernel: i915 0000:00:02.0: [drm] GT1: GuC firmware i915/mtl_guc_70.bin version 70.29.2 >> Sep 17 10:35:24 meteor kernel: i915 0000:00:02.0: [drm] GT1: HuC firmware i915/mtl_huc_gsc.bin version 8.5.4 >> Sep 17 10:35:24 meteor kernel: nvme nvme0: 14/0/0 default/read/poll queues >> Sep 17 10:35:24 meteor kernel: i915 0000:00:02.0: [drm] GT1: GUC: submission enabled >> Sep 17 10:35:24 meteor kernel: i915 0000:00:02.0: [drm] GT1: GUC: SLPC enabled >> Sep 17 10:35:24 meteor kernel: i915 0000:00:02.0: [drm] GT1: GUC: RC enabled >> Sep 17 10:35:24 meteor kernel: iwlwifi 0000:00:14.3: Not valid error log pointer 0x0024B5C0 for RT uCode >> Sep 17 10:35:24 meteor kernel: iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x1f >> Sep 17 10:35:24 meteor kernel: iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f >> Sep 17 10:35:24 meteor kernel: iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x80 >> Sep 17 10:35:24 meteor kernel: iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x0 >> Sep 17 10:35:24 meteor kernel: iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4 >> Sep 17 10:35:24 meteor kernel: mei_gsc_proxy 0000:00:16.0-0f73db04-97ab-4125-b893-e904ad0d5464: bound 0000:00:02.0 (ops i915_gsc_proxy_component_ops [i915]) >> Sep 17 10:35:24 meteor kernel: OOM killer enabled. >> Sep 17 10:35:24 meteor kernel: Restarting tasks ... done. >> Sep 17 10:35:24 meteor kernel: random: crng reseeded on system resumption >> Sep 17 10:35:25 meteor kernel: PM: suspend exit >> Sep 17 10:35:25 meteor kernel: PM: suspend entry (s2idle) >> Sep 17 10:35:25 meteor kernel: Filesystems sync: 0.019 seconds >> Sep 17 10:35:26 meteor kernel: Freezing user space processes >> Sep 17 10:35:26 meteor kernel: Freezing user space processes completed (elapsed 0.001 seconds) >> Sep 17 10:35:26 meteor kernel: OOM killer disabled. >> Sep 17 10:35:26 meteor kernel: Freezing remaining freezable tasks >> Sep 17 10:35:26 meteor kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds) >> Sep 17 10:35:26 meteor kernel: printk: Suspending console(s) (use no_console_suspend to debug) >> Sep 17 10:35:26 meteor kernel: e1000e: EEE TX LPI TIMER: 00000011 >> Sep 17 10:35:26 meteor kernel: e1000e 0000:00:1f.6: PM: pci_pm_suspend(): e1000e_pm_suspend [e1000e] returns -2 >> Sep 17 10:35:26 meteor kernel: e1000e 0000:00:1f.6: PM: dpm_run_callback(): pci_pm_suspend returns -2 >> Sep 17 10:35:26 meteor kernel: e1000e 0000:00:1f.6: PM: failed to suspend async: error -2 >> Sep 17 10:35:26 meteor kernel: PM: Some devices failed to suspend, or early wake event detected >> Sep 17 10:35:26 meteor kernel: i915 0000:00:02.0: [drm] GT0: GuC firmware i915/mtl_guc_70.bin version 70.29.2 >> Sep 17 10:35:26 meteor kernel: iwlwifi 0000:00:14.3: WRT: Invalid buffer destination >> Sep 17 10:35:26 meteor kernel: i915 0000:00:02.0: [drm] GT0: GUC: submission enabled >> Sep 17 10:35:26 meteor kernel: i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled >> Sep 17 10:35:26 meteor kernel: i915 0000:00:02.0: [drm] GT0: GUC: RC enabled >> Sep 17 10:35:26 meteor kernel: i915 0000:00:02.0: [drm] GT1: GuC firmware i915/mtl_guc_70.bin version 70.29.2 >> Sep 17 10:35:26 meteor kernel: i915 0000:00:02.0: [drm] GT1: HuC firmware i915/mtl_huc_gsc.bin version 8.5.4 >> Sep 17 10:35:26 meteor kernel: nvme nvme0: 14/0/0 default/read/poll queues >> Sep 17 10:35:26 meteor kernel: i915 0000:00:02.0: [drm] GT1: GUC: submission enabled >> Sep 17 10:35:26 meteor kernel: i915 0000:00:02.0: [drm] GT1: GUC: SLPC enabled >> Sep 17 10:35:26 meteor kernel: i915 0000:00:02.0: [drm] GT1: GUC: RC enabled >> Sep 17 10:35:26 meteor kernel: iwlwifi 0000:00:14.3: Not valid error log pointer 0x0024B5C0 for RT uCode >> Sep 17 10:35:26 meteor kernel: iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x1f >> Sep 17 10:35:26 meteor kernel: iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f >> Sep 17 10:35:26 meteor kernel: iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x80 >> Sep 17 10:35:26 meteor kernel: iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x0 >> Sep 17 10:35:26 meteor kernel: iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4 >> Sep 17 10:35:26 meteor kernel: mei_gsc_proxy 0000:00:16.0-0f73db04-97ab-4125-b893-e904ad0d5464: bound 0000:00:02.0 (ops i915_gsc_proxy_component_ops [i915]) >> Sep 17 10:35:26 meteor kernel: OOM killer enabled. >> Sep 17 10:35:26 meteor kernel: Restarting tasks ... done. >> Sep 17 10:35:26 meteor kernel: random: crng reseeded on system resumption >> Sep 17 10:35:26 meteor systemd[1502]: Started dbus-:1.2-org.xfce.Xfconf@1.service. >> Sep 17 10:35:26 meteor systemd-sleep[2378]: Failed to put system to sleep. System resumed again: No such file or directory >> Sep 17 10:35:26 meteor kernel: PM: suspend exit >> Sep 17 10:35:26 meteor systemd-sleep[2468]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend >> Sep 17 10:35:26 meteor systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE >> Sep 17 10:35:26 meteor systemd[1]: systemd-suspend.service: Failed with result 'exit-code'. >> Sep 17 10:35:26 meteor systemd[1]: Failed to start System Suspend. >> Sep 17 10:35:26 meteor systemd[1]: Dependency failed for Suspend. >> Sep 17 10:35:26 meteor systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'. >> Sep 17 10:35:26 meteor systemd-logind[976]: Operation 'suspend' finished. >> Sep 17 10:35:26 meteor systemd[1]: Stopped target Sleep. >> Sep 17 10:35:26 meteor ModemManager[1079]: <info> [sleep-monitor-systemd] system is resuming >> Sep 17 10:35:26 meteor NetworkManager[1089]: <info> [1726562126.5424] manager: sleep: wake requested (sleeping: yes enabled: yes) >> Sep 17 10:35:26 meteor NetworkManager[1089]: <info> [1726562126.5425] device (enp0s31f6): state change: unavailable -> unmanaged (reason 'unmanaged-sleeping', sys-iface-state: 'managed') >> Sep 17 10:35:28 meteor kernel: e1000e 0000:00:1f.6 enp0s31f6: Hardware Error >> Sep 17 10:35:29 meteor ModemManager[1079]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:14.3': not supported by any plugin >> Sep 17 10:35:29 meteor ModemManager[1079]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1f.6': not supported by any plugin >> Sep 17 10:35:29 meteor NetworkManager[1089]: <info> [1726562129.9289] device (enp0s31f6): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') >> Sep 17 10:35:29 meteor kernel: e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Down >> Sep 17 10:35:31 meteor kernel: e1000e 0000:00:1f.6 enp0s31f6: Hardware Error >> Sep 17 10:35:33 meteor systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. >> Sep 17 10:35:34 meteor NetworkManager[1089]: <info> [1726562134.3875] device (wlp0s20f3): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') >> Sep 17 10:35:34 meteor NetworkManager[1089]: <info> [1726562134.3884] device (p2p-dev-wlp0s20f3): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') >> Sep 17 10:35:34 meteor NetworkManager[1089]: <info> [1726562134.3887] manager: NetworkManager state is now DISCONNECTED >> Sep 17 10:35:34 meteor NetworkManager[1089]: <info> [1726562134.4327] device (wlp0s20f3): supplicant interface state: internal-starting -> disconnected >> Sep 17 10:35:34 meteor NetworkManager[1089]: <info> [1726562134.4327] device (p2p-dev-wlp0s20f3): state change: unavailable -> unmanaged (reason 'unmanaged-link-not-init', sys-iface-state: 'removed') >> Sep 17 10:35:34 meteor NetworkManager[1089]: <info> [1726562134.4331] Wi-Fi P2P device controlled by interface wlp0s20f3 created >> Sep 17 10:35:34 meteor NetworkManager[1089]: <info> [1726562134.4333] manager: (p2p-dev-wlp0s20f3): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/5) >> Sep 17 10:35:34 meteor NetworkManager[1089]: <info> [1726562134.4335] device (p2p-dev-wlp0s20f3): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') >> Sep 17 10:35:34 meteor NetworkManager[1089]: <info> [1726562134.4337] device (wlp0s20f3): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed') >> Sep 17 10:35:34 meteor NetworkManager[1089]: <info> [1726562134.4341] device (p2p-dev-wlp0s20f3): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed') >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1404] policy: auto-activating connection 'wlp0s20f3' (ed77ffbb-f7b5-3841-8b21-258e99306b9f) >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1409] device (wlp0s20f3): Activation: starting connection 'wlp0s20f3' (ed77ffbb-f7b5-3841-8b21-258e99306b9f) >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1409] device (wlp0s20f3): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1413] manager: NetworkManager state is now CONNECTING >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1418] device (wlp0s20f3): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1422] device (wlp0s20f3): Activation: (wifi) access point 'wlp0s20f3' has security, but secrets are required. >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1422] device (wlp0s20f3): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1425] sup-iface[2dde45278d9b93ec,1,wlp0s20f3]: wps: type pbc start... >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1437] device (wlp0s20f3): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1440] device (wlp0s20f3): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1443] device (wlp0s20f3): Activation: (wifi) connection 'wlp0s20f3' has security, and secrets exist. No new secrets needed. >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1444] Config: added 'ssid' value 'Hundhammer' >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1444] Config: added 'scan_ssid' value '1' >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1444] Config: added 'bgscan' value 'simple:30:-65:300' >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1444] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE' >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1444] Config: added 'auth_alg' value 'OPEN' >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1445] Config: added 'psk' value '<hidden>' >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1452] device (wlp0s20f3): supplicant interface state: disconnected -> scanning >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1452] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> scanning >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1955] device (wlp0s20f3): supplicant interface state: scanning -> authenticating >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1955] device (p2p-dev-wlp0s20f3): supplicant management interface state: scanning -> authenticating >> Sep 17 10:35:38 meteor kernel: wlp0s20f3: authenticate with c8:0e:14:46:50:44 (local address=28:a0:6b:33:40:fa) >> Sep 17 10:35:38 meteor kernel: wlp0s20f3: send auth to c8:0e:14:46:50:44 (try 1/3) >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.2279] device (wlp0s20f3): supplicant interface state: authenticating -> associating >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.2279] device (p2p-dev-wlp0s20f3): supplicant management interface state: authenticating -> associating >> Sep 17 10:35:38 meteor kernel: wlp0s20f3: authenticated >> Sep 17 10:35:38 meteor kernel: wlp0s20f3: associate with c8:0e:14:46:50:44 (try 1/3) >> Sep 17 10:35:38 meteor kernel: wlp0s20f3: RX AssocResp from c8:0e:14:46:50:44 (capab=0x1511 status=0 aid=5) >> Sep 17 10:35:38 meteor kernel: wlp0s20f3: associated >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.2422] device (wlp0s20f3): supplicant interface state: associating -> associated >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.2422] device (p2p-dev-wlp0s20f3): supplicant management interface state: associating -> associated >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.2493] device (wlp0s20f3): supplicant interface state: associated -> 4way_handshake >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.2493] device (p2p-dev-wlp0s20f3): supplicant management interface state: associated -> 4way_handshake >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.3140] device (wlp0s20f3): supplicant interface state: 4way_handshake -> completed >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.3141] device (wlp0s20f3): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Hundhammer" >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.3141] device (p2p-dev-wlp0s20f3): supplicant management interface state: 4way_handshake -> completed >> Sep 17 10:35:38 meteor kernel: wlp0s20f3: Limiting TX power to 20 (23 - 3) dBm as advertised by c8:0e:14:46:50:44 >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.3359] device (wlp0s20f3): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.3364] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds) >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.3439] dhcp4 (wlp0s20f3): state changed new lease, address=192.168.178.166, acd pending >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.5129] dhcp4 (wlp0s20f3): state changed new lease, address=192.168.178.166 >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.5134] policy: set 'wlp0s20f3' (wlp0s20f3) as default for IPv4 routing and DNS >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.5196] device (wlp0s20f3): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') >> Sep 17 10:35:38 meteor systemd[1]: Starting Network Manager Script Dispatcher Service... >> Sep 17 10:35:38 meteor systemd[1]: Started Network Manager Script Dispatcher Service. >> Sep 17 10:35:38 meteor chronyd[1208]: Source 192.168.178.1 online >> Sep 17 10:35:38 meteor chronyd[1208]: Source 85.215.189.120 online >> Sep 17 10:35:38 meteor dns-dnsmasq.sh[2493]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.6113] device (wlp0s20f3): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.6116] device (wlp0s20f3): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.6120] manager: NetworkManager state is now CONNECTED_SITE >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.6128] device (wlp0s20f3): Activation: successful, device activated. >> Sep 17 10:35:38 meteor chronyd[1208]: Could not add source 192.168.178.1 : Already in use >> Sep 17 10:35:38 meteor dns-dnsmasq.sh[2520]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit >> Sep 17 10:35:38 meteor dns-dnsmasq.sh[2534]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit >> Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.7622] manager: NetworkManager state is now CONNECTED_GLOBAL >> Sep 17 10:35:38 meteor chronyd[1208]: Selected source 192.168.178.1 >> Sep 17 10:35:38 meteor dns-dnsmasq.sh[2547]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit >> Sep 17 10:35:39 meteor NetworkManager[1089]: <info> [1726562139.5709] dhcp6 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds) >> Sep 17 10:35:39 meteor NetworkManager[1089]: <info> [1726562139.5717] policy: set 'wlp0s20f3' (wlp0s20f3) as default for IPv6 routing and DNS >> Sep 17 10:35:39 meteor NetworkManager[1089]: <info> [1726562139.5833] dhcp6 (wlp0s20f3): state changed new lease >> Sep 17 10:35:39 meteor chronyd[1208]: Could not add source 192.168.178.1 : Already in use >> Sep 17 10:35:39 meteor chronyd[1208]: Added source fd00::ca0e:14ff:fe46:503e >> Sep 17 10:35:39 meteor dns-dnsmasq.sh[2576]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit >> Sep 17 10:35:49 meteor systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. >> Sep 17 10:36:13 meteor sudo[2589]: pam_unix(sudo:session): session opened for user root(uid=0) by sh(uid=1000) >> Sep 17 10:36:13 meteor sudo[2589]: pam_unix(sudo:session): session closed for user root >> Sep 17 10:36:25 meteor sudo[2593]: pam_unix(sudo:session): session opened for user root(uid=0) by sh(uid=1000) It doesn't make a difference if I use "sudo systemctl suspend", select "suspend" from the LightDM menu or from the Xfce4 menu, or if I close the laptop lid. -- You are receiving this mail because: You are the assignee for the bug.

1 29

[Bug 1230418] [REGRESSION] laptop refuses to go to sleep and starts stuttering when battery is full
by bugzilla_noreply＠suse.com 02 Oct '24

02 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230418 https://bugzilla.suse.com/show_bug.cgi?id=1230418#c12 --- Comment #12 from Guillaume Pinchon <pinchon.guillaume(a)gmail.com> --- UPDATE3: that's still not fixed, even with the latest stable kernel, switching to Fedora this distro is unusable. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231167] New: Enable CONFIG_SCSI_UFS_QCOM for UFS support on QCOM platforms
by bugzilla_noreply＠suse.com 02 Oct '24

02 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231167 Bug ID: 1231167 Summary: Enable CONFIG_SCSI_UFS_QCOM for UFS support on QCOM platforms 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: rsalveti(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 877673 --> https://bugzilla.suse.com/attachment.cgi?id=877673&action=edit kernel config diff Hi, I'm validating openSUSE Tumbleweed on QCOM-based arm64 platforms (e.g. rb3gen2) and noticed the installer can't find the UFS controller. This patch enables CONFIG_SCSI_UFS_QCOM as module so it can identify UFS controllers on QCOM platforms. Patch attached. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1231247] New: [Build 20241001] openQA test fails in bcc
by bugzilla_noreply＠suse.com 02 Oct '24

02 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231247 Bug ID: 1231247 Summary: [Build 20241001] openQA test fails in bcc Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: PowerPC-64 URL: https://openqa.opensuse.org/tests/4527873/modules/bcc/ steps/19 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: avinesh.kumar(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes bcc test in openqa which basically installs bcc-tools and executes - `/usr/share/bcc/tools/btrfsdist 5 2` started failing in Build20240927 (Tumbleweed 20240927 - Kernel 6.11.0-1-default ) Last good: https://openqa.opensuse.org/tests/4510984#step/bcc/19 (Tumbleweed 20240925 - Kernel 6.10.11-1-default) Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=ppc64le&distri=opensu… -- You are receiving this mail because: You are the assignee for the bug.

1 3