October 2024 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1231465] Kernel 6.11.2-1 only a fraction of ram is available
by bugzilla_noreply＠suse.com 17 Oct '24

17 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231465 https://bugzilla.suse.com/show_bug.cgi?id=1231465#c25 --- Comment #25 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Jiri Slaby from comment #24) > Out of curiosity, could you boot several times: > https://github.com/jirislaby/collected_sources/tree/master/efi-dump-memattr As per PM, it output 6 times the same. I believe something corrupts the EFI memory. And it remains until cold booted. Given it is corrupted some later (the first boot is fine at this point), it might help to give KASAN a try. Could you try that: https://download.opensuse.org/repositories/home:/tiwai:/kernel:/stable-kasa… ? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231465] Kernel 6.11.2-1 only a fraction of ram is available
by bugzilla_noreply＠suse.com 17 Oct '24

17 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231465 https://bugzilla.suse.com/show_bug.cgi?id=1231465#c24 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(felix.niederwange | |r(a)suse.com) --- Comment #24 from Jiri Slaby <jslaby(a)suse.com> --- Out of curiosity, could you boot several times: https://github.com/jirislaby/collected_sources/tree/master/efi-dump-memattr prebuilt here: https://decibel.fi.muni.cz/~xslaby/n/myefi.efi (Put it to /boot/efi/EFI/boot/ and persuade bios to boot it.) To see if kernel (mapping) is at fault. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231465] Kernel 6.11.2-1 only a fraction of ram is available
by bugzilla_noreply＠suse.com 17 Oct '24

17 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231465 https://bugzilla.suse.com/show_bug.cgi?id=1231465#c23 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(felix.niederwange | |r(a)suse.com) | --- Comment #23 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Felix Niederwanger from comment #20) > I tried it now 8 times with the provided 6.11.3-4-default kernel from > https://build.opensuse.org/project/monitor/home:jirislaby:kernel-bsc1231465, > all times the system recognized 32 GiB of system memory. > > To cross-check I needed 2 reboot attempts with the 6.11.2 kernel to end up > with only 1.3 GiB. > > Did something else changed in the meantime, that would explain this? As I wrote, with my patch, it no longer wraps. So it should not eat all your ram. It eats now only: 0x0000000077535018-0x00000001429e9027 This is funny: > 08:30:26 ... efi: memattr: efi_memattr_init: tab=0x77526018 size=16+45*48=0x0000000000000880 > 08:47:54 ... efi: memattr: efi_memattr_init: tab=0x77535018 size=16+2*1705353216=0x00000000cb4b4010 > 08:51:23 ... efi: memattr: efi_memattr_init: tab=0x77535018 size=16+2*1705353216=0x00000000cb4b4010 > 08:56:03 ... efi: memattr: efi_memattr_init: tab=0x77535018 size=16+2*1705353216=0x00000000cb4b4010 > 08:59:48 ... efi: memattr: efi_memattr_init: tab=0x77535018 size=16+2*1705353216=0x00000000cb4b4010 With the first boot, your bios reported 45 tables (looks reasonable) of size 48 (this is correct). Subsequent boots of the kernel, the firmware got mad and reports 2 tables (wrong) of size 1705353216 (wrong!). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1225352] [Build 13.199] openQA test fails in prepare_firstboot: RPi3 not booting?
by bugzilla_noreply＠suse.com 17 Oct '24

17 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c47 --- Comment #47 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- (In reply to Patrik Jakobsson from comment #46) > Why is the test still failing? Shouldn't QA have the fix by now? There is a regression, since the test passed 9 days ago: https://openqa.opensuse.org/tests/4543603 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1230849] systemd[1]: bpf-restrict-fs: Failed to load BPF object: No such process
by bugzilla_noreply＠suse.com 17 Oct '24

17 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230849 Shung-Hsi Yu <shung-hsi.yu(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(shung-hsi.yu@suse | |.com) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1212696] Q965 with modesetting DIX GPU HANG
by bugzilla_noreply＠suse.com 16 Oct '24

16 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1212696 https://bugzilla.suse.com/show_bug.cgi?id=1212696#c26 Felix Miata <mrmazda(a)earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|Leap 15.5 |Leap 15.6 --- Comment #26 from Felix Miata <mrmazda(a)earthlink.net> --- In upstream report I commented again. Interestingly, 6.10.11 in TW is fine, while 6.10.11 in Debian Trixie is not, like 15.5 and 15.6. Thus, the problem might not be purely, or at all, upstream. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1225352] [Build 13.199] openQA test fails in prepare_firstboot: RPi3 not booting?
by bugzilla_noreply＠suse.com 16 Oct '24

16 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c46 --- Comment #46 from Patrik Jakobsson <patrik.jakobsson(a)suse.com> --- Why is the test still failing? Shouldn't QA have the fix by now? -- 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 16 Oct '24

16 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 3

[Bug 1230849] New: systemd[1]: bpf-restrict-fs: Failed to load BPF object: No such process
by bugzilla_noreply＠suse.com 16 Oct '24

16 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230849 Bug ID: 1230849 Summary: systemd[1]: bpf-restrict-fs: Failed to load BPF object: No such process Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: armv7 URL: https://openqa.opensuse.org/tests/4494789/modules/jour nal_check/steps/11 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-JeOS-for-AArch64-arm-jeos@aarch32-HD20G fails in [journal_check](https://openqa.opensuse.org/tests/4494789/modules/journal_ch… Journal shows: systemd[1]: bpf-restrict-fs: Failed to load BPF object: No such process ## Test suite description Maintainer: fvogt Start JeOS from the HDD image, configure it using the firstboot wizard and then run basic tests. console=tty0 added as needed for aarch64. ## Reproducible Fails since (at least) Build [20240625](https://openqa.opensuse.org/tests/4301144) ## Expected result Last good: [20240624](https://openqa.opensuse.org/tests/4298579) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=arm&distri=opensuse&f… -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1231722] New: [Build 20241015] openQA test fails in cve-2019-8912
by bugzilla_noreply＠suse.com 16 Oct '24

16 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231722 Bug ID: 1231722 Summary: [Build 20241015] openQA test fails in cve-2019-8912 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 URL: https://openqa.opensuse.org/tests/4566079/modules/cve- 2019-8912/steps/7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-JeOS-for-RPi-aarch64-jeos-ltp-cve@RPi4 fails in [cve-2019-8912](https://openqa.opensuse.org/tests/4566079/modules/cve-2019-8… Error log is: af_alg07.c:110: TFAIL: fchownat() failed to fail, kernel may be vulnerable Failed. Test took approximately 150.232929400052 seconds Some test output could not be parsed: 17 lines were ignored. ## Test suite description ## Reproducible Fails since (at least) Build [20241015](https://openqa.opensuse.org/tests/4565717) ## Expected result Last good: [20241014](https://openqa.opensuse.org/tests/4562581) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=opensu… -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1231470] After ugrading to kernel-default-6.11.2-1 system doesn't boot and caps lock key is blinking
by bugzilla_noreply＠suse.com 16 Oct '24

16 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231470 https://bugzilla.suse.com/show_bug.cgi?id=1231470#c5 --- Comment #5 from Jiri Slaby <jslaby(a)suse.com> --- Maybe improperly generated initrd? Or another kernel update fixed this? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231470] After ugrading to kernel-default-6.11.2-1 system doesn't boot and caps lock key is blinking
by bugzilla_noreply＠suse.com 16 Oct '24

16 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231470 https://bugzilla.suse.com/show_bug.cgi?id=1231470#c4 Wolfgang Engel <wolfgang.engel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID Flags|needinfo?(wolfgang.engel@su | |se.com) | --- Comment #4 from Wolfgang Engel <wolfgang.engel(a)suse.com> --- I disabled quite boot and the kernel booted without any issues. Also after rebooting again and doing a normal boot, the kernel was booting properly. I don't know what seems to be the issue but I will try to fetch more data when it occurs again. Thank you and sorry for the noise. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231662] New: [Build 20241014] openQA test of JeOS-extra fails in kdump_and_crash - Error updating initrd while calling 'mkdumprd'
by bugzilla_noreply＠suse.com 15 Oct '24

