October 2024 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[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