15 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231662 Bug ID: 1231662 Summary: [Build 20241014] openQA test of JeOS-extra fails in kdump_and_crash - Error updating initrd while calling 'mkdumprd' Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/4562566/modules/kdum p_and_crash/steps/47 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-JeOS-for-AArch64-aarch64-jeos-extra@aarch64-HD20G fails in [kdump_and_crash](https://openqa.opensuse.org/tests/4562566/modules/kdump_an… The screenshot shows: Error updating initrd while calling 'mkdumprd' ## Test suite description Same as jeos, plus some more tests. ## Reproducible Fails since (at least) Build [20240812](https://openqa.opensuse.org/tests/4400312) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=opensu… -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231465] Kernel 6.11.2-1 only a fraction of ram is available
by bugzilla_noreply＠suse.com 15 Oct '24

15 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231465 https://bugzilla.suse.com/show_bug.cgi?id=1231465#c19 --- Comment #19 from Felix Niederwanger <felix.niederwanger(a)suse.com> --- Thank you Jiri. I'm booked today and tomorrow but will make some time on Thursday to do the testing and provide feedback. Perhaps I can smuggle it in-between but no promises. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231465] Kernel 6.11.2-1 only a fraction of ram is available
by bugzilla_noreply＠suse.com 15 Oct '24

15 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231465 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? | -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231465] Kernel 6.11.2-1 only a fraction of ram is available
by bugzilla_noreply＠suse.com 15 Oct '24

15 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231465 https://bugzilla.suse.com/show_bug.cgi?id=1231465#c18 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?, | |needinfo?(felix.niederwange | |r(a)suse.com) --- Comment #18 from Jiri Slaby <jslaby(a)suse.com> --- This kernel should behave slightly better (no sign extension and wraparound): https://build.opensuse.org/project/monitor/home:jirislaby:kernel-bsc1231465 And it dumps the sizes in efi_memattr_init(). Could you attach the dmesg output of the kernel? Perhaps this excerpt from logs after several runs of the kernel with cold/warm boots: journalctl -S 0:0 -t kernel -g memattr (hopefully you use persistent journal) -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

15 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 8

[Bug 1231465] Kernel 6.11.2-1 only a fraction of ram is available
by bugzilla_noreply＠suse.com 14 Oct '24

14 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231465 https://bugzilla.suse.com/show_bug.cgi?id=1231465#c16 --- Comment #16 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Vlastimil Babka from comment #13) > Thanks to Mike Rapoport for spotting the problematic line: > > [ 0.000000] [ T0] memblock_reserve: > [0x0000000077535018-0x00000000429ef027] efi_memattr_init+0x77/0xa0 > > That range's end < start, causing an underflow. > > These values probably come directly from some efi tables, so the firmware > might be buggy if it's broken on a reboot vs cold boot? Also, without the sign, the range would be: 0x77535018-0x1429ef018 which is weird in any case: > BIOS-e820: [mem 0x000000007b600000-0x000000007f7fffff] reserved > BIOS-e820: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved > BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved > BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved > BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved > BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved > BIOS-e820: [mem 0x0000000100000000-0x000000087e7fffff] usable -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231465] Kernel 6.11.2-1 only a fraction of ram is available
by bugzilla_noreply＠suse.com 14 Oct '24

14 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231465 https://bugzilla.suse.com/show_bug.cgi?id=1231465#c15 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(felix.niederwange | |r(a)suse.com) --- Comment #15 from Jiri Slaby <jslaby(a)suse.com> --- pff, I believe the tbl_size (int) is simply so high (3252MB), so that it is negative and sign-extended to ulong: static int __initdata tbl_size; tbl_size = sizeof(*tbl) + tbl->num_entries * tbl->desc_size; memblock_reserve(efi_mem_attr_table, tbl_size); Having tbl_size = 0xcb4ba000 which is -884236272 bakes that: 0xcb4ba000 -> 0xffffffffcb4ba010 and then the resulting range: 0x77535018-0x429ef027 So does this help: --- a/drivers/firmware/efi/memattr.c +++ b/drivers/firmware/efi/memattr.c @@ -12,7 +12,7 @@ #include <asm/early_ioremap.h> -static int __initdata tbl_size; +static phys_addr_t __initdata tbl_size; unsigned long __ro_after_init efi_mem_attr_table = EFI_INVALID_TABLE_ADDR; /* ? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231465] Kernel 6.11.2-1 causes OOM errors with Plasma 6.2
by bugzilla_noreply＠suse.com 14 Oct '24

14 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231465 https://bugzilla.suse.com/show_bug.cgi?id=1231465#c13 --- Comment #13 from Vlastimil Babka <vbabka(a)suse.com> --- Thanks to Mike Rapoport for spotting the problematic line: [ 0.000000] [ T0] memblock_reserve: [0x0000000077535018-0x00000000429ef027] efi_memattr_init+0x77/0xa0 That range's end < start, causing an underflow. These values probably come directly from some efi tables, so the firmware might be buggy if it's broken on a reboot vs cold boot? Are there bios updates available? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231416] ZSWAP config cleanup
by bugzilla_noreply＠suse.com 14 Oct '24

14 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231416 https://bugzilla.suse.com/show_bug.cgi?id=1231416#c5 --- Comment #5 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1231416) was mentioned in https://build.opensuse.org/request/show/1207767 Factory / kernel-source -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1230414] New: kernel: reproducible builds issue with BTF
by bugzilla_noreply＠suse.com 14 Oct '24

14 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230414 Bug ID: 1230414 Summary: kernel: reproducible builds issue with BTF 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: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- While working on reproducible builds for openSUSE, I found that our kernel-default , kernel-vanilla and kernel-debug packages vary in the "BTF" (BPF Type Format) ELF section. With my reproducibleopensuse tools (devel branch) I do osc co openSUSE:Factory/kernel-source && cd $_ spec=kernel-default.spec debuginfo=--debuginfo rbk To get https://rb.zq1.de/compare.factory-20240904/diffs/kernel-default-compare.out -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1231247] PPC64LE: bcc test fails when executing btrfsdist
by bugzilla_noreply＠suse.com 14 Oct '24

14 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231247 https://bugzilla.suse.com/show_bug.cgi?id=1231247#c14 --- Comment #14 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Aaron Puchert from comment #10) > (In reply to Jiri Slaby from comment #7) > > WIW it doesn't make sense (read as: is invalid/undefined) to build modules > > with a different compiler. > > From my understanding bcc doesn't build native kernel modules but just BPF > code. FTR, the compiled code is: https://github.com/iovisor/bcc/blob/cb1ba20f4800f556dc940682ba7016c50bd0a3a… It seems to call lib.bpf_module_create_c_from_string with that text: https://github.com/iovisor/bcc/blob/cb1ba20f4800f556dc940682ba7016c50bd0a3a… and then somehow processes it there: https://github.com/iovisor/bcc/blob/cb1ba20f4800f556dc940682ba7016c50bd0a3a… -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231578] Dell Latitude laptop kernel panic during wake up after suspend to disk since kernel-default updates
by bugzilla_noreply＠suse.com 12 Oct '24

12 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231578 https://bugzilla.suse.com/show_bug.cgi?id=1231578#c15 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |cfamullaconrad(a)suse.com --- Comment #15 from Takashi Iwai <tiwai(a)suse.com> --- Good to hear! You can keep this test kernel until the proper fix landed in SLE15-SP5 branch. So it's indeed a regression introduced by the recent backport of PM fixes (for bsc#1221269 CVE-2023-52498). The tested kernel was the revert of patches.suse/PM-sleep-Fix-possible-deadlocks-in-core-system-wide-PM-code.patch patches.suse/async-Introduce-async_schedule_dev_nocall.patch patches.suse/async-Split-async_schedule_node_domain.patch Clemens, it's yours, please take a look. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231578] New: Dell Latitude laptop kernel panic during wake up after suspend to disk since kernel-default updates
by bugzilla_noreply＠suse.com 12 Oct '24

12 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231578 Bug ID: 1231578 Summary: Dell Latitude laptop kernel panic during wake up after suspend to disk since kernel-default updates Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: opensuse.lietuviu.kalba(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 877933 --> https://bugzilla.suse.com/attachment.cgi?id=877933&action=edit grep "kernel-default" /var/log/zypp/history I used openSUSE Leap 15.5 in Dell Latitude laptop having: - 4 × Intel® Core™ i5-4300M CPU @ 2.60GHz - Mesa Intel® HD Graphics 4600 I used it with 5.14.21-150500.55.73.1 from 2024-08-16 till 2024-10-01 without suspend to disk problems. But since update to kernel-default|5.14.21-150500.55.80.2 on 2024-10-01, computer hang during wake-up from suspend to disk. Symptoms: - black screen, - keyboard and mouse does not respond, - no disk activity, - after several seconds CAPS Lock starts blinking; - SySRq keys (REISUB) does not work. If I press Ctrl+Alt+F2 (to switch from graphical session to TTY) right after pressing button in KDE desktop to suspend to disk, computer during wake-up shows this TTY, but also have same symptoms: no cursor is blinking, keyboard does not respond, after several seconds CAPS Lock starts blinking... P.S. In past (with older openSUSE 15.4) I had similar problems, but only if I wake-up computer disconnected from power (i.e. using battery only) and it just hanged at moment of entering into graphical session (if I wake up in TTY - it not hanged, by hanged immediately at pressing Ctrl+Alt+F7). Thus in past it seemed related to graphical card drivers, but not now. -- You are receiving this mail because: You are the assignee for the bug.

1 14

[Bug 1231578] Dell Latitude laptop kernel panic during wake up after suspend to disk since kernel-default updates
by bugzilla_noreply＠suse.com 12 Oct '24

12 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231578 https://bugzilla.suse.com/show_bug.cgi?id=1231578#c8 --- Comment #8 from Takashi Iwai <tiwai(a)suse.com> --- Thanks for quick testing! So the likely cause seems to be either in the PM core change or in the storage change. To be sure, could you try the latest kernel in OBS Kernel:SLE15-SP5 repo and verify that the problem still persists? http://download.opensuse.org/repositories/Kernel:/SLE15-SP5/pool/ Meanwhile, I'm building a test kernel with a few revers of the PM core change from SLE15-SP5 branch. It's being built in OBS home:tiwai:bsc1231578 repo. Once after the build finishes (takes an hour or so), it'll appear at http://download.opensuse.org/repositories/home:/tiwai:/bsc1231578/pool/ Please give it a try, too. BTW, when you install many kernels, old ones are purged automatically. You can edit /etc/zypp/zypp.conf and increase the number of installable kernels there, e.g. set the line to: multiversion.kernels = latest,latest-1,latest-2,latest-3,running -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231578] Dell Latitude laptop kernel panic during wake up after suspend to disk since kernel-default updates
by bugzilla_noreply＠suse.com 12 Oct '24

12 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231578 https://bugzilla.suse.com/show_bug.cgi?id=1231578#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(opensuse.lietuviu | |.kalba(a)gmail.com) CC| |opensuse.lietuviu.kalba@gma | |il.com, tiwai(a)suse.com --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- Please check that the problem doesn't appear when you boot the previous kernel (*.73.1), i.e. verify it being a regression of *.80.2 kernel. Then look through the old kernel logs and check whether you get any relevant kernel crash messages. If not found, try to set up kdump and catch the crash messages. Last but not least, please give the hwinfo and the dmesg output from both working and non-working kernels. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1228887] New: [ERR]fw PC = 0x20119f92 memory issues?
by bugzilla_noreply＠suse.com 12 Oct '24

12 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1228887 Bug ID: 1228887 Summary: [ERR]fw PC = 0x20119f92 memory issues? 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: jshand2013(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- [ 1450.828761] [ T829] rtw89_8852ce 0000:02:00.0: FW status = 0xd9001100 [ 1450.828837] [ T829] rtw89_8852ce 0000:02:00.0: FW BADADDR = 0x0 [ 1450.828842] [ T829] rtw89_8852ce 0000:02:00.0: FW EPC/RA = 0x0 [ 1450.828845] [ T829] rtw89_8852ce 0000:02:00.0: FW MISC = 0x20118fd0 [ 1450.828849] [ T829] rtw89_8852ce 0000:02:00.0: R_AX_HALT_C2H = 0x1000 [ 1450.828852] [ T829] rtw89_8852ce 0000:02:00.0: R_AX_SER_DBG_INFO = 0xf1000002 [ 1450.828859] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x20119f92 [ 1450.828944] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x20119f96 [ 1450.829019] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x20119f98 [ 1450.829035] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2011a01c [ 1450.829114] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x20119f78 [ 1450.829192] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x20119f92 [ 1450.829270] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x20119f96 [ 1450.829348] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x20119f9e [ 1450.829426] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2011a028 [ 1450.829504] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x20119f9e [ 1450.829582] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2011a04e [ 1450.829660] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x20119f94 [ 1450.829738] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2011a03e [ 1450.829816] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x20119f92 [ 1450.829894] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x20119f9c [ 1450.829906] [ T829] rtw89_8852ce 0000:02:00.0: ---> err=0x1000 [ 1450.829910] [ T829] rtw89_8852ce 0000:02:00.0: R_AX_SER_DBG_INFO =0xf1000002 [ 1450.829913] [ T829] rtw89_8852ce 0000:02:00.0: R_AX_SER_DBG_INFO =0xf1000002 [ 1450.829916] [ T829] rtw89_8852ce 0000:02:00.0: DBG Counter 1 (R_AX_DRV_FW_HSK_4)=0x00070007 [ 1450.829920] [ T829] rtw89_8852ce 0000:02:00.0: DBG Counter 2 (R_AX_DRV_FW_HSK_5)=0x00a300a3 [ 1450.829924] [ T829] rtw89_8852ce 0000:02:00.0: R_AX_DMAC_ERR_ISR=0x00000002 [ 1450.829927] [ T829] rtw89_8852ce 0000:02:00.0: R_AX_DMAC_ERR_IMR=0x00000000 [ 1450.830028] [ T829] rtw89_8852ce 0000:02:00.0: R_AX_WDE_ERR_FLAG_CFG=0x00000000 [ 1450.830031] [ T829] rtw89_8852ce 0000:02:00.0: R_AX_PLE_ERR_FLAG_CFG=0x00000000 [ 1450.830034] [ T829] rtw89_8852ce 0000:02:00.0: R_AX_PLE_ERRFLAG_MSG=0x00000000 [ 1450.830036] [ T829] rtw89_8852ce 0000:02:00.0: R_AX_WDE_ERRFLAG_MSG=0x00000000 [ 1450.830039] [ T829] rtw89_8852ce 0000:02:00.0: R_AX_PLE_DBGERR_LOCKEN=0x00000000 [ 1450.830041] [ T829] rtw89_8852ce 0000:02:00.0: R_AX_PLE_DBGERR_STS=0x00000000 [ 1450.830044] [ T829] rtw89_8852ce 0000:02:00.0: R_AX_SEC_ERR_IMR=0x00000003 [ 1450.830046] [ T829] rtw89_8852ce 0000:02:00.0: R_AX_SEC_ERR_ISR=0x00000001 [ 1450.830049] [ T829] rtw89_8852ce 0000:02:00.0: R_AX_SEC_ENG_CTRL=0x80001f3f [ 1450.830052] [ T829] rtw89_8852ce 0000:02:00.0: R_AX_SEC_MPDU_PROC=0x00000003 [ 1450.830054] [ T829] rtw89_8852ce 0000:02:00.0: R_AX_SEC_CAM_ACCESS=0x00000000 [ 1450.830057] [ T829] rtw89_8852ce 0000:02:00.0: R_AX_SEC_CAM_RDATA=0x00000000 [ 1450.830059] [ T829] rtw89_8852ce 0000:02:00.0: R_AX_SEC_DEBUG1=0x045644d0 [ 1450.830062] [ T829] rtw89_8852ce 0000:02:00.0: R_AX_SEC_TX_DEBUG=0x00808000 [ 1450.830065] [ T829] rtw89_8852ce 0000:02:00.0: R_AX_SEC_RX_DEBUG=0x02023002 [ 1450.830077] [ T829] rtw89_8852ce 0000:02:00.0: sel=0,R_AX_SEC_DEBUG2=0x02000006 [ 1450.830082] [ T829] rtw89_8852ce 0000:02:00.0: sel=1,R_AX_SEC_DEBUG2=0x040045c0 [ 1450.830087] [ T829] rtw89_8852ce 0000:02:00.0: sel=2,R_AX_SEC_DEBUG2=0x00000000 [ 1450.830091] [ T829] rtw89_8852ce 0000:02:00.0: sel=3,R_AX_SEC_DEBUG2=0x00000000 [ 1450.830096] [ T829] rtw89_8852ce 0000:02:00.0: sel=4,R_AX_SEC_DEBUG2=0x0040400f [ 1450.830100] [ T829] rtw89_8852ce 0000:02:00.0: sel=5,R_AX_SEC_DEBUG2=0x00081000 [ 1450.830105] [ T829] rtw89_8852ce 0000:02:00.0: sel=6,R_AX_SEC_DEBUG2=0x21300f40 [ 1450.830109] [ T829] rtw89_8852ce 0000:02:00.0: sel=7,R_AX_SEC_DEBUG2=0x45600000 [ 1450.830114] [ T829] rtw89_8852ce 0000:02:00.0: sel=8,R_AX_SEC_DEBUG2=0x01010040 [ 1450.830118] [ T829] rtw89_8852ce 0000:02:00.0: sel=9,R_AX_SEC_DEBUG2=0x00c00201 [ 1450.830123] [ T829] rtw89_8852ce 0000:02:00.0: sel=a,R_AX_SEC_DEBUG2=0x00000000 [ 1450.830127] [ T829] rtw89_8852ce 0000:02:00.0: sel=b,R_AX_SEC_DEBUG2=0x00000308 [ 1450.830132] [ T829] rtw89_8852ce 0000:02:00.0: sel=c,R_AX_SEC_DEBUG2=0x00000000 [ 1450.830136] [ T829] rtw89_8852ce 0000:02:00.0: sel=d,R_AX_SEC_DEBUG2=0x00000000 [ 1450.830140] [ T829] rtw89_8852ce 0000:02:00.0: sel=e,R_AX_SEC_DEBUG2=0x00000000 [ 1450.830145] [ T829] rtw89_8852ce 0000:02:00.0: sel=f,R_AX_SEC_DEBUG2=0x00000000 [ 1450.830151] [ T829] rtw89_8852ce 0000:02:00.0: R_AX_CMAC_ERR_ISR [0]=0x00000000 [ 1450.830154] [ T829] rtw89_8852ce 0000:02:00.0: R_AX_CMAC_FUNC_EN [0]=0xf000803f [ 1450.830157] [ T829] rtw89_8852ce 0000:02:00.0: R_AX_CK_EN [0]=0xffffffff [ 1450.830160] [ T829] rtw89_8852ce 0000:02:00.0: R_AX_CMAC_ERR_IMR [0]=0x00000000 [ 1450.830163] [ T829] rtw89_8852ce 0000:02:00.0: [CMAC] : CMAC1 not enabled [ 1450.830166] [ T829] rtw89_8852ce 0000:02:00.0: R_AX_DBG_ERR_FLAG=0x00000000 [ 1450.830169] [ T829] rtw89_8852ce 0000:02:00.0: R_AX_LBC_WATCHDOG=0x0030d800 [ 1450.830170] [ T829] rtw89_8852ce 0000:02:00.0: <--- [ 1450.830171] [ T829] rtw89_8852ce 0000:02:00.0: SER catches error: 0x1000 [ 1450.830490] [ T829] rtw89_8852ce 0000:02:00.0: FW status = 0xd9001100 [ 1450.830497] [ T829] rtw89_8852ce 0000:02:00.0: FW BADADDR = 0x0 [ 1450.830501] [ T829] rtw89_8852ce 0000:02:00.0: FW EPC/RA = 0x0 [ 1450.830504] [ T829] rtw89_8852ce 0000:02:00.0: FW MISC = 0x20118fd0 [ 1450.830507] [ T829] rtw89_8852ce 0000:02:00.0: R_AX_HALT_C2H = 0x1001 [ 1450.830510] [ T829] rtw89_8852ce 0000:02:00.0: R_AX_SER_DBG_INFO = 0xf1000002 [ 1450.830517] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2011a034 [ 1450.830544] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x20119fd4 [ 1450.830622] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2011a110 [ 1450.830699] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2011a02e [ 1450.830777] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2011a026 [ 1450.830855] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2011a032 [ 1450.830933] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2011a03a [ 1450.831011] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x20119f9e [ 1450.831089] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2011a01e [ 1450.831167] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x20119f6e [ 1450.831245] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2011a02c [ 1450.831323] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x20119f6e [ 1450.831401] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x20119f70 [ 1450.831479] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2011a07e [ 1450.831557] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2011a02e [ 1450.831569] [ T829] rtw89_8852ce 0000:02:00.0: SER catches error: 0x1001 [ 1450.831858] [ T829] rtw89_8852ce 0000:02:00.0: FW status = 0xd9008100 [ 1450.831863] [ T829] rtw89_8852ce 0000:02:00.0: FW BADADDR = 0x0 [ 1450.831866] [ T829] rtw89_8852ce 0000:02:00.0: FW EPC/RA = 0x0 [ 1450.831869] [ T829] rtw89_8852ce 0000:02:00.0: FW MISC = 0x20117bd4 [ 1450.831872] [ T829] rtw89_8852ce 0000:02:00.0: R_AX_HALT_C2H = 0x1002 [ 1450.831875] [ T829] rtw89_8852ce 0000:02:00.0: R_AX_SER_DBG_INFO = 0xf1000002 [ 1450.831881] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2013f146 [ 1450.831900] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2013aefe [ 1450.831919] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2013ae42 [ 1450.831938] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2013ae76 [ 1450.831957] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2013b30a [ 1450.831976] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2003c97c [ 1450.831995] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2013f11c [ 1450.832014] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2003b98e [ 1450.832032] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2003c934 [ 1450.832052] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2013af42 [ 1450.832071] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2013a10e [ 1450.832090] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2003c5f4 [ 1450.832109] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2003c99e [ 1450.832128] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2003c98e [ 1450.832147] [ T829] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2002d972 [ 1450.832158] [ T829] rtw89_8852ce 0000:02:00.0: SER catches error: 0x1002 [ 1450.859411] [ T891] rtw89_8852ce 0000:02:00.0: c2h class 1 func 3 not support -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1230889] New: nvme nvme0: I/O tag 864 (e360) opcode 0x1 (I/O Cmd) QID 3 timeout, aborting req_op:WRITE(1) size:524288
by bugzilla_noreply＠suse.com 12 Oct '24

12 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230889 Bug ID: 1230889 Summary: nvme nvme0: I/O tag 864 (e360) opcode 0x1 (I/O Cmd) QID 3 timeout, aborting req_op:WRITE(1) size:524288 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: jshand2013(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- [ 870.274430] [ T281] nvme nvme0: I/O tag 864 (e360) opcode 0x1 (I/O Cmd) QID 3 timeout, aborting req_op:WRITE(1) size:524288 [ 870.274497] [ T281] nvme nvme0: I/O tag 865 (d361) opcode 0x1 (I/O Cmd) QID 3 timeout, aborting req_op:WRITE(1) size:524288 [ 870.274524] [ T281] nvme nvme0: I/O tag 866 (d362) opcode 0x1 (I/O Cmd) QID 3 timeout, aborting req_op:WRITE(1) size:524288 [ 870.274544] [ T281] nvme nvme0: I/O tag 867 (c363) opcode 0x1 (I/O Cmd) QID 3 timeout, aborting req_op:WRITE(1) size:524288 [ 870.274562] [ T281] nvme nvme0: I/O tag 868 (c364) opcode 0x1 (I/O Cmd) QID 3 timeout, aborting req_op:WRITE(1) size:524288 [ 870.274580] [ T281] nvme nvme0: I/O tag 869 (c365) opcode 0x1 (I/O Cmd) QID 3 timeout, aborting req_op:WRITE(1) size:524288 [ 870.274598] [ T281] nvme nvme0: I/O tag 870 (c366) opcode 0x1 (I/O Cmd) QID 3 timeout, aborting req_op:WRITE(1) size:36864 [ 870.274615] [ T281] nvme nvme0: I/O tag 871 (c367) opcode 0x1 (I/O Cmd) QID 3 timeout, aborting req_op:WRITE(1) size:524288 [ 871.319296] [ C2] nvme nvme0: Abort status: 0x0 [ 872.311601] [ C2] nvme nvme0: Abort status: 0x0 [ 873.088770] [ C2] nvme nvme0: Abort status: 0x0 [ 873.792506] [ C2] nvme nvme0: Abort status: 0x0 [ 874.358983] [ C2] nvme nvme0: Abort status: 0x0 [ 874.360148] [ C2] nvme nvme0: Abort status: 0x0 [ 874.360729] [ C2] nvme nvme0: Abort status: 0x0 [ 874.366612] [ C2] nvme nvme0: Abort status: 0x0 -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1231341] missing vbox module for current kernel-default
by bugzilla_noreply＠suse.com 11 Oct '24

11 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231341 https://bugzilla.suse.com/show_bug.cgi?id=1231341#c5 --- Comment #5 from Daniel Pecka <nettezzaumanaa(a)gmail.com> --- Hi, couple of new kernels are available but we're still missing a virtualbox-kmp-default # zypper -vv se -sx -r kernel -r kernel-kmp virtualbox-kmp-default kernel-default Verbosity: 3 Non-option program arguments: 'virtualbox-kmp-default' 'kernel-default' Initializing Target Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository ---+------------------------+------------+--------------------------------------------+--------+----------- vl | kernel-default | package | 6.11.3-lp155.2.1.g006a2b4 | x86_64 | kernel | kernel-default | srcpackage | 6.11.3-lp155.2.1.g006a2b4 | noarch | kernel | kernel-default | srcpackage | 6.11.2-lp155.5.1.g4ec2eee | noarch | kernel vl | virtualbox-kmp-default | package | 7.0.20_k6.11.0_lp155.5.gb87e886-lp155.2.21 | x86_64 | kernel-kmp can please somebody look into it .. this is unfortunately very serious issue .. thanks and regards, ~dan -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231465] Kernel 6.11.2-1 causes OOM errors with Plasma 6.2
by bugzilla_noreply＠suse.com 11 Oct '24

11 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231465 https://bugzilla.suse.com/show_bug.cgi?id=1231465#c9 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |felix.niederwanger(a)suse.com | |, jslaby(a)suse.com Flags| |needinfo?(felix.niederwange | |r(a)suse.com) --- Comment #9 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Vlastimil Babka from comment #8) > It should also help if both the working 6.11.0 and not working 6.11.2 was > booted with kernel parameter memblock=debug so we can check differences of > memblock allocations from the dmesg. Thanks! While doing that, please add also: kprobe_event='p,__ioremap_caller,$arg1,$arg2,$arg4:symbol' kernel parameter. And attach the output of cat /sys/kernel/tracing/trace -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231465] Kernel 6.11.2-1 causes OOM errors with Plasma 6.2
by bugzilla_noreply＠suse.com 11 Oct '24

11 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231465 https://bugzilla.suse.com/show_bug.cgi?id=1231465#c8 --- Comment #8 from Vlastimil Babka <vbabka(a)suse.com> --- It should also help if both the working 6.11.0 and not working 6.11.2 was booted with kernel parameter memblock=debug so we can check differences of memblock allocations from the dmesg. Thanks! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231247] PPC64LE: bcc test fails when executing btrfsdist
by bugzilla_noreply＠suse.com 11 Oct '24

11 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231247 https://bugzilla.suse.com/show_bug.cgi?id=1231247#c9 --- Comment #9 from Michal Suchanek <msuchanek(a)suse.com> --- Indeed, then it should use the system compiler for that. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231247] PPC64LE: bcc test fails when executing btrfsdist
by bugzilla_noreply＠suse.com 11 Oct '24

11 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231247 https://bugzilla.suse.com/show_bug.cgi?id=1231247#c8 --- Comment #8 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Michal Suchanek from comment #6) > It's a bug in the ifdef. > > Instead of checking CC_IS_CLANG which is kernel-specific and not defined > when the header is used by userspace it should check some define that is > provided by clang compiler itself. Nope, it's a kernel btf module being built. The header is not uapi, hence not exported. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231247] PPC64LE: bcc test fails when executing btrfsdist
by bugzilla_noreply＠suse.com 11 Oct '24

11 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231247 https://bugzilla.suse.com/show_bug.cgi?id=1231247#c7 --- Comment #7 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Shung-Hsi Yu from comment #5) > The compilation error is coming from Clang/LLVM, maybe @Aaron has some clues > regarding Clang's support of machine constrain targeting ppc64le? Ah then clearly Z<> should have been used: +#ifdef CONFIG_CC_IS_CLANG +#define DS_FORM_CONSTRAINT "Z<>" +#else +#define DS_FORM_CONSTRAINT "YZ<>" +#endif WIW it doesn't make sense (read as: is invalid/undefined) to build modules with a different compiler. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231247] PPC64LE: bcc test fails when executing btrfsdist
by bugzilla_noreply＠suse.com 11 Oct '24

11 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231247 https://bugzilla.suse.com/show_bug.cgi?id=1231247#c6 Michal Suchanek <msuchanek(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(msuchanek(a)suse.co | |m), | |needinfo?(duwe(a)suse.com) | --- Comment #6 from Michal Suchanek <msuchanek(a)suse.com> --- It's a bug in the ifdef. Instead of checking CC_IS_CLANG which is kernel-specific and not defined when the header is used by userspace it should check some define that is provided by clang compiler itself. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231470] After ugrading to kernel-default-6.11.2-1 system doesn't boot and caps lock key is blinking
by bugzilla_noreply＠suse.com 11 Oct '24

11 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231470 https://bugzilla.suse.com/show_bug.cgi?id=1231470#c3 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(wolfgang.engel@su | |se.com) CC| |jslaby(a)suse.com, | |wolfgang.engel(a)suse.com --- Comment #3 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Wolfgang Engel from comment #0) > Please let me know if you need further information. dmesg, kdump crash report, or at least a picture of the screen with "quiet" kernel option disabled and/or earlycon enabled. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231247] PPC64LE: bcc test fails when executing btrfsdist
by bugzilla_noreply＠suse.com 11 Oct '24

11 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231247 https://bugzilla.suse.com/show_bug.cgi?id=1231247#c5 Shung-Hsi Yu <shung-hsi.yu(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aaronpuchert(a)alice-dsl.net --- Comment #5 from Shung-Hsi Yu <shung-hsi.yu(a)suse.com> --- The compilation error is coming from Clang/LLVM, maybe @Aaron has some clues regarding Clang's support of machine constrain targeting ppc64le? (On a side note I should probably bump the Clang/LLVM version up, but I'm not sure if it would helps with this case) -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

11 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230418 https://bugzilla.suse.com/show_bug.cgi?id=1230418#c14 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com --- Comment #14 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Guillaume Pinchon from comment #12) > UPDATE3: that's still not fixed, even with the latest stable kernel, > switching to Fedora this distro is unusable. Good luck then. Provided both fedora and opensuse follows the latest upstream, I wonder if it helped at all. -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

11 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231167 https://bugzilla.suse.com/show_bug.cgi?id=1231167#c7 --- Comment #7 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Ricardo Salveti from comment #0) > Created attachment 877673 [details] > kernel config diff pushed to master+stable. Leaving open for inst-images. -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

11 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231167 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com Attachment #877673|application/mbox |text/plain mime type| | -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231247] PPC64LE: bcc test fails when executing btrfsdist
by bugzilla_noreply＠suse.com 11 Oct '24

11 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231247 https://bugzilla.suse.com/show_bug.cgi?id=1231247#c4 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |duwe(a)suse.com, | |msuchanek(a)suse.com Flags| |needinfo?(msuchanek(a)suse.co | |m), | |needinfo?(duwe(a)suse.com) --- Comment #4 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Avinesh Kumar from comment #1) > $ /usr/share/bcc/tools/btrfsdist 5 2 > .. > .. > In file included from /virtual/main.c:3: > include/linux/fs.h:3661:15: error: invalid input constraint 'YZ<>' in asm > 3661 | if (unlikely(get_user(c, path))) > | ^ ... > arch/powerpc/include/asm/uaccess.h:98:28: note: expanded from macro > 'DS_FORM_CONSTRAINT' > 98 | #define DS_FORM_CONSTRAINT "YZ<>" Guys, any idea what could have changed in 6.10..6.11 in this respect? Is bcc missing some compiler flags when building against 6.11's includes? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231247] PPC64LE: bcc test fails when executing btrfsdist
by bugzilla_noreply＠suse.com 11 Oct '24

11 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231247 https://bugzilla.suse.com/show_bug.cgi?id=1231247#c3 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com --- Comment #3 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Avinesh Kumar from comment #2) > I see this recent commit, which looks very relevant to the compilation error > - > https://lore.kernel.org/netdev/172657576225.2195991.10894874767253579579.b4- > ty(a)ellerman.id.au/T/ > > and it is merged in 6.12-rc1 commit 39190ac7cff1fd15135fa8e658030d9646fdb5f2 Author: Michael Ellerman <mpe(a)ellerman.id.au> Date: Mon Sep 16 22:05:10 2024 +1000 powerpc/atomic: Use YZ constraints for DS-form instructions is contained in 6.11.2. The commit is intended to fix atomic_reads. So yes, the test still fails even with 6.11.2. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231470] After ugrading to kernel-default-6.11.2-1 system doesn't boot and caps lock key is blinking
by bugzilla_noreply＠suse.com 10 Oct '24

10 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231470 https://bugzilla.suse.com/show_bug.cgi?id=1231470#c2 Michael Hirmke <opensuse(a)mike.franken.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |opensuse(a)mike.franken.de --- Comment #2 from Michael Hirmke <opensuse(a)mike.franken.de> --- (In reply to Wolfgang Engel from comment #0) > After upgrading from kernel-default-6.11.0-1 to kernel-default-6.11.2-1 the > system doesn't boot and only shows blinking caps lock key, screen stays > black. > > This happens after grub is loading the kernel and initrd and kernel is > started. > > Hardware is Dell XPS13 laptop. > > System is starting with kernel-default-6.11.0-1 just fine. > > Please let me know if you need further information. I don't have this problem with and kernel 6.11.2-1 on my XPS 13 9310 2-in-1/0NVVG0, BIOS 2.25.0 04/24/2024. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231465] Kernel 6.11.2-1 causes OOM errors with Plasma 6.2
by bugzilla_noreply＠suse.com 10 Oct '24

10 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231465 https://bugzilla.suse.com/show_bug.cgi?id=1231465#c7 --- Comment #7 from Takashi Iwai <tiwai(a)suse.com> --- Thanks. The dmesg from 6.11 (just before the breakage) would be appreciated. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231465] Kernel 6.11.2-1 causes OOM errors with Plasma 6.2
by bugzilla_noreply＠suse.com 10 Oct '24

10 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231465 https://bugzilla.suse.com/show_bug.cgi?id=1231465#c5 --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- Thanks for quick testing! Then it's an invalid / incomplete backport of 6.11.x stable tree that broke, as it seems. I'm building 6.11.3 kernel in OBS home:tiwai:bsc1231465 repo (which should be the same content as Kernel:stable of tomorrow). Although I'm not sure whether it covers your case, please check it later. Meanwhile, please give the dmesg output of the working kernel (6.11.0) for comparison, too. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231465] Kernel 6.11.2-1 causes OOM errors with Plasma 6.2
by bugzilla_noreply＠suse.com 10 Oct '24

10 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231465 https://bugzilla.suse.com/show_bug.cgi?id=1231465#c4 --- Comment #4 from Felix Niederwanger <felix.niederwanger(a)suse.com> --- 6.11-rc2 works fine on my laptop. No signs of OOM-killer in action so far. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231465] Kernel 6.11.2-1 causes OOM errors with Plasma 6.2
by bugzilla_noreply＠suse.com 10 Oct '24

10 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231465 https://bugzilla.suse.com/show_bug.cgi?id=1231465#c3 --- Comment #3 from Felix Niederwanger <felix.niederwanger(a)suse.com> --- (In reply to Takashi Iwai from comment #2) > As a quick check, could you test 6.11-rc2 kernel from OBS Kernel:HEAD repo? > http://download.opensuse.org/repositories/Kernel:/HEAD/standard/ Sure thing, will have a look later today and report back. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231465] Kernel 6.11.2-1 causes OOM errors with Plasma 6.2
by bugzilla_noreply＠suse.com 10 Oct '24

10 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231465 https://bugzilla.suse.com/show_bug.cgi?id=1231465#c2 --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- Not trivial to figure out which change caused the problem, as there have been massive changes between 6.11 and 6.11.2, unfortunately. As a quick check, could you test 6.11-rc2 kernel from OBS Kernel:HEAD repo? http://download.opensuse.org/repositories/Kernel:/HEAD/standard/ -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231470] After ugrading to kernel-default-6.11.2-1 system doesn't boot and caps lock key is blinking
by bugzilla_noreply＠suse.com 10 Oct '24

10 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231470 https://bugzilla.suse.com/show_bug.cgi?id=1231470#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Probably a dup of bsc#1231465? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231470] New: After ugrading to kernel-default-6.11.2-1 system doesn't boot and caps lock key is blinking
by bugzilla_noreply＠suse.com 10 Oct '24

10 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231470 Bug ID: 1231470 Summary: After ugrading to kernel-default-6.11.2-1 system doesn't boot and caps lock key is blinking Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: wolfgang.engel(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After upgrading from kernel-default-6.11.0-1 to kernel-default-6.11.2-1 the system doesn't boot and only shows blinking caps lock key, screen stays black. This happens after grub is loading the kernel and initrd and kernel is started. Hardware is Dell XPS13 laptop. System is starting with kernel-default-6.11.0-1 just fine. Please let me know if you need further information. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231465] Kernel 6.11.2-1 causes OOM errors with Plasma 6.2
by bugzilla_noreply＠suse.com 10 Oct '24

10 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231465 https://bugzilla.suse.com/show_bug.cgi?id=1231465#c1 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvogt(a)suse.com, | |vbabka(a)suse.com --- Comment #1 from Fabian Vogt <fvogt(a)suse.com> --- [ 92.704262] [ T848] 8357393 pages RAM [ 92.704264] [ T848] 8016776 pages reserved That looks broken. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1227144] iwlwifi 0000:6f:00.0: Microcode SW error detected. Restarting 0x0.
by bugzilla_noreply＠suse.com 09 Oct '24

09 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1227144 https://bugzilla.suse.com/show_bug.cgi?id=1227144#c13 --- Comment #13 from Andreas <opendreas(a)gmail.com> --- I installed Leap 16 preAlpha in Virtualbox, the warnings remained, but there were no wifi errors as is the case with Windows. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1227144] iwlwifi 0000:6f:00.0: Microcode SW error detected. Restarting 0x0.
by bugzilla_noreply＠suse.com 09 Oct '24

09 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1227144 https://bugzilla.suse.com/show_bug.cgi?id=1227144#c12 --- Comment #12 from Andreas <opendreas(a)gmail.com> --- Created attachment 877848 --> https://bugzilla.suse.com/attachment.cgi?id=877848&action=edit dmesg-6.4.0-150600.23.25 (In reply to Takashi Iwai from comment #11) > Care to check the latest Leap 15.6 kernel in OBS Kernel:SLE15-SP6 repo, too? > http://download.opensuse.org/repositories/Kernel:/SLE15-SP6/pool/ With the latest kernel, I had errors in two scenarios: 1. Using VirtualBox 2. After a standby, when trying to intensively download something, for example, large updates or Youtube. Errors with Virtualbox remained with the new kernel, dmesg log after starting Windows in Virtualbox. I'll be testing more; but there are no errors in the quick test yet. But it is impossible to work with Virtualbox. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231416] New: ZSWAP config cleanup
by bugzilla_noreply＠suse.com 09 Oct '24

09 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231416 Bug ID: 1231416 Summary: ZSWAP config cleanup 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: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Following: commit 13a488ad6c85976074f78f80a06414914890703c Author: Yosry Ahmed <yosryahmed(a)google.com> Date: Mon Oct 7 19:21:16 2024 +0000 mm: z3fold: deprecate CONFIG_Z3FOLD The z3fold compressed pages allocator is rarely used, most users use zsmalloc. The only disadvantage of zsmalloc in comparison is the dependency on MMU, and zbud is a more common option for !MMU as it was the default zswap allocator for a long time. Historically, zsmalloc had worse latency than zbud and z3fold but offered better memory savings. This is no longer the case as shown by a simple recent analysis [1]. That analysis showed that z3fold does not have any advantage over zsmalloc or zbud considering both performance and memory usage. In a kernel build test on tmpfs in a limited cgroup, z3fold took 3% more time and used 1.8% more memory. The latency of zswap_load() was 7% higher, and that of zswap_store() was 10% higher. Zsmalloc is better in all metrics. Moreover, z3fold apparently has latent bugs, which was made noticeable by a recent soft lockup bug report with z3fold [2]. Switching to zsmalloc not only fixed the problem, but also reduced the swap usage from 6~8G to 1~2G. Other users have also reported being bitten by mistakenly enabling z3fold. Other than hurting users, z3fold is repeatedly causing wasted engineering effort. Apart from investigating the above bug, it came up in multiple development discussions (e.g. [3]) as something we need to handle, when there aren't any legit users (at least not intentionally). The natural course of action is to deprecate z3fold, and remove in a few cycles if no objections are raised from active users. Next on the list should be zbud, as it offers marginal latency gains at the cost of huge memory waste when compared to zsmalloc. That one will need to wait until zsmalloc does not depend on MMU. We should likely: * set CONFIG_ZSWAP_ZPOOL_DEFAULT_Z3FOLD_DEPRECATED=n * set CONFIG_ZSWAP_ZPOOL_DEFAULT_ZSMALLOC=y and CONFIG_ZSWAP_ZPOOL_DEFAULT_ZBUD=n -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1230414] kernel: reproducible builds issue with BTF
by bugzilla_noreply＠suse.com 08 Oct '24

08 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230414 https://bugzilla.suse.com/show_bug.cgi?id=1230414#c13 --- Comment #13 from Michal Suchanek <msuchanek(a)suse.com> --- The issue exists downto SLE15-SP5 where the commit introducing the non-deterministic BTF generation was backported, it's not part of the base kernel. Prerequisites: c1177979af9c616661a126a80dd486ad0543b836 v6.3-rc1 btf, scripts: Exclude Rust CUs with pahole noop on 5.14, no Rust support 7b99f75942da332e3f4f865e55a10fec95a30d4f v6.5-rc1 bpf: Add --skip_encoding_btf_inconsistent_proto, Fix preventing attachment of functions specialized by the compiler 72d091846de935e0942a8a0f1fe24ff739d85d76 v6.7-rc1 kbuild: avoid too many execution of scripts/pahole-flags.sh Rewrite of how pahole flags are passed around in make fcd1ed89a0439c45e1336bd9649485c44b7597c7 v6.10-rc1 kbuild,bpf: Switch to using --btf_features for pahole v1.26 Another flag passing change, and only for pahole 1.26, we only use 1.25 34021caef79f76e70ac31247d321ecd0683c4939 v6.11-rc1 kbuild, bpf: Use test-ge check for v1.25-only pahole And another one ebb79e96f1ea454fbcc8fe27dfe44e751bd74b4b v6.11-rc1 kbuild: bpf: Tell pahole to DECL_TAG kfuncs Looking at the history this has no prerequisites. bpftool might make use of the data, the kernel does not have support for it and should ignore it. Also requires pahole 1.27 46fb0b62ea29c0dbcb3e44f1d67aafe79bc6e045 v6.11-rc1 kbuild,bpf: Add module-specific pahole flags for distilled Adds new section that might be used by current bpftool, should not affect kernel. Also our pahole does not support it. With the prerequisites applied whatever fix is finally merged upstream should apply cleanly to our kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1230414] kernel: reproducible builds issue with BTF
by bugzilla_noreply＠suse.com 08 Oct '24

08 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230414 https://bugzilla.suse.com/show_bug.cgi?id=1230414#c12 --- Comment #12 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Takashi Iwai from comment #11) > I guess the -j1 hack is acceptable as a temporary solution for us, while we > should ping upstream devs for the more proper fix. I pushed the temporary fix with -j1 option to users/tiwai/master/for-next and */stable/for-next branches now. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231050] What does this error mean: xs_tcp_setup_socket...unhandled error -107
by bugzilla_noreply＠suse.com 08 Oct '24

08 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231050 https://bugzilla.suse.com/show_bug.cgi?id=1231050#c6 Neil Brown <nfbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #6 from Neil Brown <nfbrown(a)suse.com> --- I think this is simply an omission from the switch statement in xs_tcp_setup_socket(). -ENOTCONN should be handled the same way as -ECONNREFUSED set. If it was, the error would be passed to xprt_wake_pending_tasks which end up calling call_connect_status() which does handle -ENOTCONN. I'll look thorough the code again when I get a bit more time and ensure that makes sense - then will suggest a patch upstream. Thanks for the report. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1227144] iwlwifi 0000:6f:00.0: Microcode SW error detected. Restarting 0x0.
by bugzilla_noreply＠suse.com 08 Oct '24

08 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1227144 https://bugzilla.suse.com/show_bug.cgi?id=1227144#c11 --- Comment #11 from Takashi Iwai <tiwai(a)suse.com> --- Care to check the latest Leap 15.6 kernel in OBS Kernel:SLE15-SP6 repo, too? http://download.opensuse.org/repositories/Kernel:/SLE15-SP6/pool/ -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231341] missing vbox module for current kernel-default
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231341 https://bugzilla.suse.com/show_bug.cgi?id=1231341#c4 --- Comment #4 from Stephan Hemeier <Sauerlandlinux(a)gmx.de> --- You are right, my fault. There is an unsolvable: https://build.opensuse.org/package/show/Kernel:stable:Backport:KMP/virtualb… So the Repo might be out of sync. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231341] missing vbox module for current kernel-default
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231341 https://bugzilla.suse.com/show_bug.cgi?id=1231341#c3 --- Comment #3 from Daniel Pecka <nettezzaumanaa(a)gmail.com> --- Hi Stefan .. https://download.opensuse.org/repositories/Kernel:/stable:/KMP/standard/x86… is for TW and not leap o.O ... Kernel:/stable:/Backport/standard/ + Kernel:/stable:/Backport:/KMP/standard/ are meant for leap ... regards, ~dan -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231341] missing vbox module for current kernel-default
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231341 https://bugzilla.suse.com/show_bug.cgi?id=1231341#c2 --- Comment #2 from Stephan Hemeier <Sauerlandlinux(a)gmx.de> --- And enable the refresh for the Repos....... -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231341] missing vbox module for current kernel-default
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231341 https://bugzilla.suse.com/show_bug.cgi?id=1231341#c1 Stephan Hemeier <Sauerlandlinux(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Sauerlandlinux(a)gmx.de --- Comment #1 from Stephan Hemeier <Sauerlandlinux(a)gmx.de> --- Virtualbox is on Version 7.1: https://download.opensuse.org/repositories/Kernel:/stable:/KMP/standard/x86… So update your System. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231341] New: missing vbox module for current kernel-default
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231341 Bug ID: 1231341 Summary: missing vbox module for current kernel-default Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: nettezzaumanaa(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 877766 --> https://bugzilla.suse.com/attachment.cgi?id=877766&action=edit more details from command-line Hello, there is missing a virtualbox-kmp-default package for current kernel from https://download.opensuse.org/repositories/Kernel:/stable:/Backport/standar… building the module fails also .. Please see attached file .. Currently available kernel + vboxdrv package is this # zypper -vv se -sx -t package -r kernel -r kernel-kmp kernel-default virtualbox-kmp-default Verbosity: 3 Non-option program arguments: 'kernel-default' 'virtualbox-kmp-default' Initializing Target Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository ---+------------------------+---------+--------------------------------------------+--------+----------- i+ | kernel-default | package | 6.11.2-lp155.2.1.g38c846e | x86_64 | kernel i+ | virtualbox-kmp-default | package | 7.0.20_k6.11.0_lp155.5.gb87e886-lp155.2.21 | x86_64 | kernel-kmp virtualbox-kmp-default doesn't fit to current kernel .. Please see more in attached file where are mode details .. thanks and regards, ~dan -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231050] What does this error mean: xs_tcp_setup_socket...unhandled error -107
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231050 https://bugzilla.suse.com/show_bug.cgi?id=1231050#c5 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nfbrown(a)suse.com Flags| |needinfo?(nfbrown(a)suse.com) --- Comment #5 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to James Moe from comment #0) > 2024-09-27T11:03:03-07:00 sma-station14l kernel: xs_tcp_setup_socket: > connect returned unhandled error -107 ENOTCONN is really unhandled in xs_tcp_setup_socket() [1]. And obviously, xs_tcp_finish_connecting() can return it [2]. Neil any ideas? [1] https://github.com/torvalds/linux/blob/98f7e32f20d28/net/sunrpc/xprtsock.c#… [2] https://github.com/torvalds/linux/blob/98f7e32f20d28/net/sunrpc/xprtsock.c#… Seems to be added in 2009 by: https://github.com/torvalds/linux/commit/01d37c428ae080563c0a3bb8bdfa88c65a… i.e. commit 01d37c428ae080563c0a3bb8bdfa88c65a6891d3 Author: Trond Myklebust <Trond.Myklebust(a)netapp.com> Date: Wed Mar 11 14:09:39 2009 -0400 SUNRPC: xprt_connect() don't abort the task if the transport isn't bound -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231235] New: Please backport 6.12 snapdragon lenovo t14s gen6 drivers to 6.11 kernel
by bugzilla_noreply＠suse.com 05 Oct '24

05 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231235 Bug ID: 1231235 Summary: Please backport 6.12 snapdragon lenovo t14s gen6 drivers to 6.11 kernel Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: rosuna(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- These 3 commits seem to be available for 6.12-rc1. Would it be possible to backport them into the freshly released 6.11 kernel? 7ad660f9991d dt-bindings: arm: qcom: Add Lenovo ThinkPad T14s Gen 6 e6b5a4c3ae3b firmware: qcom: scm: Allow QSEECOM on ThinkPad T14s 7d1cbe2f4985 arm64: dts: qcom: Add X1E78100 ThinkPad T14s Gen 6 Sources: https://www.phoronix.com/news/Linux-X1E-ThinkPad-T14s-Gen-6 "The Linux DT patches for the ThinkPad T14s Gen 6 can be found on the kernel mailing list. Here's to hoping the addition is ready to go later this year into the Linux v6.12 kernel" https://lore.kernel.org/lkml/20240719-topic-t14s_upstream-v1-0-d7d97fdebb28… https://patchew.org/linux/20240828-topic-t14s._5Fupstream-v2-0-49faea18de84… Thanks in advance! -- You are receiving this mail because: You are the assignee for the bug.

1 1

[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 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] 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 https://bugzilla.suse.com/show_bug.cgi?id=1231167#c5 --- Comment #5 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- You could make changes to installation ISO yourself, for testing. Here are the instruction how to do this: --- Download kernel-default*.rpm packages from the kernel of the day (KOT) repository [1] or build one yourself with additionally enabled modules. Download latest "minimal" Tumbleweed ISO from here [2]. Specify which modules you think are essential for device to boot. For example: export MODULES="ufs-qcom ..." Create driver upadate package (DUD) [3] from the downloaded/builded kernel package: mkdud --create qualcom.dud --dist TW --install repo kernel-default* Rebuild installation ISO init ramfs [4] with your additional modules specified above. sudo mksusecd --verbose --create qualcom.iso --rebuild-initrd \ --initrd qualcom.dud --kernel kernel-default* \ --modules ${MODULES} -- openSUSE-Tumbleweed-NET-aarch64-Current.iso Test new qualcom.iso. Please try to narrow down required modules. Once you are happy with the result share the list of modules here. Hope this helps. [1] https://download.opensuse.org/repositories/Kernel:/stable/ARM/aarch64/ [2] https://download.opensuse.org/ports/aarch64/tumbleweed/iso/openSUSE-Tumblew… [3] https://github.com/openSUSE/mkdud [4] https://github.com/openSUSE/mksusecd -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231235] Please backport 6.12 snapdragon lenovo t14s gen6 drivers to 6.11 kernel
by bugzilla_noreply＠suse.com 02 Oct '24

02 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231235 https://bugzilla.suse.com/show_bug.cgi?id=1231235#c1 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |jslaby(a)suse.com Resolution|--- |FIXED --- Comment #1 from Jiri Slaby <jslaby(a)suse.com> --- Pushed. -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231167 https://bugzilla.suse.com/show_bug.cgi?id=1231167#c3 --- Comment #3 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- Take a look here for example how to add new driver to install image: https://github.com/openSUSE/installation-images/pull/669 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1230893] Kernel panic/kernel crash on HP ProBook laptop
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230893 https://bugzilla.suse.com/show_bug.cgi?id=1230893#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(nada-infinita@pos | |teo.net) CC| |nada-infinita(a)posteo.net, | |tiwai(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Is it a regression? e.g. didn't i happen with 6.9.x kernel? Also, how about 6.11.x kernel in OBS Kernel:stable repo? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231068] New: modprobe v4l2loopback: key rejected by service / opensuse i6.4.0-150600.23.22-default
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231068 Bug ID: 1231068 Summary: modprobe v4l2loopback: key rejected by service / opensuse i6.4.0-150600.23.22-default Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: obs(a)akr.yagii.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Actual behaviour: # uname -a Linux xxx 6.4.0-150600.23.22-default #1 SMP PREEMPT_DYNAMIC Fri Sep 13 10:42:50 UTC 2024 (5c05eeb) x86_64 x86_64 x86_64 GNU/Linux # rpm -q v4l2loopback-kmp-default v4l2loopback-kmp-default-0.13.1_k6.4.0_150600.21-lp156.1.8.x86_64 u # find /lib/modules/ -name 'v4l*.ko' /lib/modules/6.4.0-150600.23.17-default/weak-updates/updates/v4l2loopback.ko /lib/modules/6.4.0-150600.21-default/updates/v4l2loopback.ko /lib/modules/6.4.0-150600.23.22-default/weak-updates/updates/v4l2loopback.ko # modprobe v4l2loopback modprobe: ERROR: could not insert 'v4l2loopback': Key was rejected by service Expected behaviour: - module loads w/o issue -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1215516] kernel: RT requires X86_FEATURE_CONSTANT_TSC
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1215516 Martin Loviska <mloviska(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.suse.com/s | |how_bug.cgi?id=1230940 -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231167 https://bugzilla.suse.com/show_bug.cgi?id=1231167#c1 --- Comment #1 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- Thanks, but I think this module will need to be added into initramfs too. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231068] modprobe v4l2loopback: key rejected by service / opensuse i6.4.0-150600.23.22-default
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231068 https://bugzilla.suse.com/show_bug.cgi?id=1231068#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |obs(a)akr.yagii.de, | |tiwai(a)suse.com Flags| |needinfo?(obs(a)akr.yagii.de) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- I guess you enabled Secure Boot? Have you imported / deployed MOK for openSUSE properly? Otherwise a module built in OBS won't be loaded. -- You are receiving this mail because: You are the assignee for the bug.

1 0