October 2024 - openSUSE Kernel Bugs - openSUSE Mailing Lists

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

25 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231247 Héctor Orón Martínez <hector.oron(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1232292] Machine locks on restore from hibernation after upgrade to kernel-default 5.14.21-150500.55.83-default
by bugzilla_noreply＠suse.com 25 Oct '24

25 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1232292 https://bugzilla.suse.com/show_bug.cgi?id=1232292#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- . *** This bug has been marked as a duplicate of bug 1231578 *** -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1232342] No Ethernet device anymore on RPi3
by bugzilla_noreply＠suse.com 25 Oct '24

25 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1232342 https://bugzilla.suse.com/show_bug.cgi?id=1232342#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> --- Do you have the dmesg output from the working case, too? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1232342] New: No Ethernet device anymore on RPi3
by bugzilla_noreply＠suse.com 25 Oct '24

25 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1232342 Bug ID: 1232342 Summary: No Ethernet device anymore on RPi3 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: aarch64 URL: https://openqa.opensuse.org/tests/4593773/modules/prep are_firstboot/steps/1 OS: Other Status: NEW Severity: Major 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-15.6-JeOS-for-RPi-aarch64-jeos@RPi3 fails in [prepare_firstboot](https://openqa.opensuse.org/tests/4593773/modules/prepar… Since build 13.376 Leap 15.6 fails to boot RPi3 in openQA. Same problem with Leap 15.5 since build 13.326: https://openqa.opensuse.org/tests/4591682#next_previous Serial connection showed that the problem is Ethernet device is not found (for both Leap 15.5 and 15.6). ## 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 [13.376](https://openqa.opensuse.org/tests/4545136) ## Expected result Last good: [13.375](https://openqa.opensuse.org/tests/4542889) (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 1225352] [Build 13.199] openQA test fails in prepare_firstboot: RPi3 not booting?
by bugzilla_noreply＠suse.com 25 Oct '24

25 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c52 --- Comment #52 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- (In reply to Fabian Vogt from comment #51) > (In reply to Guillaume GARDET from comment #49) > > Created attachment 878195 [details] > > 15.5 log for no eth0 > > > > A quick check shows eth0 is not found: > > That's bad. Can you create a new bug report for this? Tracked in https://bugzilla.opensuse.org/show_bug.cgi?id=1232342 -- 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 25 Oct '24

25 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c51 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|REOPENED |RESOLVED --- Comment #51 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Guillaume GARDET from comment #49) > Created attachment 878195 [details] > 15.5 log for no eth0 > > A quick check shows eth0 is not found: That's bad. Can you create a new bug report for this? -- 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 25 Oct '24

25 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c50 --- Comment #50 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- Created attachment 878201 --> https://bugzilla.suse.com/attachment.cgi?id=878201&action=edit dmesg 15.6 for no eth0 Same problem on Leap 15.6, no eth0: ********** Welcome to openSUSE Leap 15.6 - Kernel 6.4.0-150600.23.25-default (ttyS0). wlan0: localhost login: ********** -- 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 25 Oct '24

25 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231465 https://bugzilla.suse.com/show_bug.cgi?id=1231465#c40 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(felix.niederwange | |r(a)suse.com) --- Comment #40 from Jiri Slaby <jslaby(a)suse.com> --- Thanks a lot for the bisection. Could you also cold-boot my kernel and attach dmesg from that boot? I am curious if the table is really present on the stable location, only the config table pointer to memattr gets corrupted. -- 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 24 Oct '24

24 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1225352 https://bugzilla.suse.com/show_bug.cgi?id=1225352#c49 --- Comment #49 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- Created attachment 878195 --> https://bugzilla.suse.com/attachment.cgi?id=878195&action=edit 15.5 log for no eth0 A quick check shows eth0 is not found: ********** Welcome to openSUSE Leap 15.5 - Kernel 5.14.21-150500.55.83-default (ttyS0). wlan0: localhost login: ********** -- 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 24 Oct '24

24 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231465 https://bugzilla.suse.com/show_bug.cgi?id=1231465#c39 --- Comment #39 from Jiri Slaby <jslaby(a)suse.com> --- Reported upstream: https://lore.kernel.org/all/ec7db629-61b0-49aa-a67d-df663f004cd0@kernel.org/ -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1232292] Machine locks on restore from hibernation after upgrade to kernel-default 5.14.21-150500.55.83-default
by bugzilla_noreply＠suse.com 24 Oct '24

24 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1232292 https://bugzilla.suse.com/show_bug.cgi?id=1232292#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> --- Likely the dup of bsc#1231578 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1230062] New: RISC-V: virtio-console sometimes gets stuck in set_termios.part.0
by bugzilla_noreply＠suse.com 24 Oct '24

24 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230062 Bug ID: 1230062 Summary: RISC-V: virtio-console sometimes gets stuck in set_termios.part.0 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: RISC-V OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 877101 --> https://bugzilla.suse.com/attachment.cgi?id=877101&action=edit /proc/*/task/*/stack + strace of bash openQA types in commands to the serial console, sends a newline and then waits until the prompt appears. Running this in a loop causes it to get stuck sometimes: https://openqa.opensuse.org/tests/4445068#step/http_srv/16 In the QEMU chardev log it appears like this: # systemctl --no-pager is-active apache2; echo hjhkw-$?- active hjhkw-0- echo Lorem ipsum dolor sit amet > /srv/www/htdocs/index.html openQA sends 'systemctl --no-pager is-active apache2; echo hjhkw-$?-\n', receives 'active\nhjhkw-0-\n', then sends 'echo Lorem ipsum dolor sit amet > /srv/www/htdocs/index.html\n' and waits for '# '. That does not arrive however and the wait times out. In most cases that's just ignored by openQA and it moves on to the next command. When it sends that ("curl -f ..." here), the missing part suddenly appears: # echo Lorem ipsum dolor sit amet > /srv/www/htdocs/index.html # curl -f http://localhost/ | grep 'Lorem ipsum dolor sit amet'; echo _Z5Xg-$?- This issue appears to happen on riscv64 only, I have not observed it anywhere else so far. Thankfully the arbitrarily long delay of the prompt allows to debug this. I created a testcase that exercises the serial terminal in a loop and so far it always gets stuck before the 20th attempt. I logged onto the graphical console and collected some info. The /bin/bash process on the console is stuck in the kernel: /proc/1624/task/1624/stack:[<0>] set_termios.part.0+0x130/0x206 /proc/1624/task/1624/stack:[<0>] tty_mode_ioctl+0x46e/0x576 /proc/1624/task/1624/stack:[<0>] n_tty_ioctl_helper+0x2a/0xe4 /proc/1624/task/1624/stack:[<0>] n_tty_ioctl+0x9a/0x148 /proc/1624/task/1624/stack:[<0>] tty_ioctl+0x170/0x64e /proc/1624/task/1624/stack:[<0>] __riscv_sys_ioctl+0x82/0xaa /proc/1624/task/1624/stack:[<0>] do_trap_ecall_u+0x200/0x212 /proc/1624/task/1624/stack:[<0>] handle_exception+0xde/0xde FWICT this is inside the "retry_write_wait" loop: https://github.com/torvalds/linux/blob/67784a74e258a467225f0e68335df77acd67… No other process trace has any related tty call pending. When I attached to the process with strace, it immediately continued and the missing output appeared on the serial console. /proc/*/task/*/stack and strace log are attached. The first syscall that strace reports is rt_sigprocmask(SIG_BLOCK, ...), which usually follows ioctl(0, TCSETSW, ...), so it was probably stuck in that ioctl. As it helps to provide more input or attach with strace, it appears like some wakeup signal is missing or got lost that would notify the wait that the write has completed. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1231802] [drm] *ERROR* Atomic update failure on pipe A
by bugzilla_noreply＠suse.com 23 Oct '24

23 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231802 https://bugzilla.suse.com/show_bug.cgi?id=1231802#c2 --- Comment #2 from John Shand <jshand2013(a)gmail.com> --- (In reply to Takashi Iwai from comment #1) > Do you see any real issue (some visual influence on the graphics output)? There is not real graphical error, just it came up in kernel logs as a error with red -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231800] Many problems with kernel prior 6.9 release. AMD platform.
by bugzilla_noreply＠suse.com 23 Oct '24

23 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231800 https://bugzilla.suse.com/show_bug.cgi?id=1231800#c11 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |Kernel:Filesystems Assignee|kernel-bugs(a)opensuse.org |kernel-fs(a)suse.de --- Comment #11 from Takashi Iwai <tiwai(a)suse.com> --- I don't know of such changes. As the main problem is about the filesystems, let's toss to filesystem guys. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231800] New: Many problems with kernel prior 6.9 release. AMD platform.
by bugzilla_noreply＠suse.com 23 Oct '24

23 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231800 Bug ID: 1231800 Summary: Many problems with kernel prior 6.9 release. AMD platform. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: slawek(a)lach.art.pl QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:131.0) Gecko/20100101 Firefox/131.0 Build Identifier: I currently must work on kernel 6.8, cause any newer causes serious problem. I trying many thinks, but nothing helps. Firstly, this bug may be related to closed source NVidia driver. Kernel many times do panic and print some debug info with NVidia string. I try to disable nvidia module. Blacklisting does nothing, so I removed it and try to ran 6.11 kernel. But, I do not disable NVidia service and maybe I unfortunately install it again. Meanwhile, I got information about update in discover and it hangs on installing updates. I try with zypper and I must accept license for NVidia. Discover do not ask for accepting license in previous event, so I think NVidia kernel was installed again, without my knowledge, as I described. When installing via zypper, system halt and sound was playing in loop. Fortunaty, I installed NVidia service and remove nvidia drivers via zypper and test 6.11 again. System many times complained about XFS (/home) filesystem error. Plasma 6.2 then reset and default settings was loaded. I currently, again working on 6.8. Related info: https://www.gamingonlinux.com/2024/08/nvidia-driver-with-linux-kernel-6-10-… . https://forums.opensuse.org/t/when-kernels-e8c6092e52f8-will-be-applied-on-… https://forums.opensuse.org/t/asus-zenbook-flip-15-kernel-6-9-fail-to-boot/… Thanks. Reproducible: Sometimes Steps to Reproduce: 1. Ran system, play many web games (freecivweb, total battle, forge of empires, the settlers: online, tentlan, etc.) at once, play video. Actual Results: On 6.8 no problems, but on newer multiple problems. I am not sure system is hanging, because it may be related to NVidia driver, but sometimes system complained about filesystem is mounted read only. Expected Results: Everything working without problems, like in 6.8. My laptop is ASUS ZenBook Flip 15. Operating System: openSUSE Tumbleweed 20241016 KDE Plasma Version: 6.2.1 KDE Frameworks Version: 6.7.0 Qt Version: 6.7.3 Kernel Version: 6.8.9-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 7 4700U with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: ZenBook UX562IQ_UM562IQ System Version: 1.0 -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 1231800] Many problems with kernel prior 6.9 release. AMD platform.
by bugzilla_noreply＠suse.com 23 Oct '24

23 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231800 https://bugzilla.suse.com/show_bug.cgi?id=1231800#c8 --- Comment #8 from Takashi Iwai <tiwai(a)suse.com> --- You aren't booting from the snapshot, right? I haven't heard of XFS problem with 6.11 kernel, so it's likely a real filesystem corruption. But the read-only btrfs smells already bad... -- 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 23 Oct '24

23 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230418 https://bugzilla.suse.com/show_bug.cgi?id=1230418#c15 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|NEW |RESOLVED --- Comment #15 from Takashi Iwai <tiwai(a)suse.com> --- Closing as the reporter won't be able to test. Feel free to reopen if the problem persists with the latest TW release. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231802] [drm] *ERROR* Atomic update failure on pipe A
by bugzilla_noreply＠suse.com 23 Oct '24

23 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231802 https://bugzilla.suse.com/show_bug.cgi?id=1231802#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(jshand2013@gmail. | |com) CC| |tiwai(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Do you see any real issue (some visual influence on the graphics output)? -- 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 23 Oct '24

23 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230835 https://bugzilla.suse.com/show_bug.cgi?id=1230835#c5 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- Let's close, then. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231802] [drm] *ERROR* Atomic update failure on pipe A
by bugzilla_noreply＠suse.com 23 Oct '24

23 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231802 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Other |Kernel Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1232046] PC Freezes When Coming Out of Sleep
by bugzilla_noreply＠suse.com 22 Oct '24

22 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1232046 https://bugzilla.suse.com/show_bug.cgi?id=1232046#c1 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adamska156(a)gmail.com, | |Andreas.Stieger(a)gmx.de Component|Basesystem |Kernel Flags| |needinfo?(adamska156@gmail. | |com) Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org --- Comment #1 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- (In reply to Rylee K from comment #0) > I've looked through logs and don't see anything but I don't know what to > look for. Attach the logs you were looking at. > This issue has been occuring for 2 or 3 weeks. Roll back to when this was last working. Then update packages one by one and see which single package added this. Start with Kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1218682] New: EFI aarch64 boot failure on honeycomb lx2
by bugzilla_noreply＠suse.com 22 Oct '24

22 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1218682 Bug ID: 1218682 Summary: EFI aarch64 boot failure on honeycomb lx2 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: james.hobson(a)oriel.ox.ac.uk QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- We are running micro os (tumbleweed) on two build servers. Two nights ago, these failed to boot after an upgrade, same thing happened last night. The hardware is the honeycomb lx2, the boot log is: Booting `openSUSE MicroOS' Loading Linux 6.6.9-1-default ... Loading initial ramdisk ... [ 0.687447][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000140, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 0.699962][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 0.712472][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 0.724981][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 0.737490][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 0.749998][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 0.762507][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 0.775015][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 0.787522][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 0.800030][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 1.187743][ T99] fsl_mc_bus NXP0008:00: mc_get_version() failed with error -110 [ 5.689703][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 5.702224][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 5.714736][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 5.727248][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 5.739760][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 5.752271][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 5.764783][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 5.777294][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 5.789805][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 5.802316][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.693031][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.705546][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.718058][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.730569][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.743080][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.755592][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.768102][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.780613][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.793124][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.805635][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.696364][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.708881][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.721393][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.733904][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.746416][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.758927][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.771438][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.783949][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.796460][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.808971][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.699708][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.712228][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.724743][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.737256][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.749770][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.762283][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.774797][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.787311][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.799824][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.812337][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.703043][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.715557][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.728071][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.740585][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.753098][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.765611][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.778124][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.790637][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.803150][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.815663][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.706370][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.718885][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.731398][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.743911][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.756424][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.768937][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.781450][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.793964][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.806477][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.818990][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.709704][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.722219][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.734732][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.747245][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.759758][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.772271][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.784785][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.797298][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.809811][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.822325][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.713036][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.725551][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.738064][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.750578][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.763090][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.775603][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.788117][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.800630][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.813143][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.825656][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 44.003022][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 26s! [swapper/0:0] [ 45.716367][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 45.728884][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 45.741398][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 45.753912][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 45.766425][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 45.778939][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 45.791452][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 45.803965][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 45.816479][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 45.828992][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.719700][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.732214][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.744728][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.757240][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.769754][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.782267][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.794780][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.807294][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.819807][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.832320][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1231583] New: kernel panic especially shorttly after wakeup from STR on linux-default-6.4.0 "kernel BUG at ../lib/dynamic_queue_limits.c:27!"
by bugzilla_noreply＠suse.com 22 Oct '24

22 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231583 Bug ID: 1231583 Summary: kernel panic especially shorttly after wakeup from STR on linux-default-6.4.0 "kernel BUG at ../lib/dynamic_queue_limits.c:27!" Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: okurz(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 877944 --> https://bugzilla.suse.com/attachment.cgi?id=877944&action=edit dmesg of kernel panic especially shorttly after wakeup from STR on linux-default-6.4.0 showing "kernel BUG at ../lib/dynamic_queue_limits.c:27!" ## Observation Since about 2024-06-19 on my Dell Inc. Latitude 5300 2-in-1/0J9C2F, BIOS 1.19.0 12/14/2021, I observed multiple kernel panics, mostly either immediately or some seconds after wakeup from STR. After enabling kdump I could verify that every time the problem reported is "kernel BUG at ../lib/dynamic_queue_limits.c:27! invalid opcode: 0000 [#1] PREEMPT SMP NOPTI". Currently running 6.4.0-150600.23.25-default. stack trace of latest recorded kernel panic: ``` [27011.816948] kernel BUG at ../lib/dynamic_queue_limits.c:27! [27011.816961] invalid opcode: 0000 [#1] PREEMPT SMP NOPTI [27011.816969] CPU: 0 PID: 10821 Comm: StreamT~ns #477 Kdump: loaded Tainted: P OE n 6.4.0-150600.23.25-default #1 SLE15-SP6 7129efd26ed51feb3306c16abaa78c465d48fc44 [27011.816981] Hardware name: Dell Inc. Latitude 5300 2-in-1/0J9C2F, BIOS 1.19.0 12/14/2021 [27011.816987] RIP: 0010:dql_completed+0x13b/0x150 [27011.817001] Code: ef 74 01 48 89 57 58 e9 47 ff ff ff 85 ed 40 0f 95 c5 41 39 db 41 0f 95 c3 44 84 dd 74 04 85 d2 78 0a 44 89 c1 e9 29 ff ff ff <0f> 0b 01 f6 44 89 c2 29 f2 0f 48 d1 eb 8a cc cc cc cc cc cc cc 90 [27011.817013] RSP: 0000:ffff993541cf3de8 EFLAGS: 00010293 [27011.817021] RAX: 00000000000000aa RBX: ffff8d9a81e09b78 RCX: 00000022dd8dc000 [27011.817029] RDX: 00000022dd8da000 RSI: 000000000000012e RDI: ffff8d9a81d03100 [27011.817036] RBP: ffff8d9a81e099c0 R08: 0000000000000001 R09: 0000000000000000 [27011.817043] R10: 00000000000000aa R11: 0000000000000000 R12: ffff8d9a81d03000 [27011.817050] R13: ffff8d9a81e09b98 R14: ffff8d9a81e09000 R15: 0000000000000006 [27011.817056] FS: 00007f8df98036c0(0000) GS:ffff8da1c7e00000(0000) knlGS:0000000000000000 [27011.817064] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [27011.817071] CR2: 00007f8ded069000 CR3: 00000001dcd82001 CR4: 00000000003706f0 [27011.817078] Call Trace: [27011.817084] <TASK> [27011.817091] ? __die_body+0x1a/0x60 [27011.817103] ? die+0x38/0x60 [27011.817111] ? do_trap+0x10a/0x120 [27011.817120] ? dql_completed+0x13b/0x150 [27011.817129] ? do_error_trap+0x64/0xa0 [27011.817137] ? dql_completed+0x13b/0x150 [27011.817146] ? exc_invalid_op+0x53/0x60 [27011.817154] ? dql_completed+0x13b/0x150 [27011.817161] ? asm_exc_invalid_op+0x16/0x20 [27011.817172] ? dql_completed+0x13b/0x150 [27011.817181] write_bulk_sg_callback+0xc7/0x1e0 [r8152 5053a9ece6fed4b24993dc907e4c2f28089d5aff] [27011.817210] __usb_hcd_giveback_urb+0x84/0x120 [usbcore e5761cade106b17f06019a7c390c1f126777ec30] [27011.817286] usb_giveback_urb_bh+0x94/0x120 [usbcore e5761cade106b17f06019a7c390c1f126777ec30] [27011.817357] tasklet_action_common.isra.23+0xc0/0x240 [27011.817369] __do_softirq+0xbf/0x2b3 [27011.817379] irq_exit_rcu+0xa3/0xc0 [27011.817387] common_interrupt+0x8b/0xa0 [27011.817395] asm_common_interrupt+0x22/0x40 [27011.817403] RIP: 0033:0x7f8e13180ceb [27011.817468] Code: 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 c4 41 01 ef ff 89 f8 09 f0 c1 e0 14 3d 00 00 00 f8 0f 87 29 03 00 00 c5 fe 6f 07 <c5> fd 74 0e c5 85 74 d0 c5 ed df c9 c5 fd d7 c9 ff c1 74 61 90 f3 [27011.817480] RSP: 002b:00007f8df9802098 EFLAGS: 00000287 [27011.817489] RAX: 00000000e9400000 RBX: 00007f8de5ed8e80 RCX: 000000000000000c [27011.817496] RDX: 00007f8e0c3b37a0 RSI: 00007f8e09877a14 RDI: 00007f8de5ed8e80 [27011.817504] RBP: 0000000000000014 R08: 0000000000000053 R09: 00000000ffffffff [27011.817511] R10: 0000000000000000 R11: 00007f8e131a8680 R12: 00007f8ded069330 [27011.817519] R13: 00007f8e0c3b3840 R14: 0000000000000000 R15: 000000000000000a [27011.817530] </TASK> [27011.817535] Modules linked in: rfcomm snd_seq_dummy snd_hrtimer snd_seq tun nf_conntrack_netbios_ns nf_conntrack_broadcast ccm tls nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet af_packet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat wireguard libchacha20poly1305 chacha_x86_64 poly1305_x86_64 curve25519_x86_64 libcurve25519_generic libchacha ip6_udp_tunnel udp_tunnel nf_tables ebtable_nat ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_raw iptable_security ip_set nfnetlink ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter qrtr(n) cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi nls_iso8859_1 nls_cp437 vfat fat snd_sof_pci_intel_cnl ext4 snd_sof_intel_hda_common soundwire_intel hid_multitouch wacom snd_sof_intel_hda_mlink mbcache binfmt_misc jbd2 soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils [27011.817631] soundwire_generic_allocation iTCO_wdt soundwire_bus spi_nor intel_pmc_bxt i2c_designware_platform ee1004(n) iTCO_vendor_support mei_wdt mei_hdcp(n) i2c_designware_core mtd mei_pxp dell_rbtn(n) snd_soc_skl(n) ccp snd_soc_hdac_hda snd_hda_ext_core dell_laptop intel_rapl_msr snd_ctl_led snd_soc_sst_ipc snd_hda_codec_realtek snd_soc_sst_dsp dell_smm_hwmon(n) snd_soc_acpi_intel_match snd_soc_acpi snd_hda_codec_generic intel_tcc_cooling(n) snd_soc_core x86_pkg_temp_thermal dell_wmi snd_compress snd_pcm_dmaengine intel_powerclamp coretemp iwlmvm snd_hda_intel kvm_intel dell_smbios snd_intel_dspcfg dcdbas(X) snd_intel_sdw_acpi kvm irqbypass pcspkr uvcvideo snd_usb_audio btusb snd_hda_codec videobuf2_vmalloc dell_wmi_sysman(n) snd_usbmidi_lib btrtl dell_wmi_ddv(n) ledtrig_audio dell_wmi_descriptor efi_pstore(n) firmware_attributes_class(n) thunderbolt wmi_bmof mac80211 intel_wmi_thunderbolt(n) snd_hda_core spi_intel_pci(n) snd_ump uvc btintel i2c_i801 spi_intel(n) btbcm videobuf2_memops btmtk libarc4 snd_hwdep [27011.817760] i2c_smbus squashfs bluetooth snd_rawmidi snd_seq_device videobuf2_v4l2 mei_me mei snd_pcm loop videodev snd_timer hid_sensor_incl_3d ecdh_generic intel_lpss_pci hid_sensor_magn_3d hid_sensor_rotation snd hid_sensor_gyro_3d hid_sensor_accel_3d videobuf2_common intel_lpss iwlwifi crc16 mc idma64 soundcore hid_sensor_trigger hid_sensor_iio_common processor_thermal_device_pci_legacy(n) industrialio_triggered_buffer kfifo_buf processor_thermal_device processor_thermal_rfim processor_thermal_mbox industrialio tiny_power_button(n) processor_thermal_rapl intel_rapl_common intel_pch_thermal intel_soc_dts_iosf(n) thermal button joydev int3403_thermal soc_button_array(n) int340x_thermal_zone int3400_thermal intel_hid(n) intel_pmc_core acpi_thermal_rel sparse_keymap acpi_pad ac nvme_fabrics fuse nvme_keyring configfs dmi_sysfs ip_tables x_tables dm_crypt essiv authenc typec_displayport r8152(OEX) hid_sensor_custom(n) hid_sensor_hub intel_ishtp_hid wl(POEn) crc32_pclmul polyval_clmulni(n) polyval_generic(n) gf128mul [27011.817891] ghash_clmulni_intel hid_generic sha512_ssse3 rtsx_pci_sdmmc sha256_ssse3 usbhid i915 nvme sha1_ssse3 mmc_core i2c_algo_bit cfg80211 drm_buddy nvme_core ttm drm_display_helper nvme_auth rtsx_pci t10_pi aesni_intel crc64_rocksoft_generic ucsi_acpi cec xhci_pci typec_ucsi video intel_ish_ipc xhci_pci_renesas crypto_simd crc64_rocksoft xhci_hcd cryptd usbcore roles crc64 mfd_core rc_core intel_ishtp i2c_hid_acpi rfkill typec i2c_hid battery wmi pinctrl_cannonlake serio_raw btrfs blake2b_generic libcrc32c crc32c_intel xor raid6_pq dm_mod uhid br_netfilter bridge stp llc msr efivarfs [27011.817994] Unloaded tainted modules: intel_pmc_core_pltdrv(n):1 [27011.818026] Supported: No, Proprietary modules are loaded ``` In three stack traces I found ``` write_bulk_sg_callback+0xc7/0x1e0 [r8152 5053a9ece6fed4b24993dc907e4c2f28089d5aff] ``` so potentially the problem source is the network driver r8152 but maybe that's only a symptom. ## Reproducible Unclear. So far only observed on that device after some wakeups from STR, not all. Not fully reproducible yet. ## Expected result Last known good is possibly kernel-default-5.14.21-150500.55.52.1 from Leap 15.5 -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 1225891] [tw][Build 20240531] sysctl 'Sysctl_fs_inotify_max_user_watches' value is changed
by bugzilla_noreply＠suse.com 22 Oct '24

22 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1225891 https://bugzilla.suse.com/show_bug.cgi?id=1225891#c1 Jozef Pupava <jpupava(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jpupava(a)suse.com Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #1 from Jozef Pupava <jpupava(a)suse.com> --- Issue does not happen anymore -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1220088] Hibernate completes shuts machine off *then* machine automatically turns back on.
by bugzilla_noreply＠suse.com 22 Oct '24

22 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1220088 https://bugzilla.suse.com/show_bug.cgi?id=1220088#c5 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com Flags| |needinfo?(pj.opensuse(a)gmx.c | |om) --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- Is this a regression by the updates, e.g. by the recent kernels? You can try to check /proc/acpi/wakeup contents and disable the wake up sources by writing to it. e.g. echo -n XHC1 > /proc/acpi/wakeup will toggle the enable/disable of the wakeup from XHC1. After disabling all wake up sources, go to hibernate and check whether the wake up happens. Last but not least, please give the hwinfo output and the dmesg output. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231813] [riscv64][Unmatched][regression] Hard lockup on reboot/poweroff
by bugzilla_noreply＠suse.com 22 Oct '24

22 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231813 https://bugzilla.suse.com/show_bug.cgi?id=1231813#c1 --- Comment #1 from Andreas Schwab <schwab(a)suse.de> --- Worksforme. Do you have any extra hardware installed? -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

22 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231662 https://bugzilla.suse.com/show_bug.cgi?id=1231662#c1 Santiago Zarate <santiago.zarate(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |santiago.zarate(a)suse.com --- Comment #1 from Santiago Zarate <santiago.zarate(a)suse.com> --- looking at the logs: > 2024-10-15 08:45:39 <3> localhost.localdomain(53696) [Ruby] modules/Kdump.rb(update_initrd_with):419 Error updating initrd, see /var/log/YaST2/y2logmkinitrd or call mkdumprd manually > 2024-10-15 08:45:39 <3> localhost.localdomain(53696) [Ruby] modules/Kdump.rb(update_initrd_with):420 Error updating initrd while calling 'mkdumprd'. See /var/log/YaST2/y2logmkinitrd for details. # cat /var/log/YaST2/y2logmkinitrd > Kernel not found. Though looking at the logs, system is running: 6.11.2-1-default > 2024-10-15T08:36:15.591952+00:00 localhost [RPM][53586]: Transaction ID 670e297e started > 2024-10-15T08:36:51.228311+00:00 localhost [RPM][53586]: install kernel-default-debugsource-6.11.2-1.2.aarch64: success > 2024-10-15T08:36:51.296736+00:00 localhost [RPM][53586]: install kernel-default-debugsource-6.11.2-1.2.aarch64: success > 2024-10-15T08:36:51.296875+00:00 localhost [RPM][53586]: Transaction ID 670e297e finished: 0 > 2024-10-15T08:37:11.544524+00:00 localhost [RPM][53593]: Transaction ID 670e29aa started > 2024-10-15T08:44:53.779988+00:00 localhost [RPM][53593]: install kernel-default-debuginfo-6.11.2-1.2.aarch64: success > 2024-10-15T08:44:53.825653+00:00 localhost [RPM][53593]: install kernel-default-debuginfo-6.11.2-1.2.aarch64: success > 2024-10-15T08:44:53.835874+00:00 localhost [RPM][53593]: Transaction ID 670e29aa finished: 0 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231825] Kernel 6.11.4 bluetooth scan stops working
by bugzilla_noreply＠suse.com 22 Oct '24

22 Oct '24

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

1 0

[Bug 1231800] Many problems with kernel prior 6.9 release. AMD platform.
by bugzilla_noreply＠suse.com 21 Oct '24

21 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231800 https://bugzilla.suse.com/show_bug.cgi?id=1231800#c4 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- Well, we can't debug anything unless you can give the crash log or whatever. In anyway, it's right to start with the complete removal of Nvidia stuff. Uninstall the relevant packages and possibly leftover configs. Then check whether you can still booth 6.8 kernel without Nvidia. After that, try to install only kernel-default-6.11.x package, and boot with it. Does the boot fail? If it doesn't, please give the errors or the problematic symptom as precisely as possible. If the filesystem error shows up, try to boot the latest TW ISO and the recovery image from there. It must be also 6.11.x kernel. Then you can try to repair the filesystems, if needed, too. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231772] New: network-netperf-rr-ipv4-unbound upstream regresses in comparison to SP6
by bugzilla_noreply＠suse.com 21 Oct '24

21 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231772 Bug ID: 1231772 Summary: network-netperf-rr-ipv4-unbound upstream regresses in comparison to SP6 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: gabriel.bertazi(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Looking at the dashboard, we see all machines have regressed the network-netperf-rr-ipv4-unbound benchmark, TCP and UDP, between SLE-15-SP6-6.4.0-150600.23.25 and 15.6-6.12.0-rc1. While some of the machines have reported unreasonably high variance, some of them have lower variance and the issue is still visible. i.e: cedric: 1 6.4.0-150600.23.25 6.12.0-rc1-vanilla Hmean 1 1551.36 ( 0.00%) 1037.44 ( -33.13%) Stddev 1 20.03 ( 0.00%) 58.39 (-191.52%) CoeffVar 1 1.29 ( 0.00%) 5.61 (-334.88%) pumbaa: Hmean 1 1965.47 ( 0.00%) 564.17 ( -71.30%) Stddev 1 85.42 ( 0.00%) 2.31 ( 97.29%) CoeffVar 1 4.34 ( 0.00%) 0.41 ( 90.54%) My first idea, would be the eevdf schedduler. But if we look at the upstream dashboard, while there is definitely an EEVDF comoponent, there is also a difference between SP6 and 6.10 that deserves investigation: 6.10.0 6.11.0 6.12.0-rc1 cedric: Hmean 1 952.58 ( 0.00%) 906.93 ( -4.79%) 598.35 ( -37.19%) Stddev 1 107.52 ( 0.00%) 157.16 ( -46.17%) 80.04 ( 25.56%) CoeffVar 1 11.15 ( 0.00%) 16.89 ( -51.51%) 13.17 ( -18.10%) pumbaa: Hmean 1 653.23 ( 0.00%) 680.09 ( 4.11%) 564.17 ( -13.63%) Stddev 1 37.20 ( 0.00%) 38.57 ( -3.69%) 2.31 ( 93.78%) CoeffVar 1 5.68 ( 0.00%) 5.65 ( 0.39%) 0.41 ( 92.77%) This bug tracks the netperf regression with the goal of explaining and/or fixing the regression between 6.4.0-150600.23 and 6.10, as well as measuring the real impact of the EEVDF regression, confirming it is the sole cause of regression between 6.10 and 6.12.0-rc1. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1220088] Hibernate completes shuts machine off *then* machine automatically turns back on.
by bugzilla_noreply＠suse.com 21 Oct '24

21 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1220088 Stefan Hundhammer <shundhammer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org Component|Basesystem |Kernel -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1219444] New: amdgpu critical error
by bugzilla_noreply＠suse.com 21 Oct '24

21 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1219444 Bug ID: 1219444 Summary: amdgpu critical error Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: teuniz(a)protonmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 872372 --> https://bugzilla.suse.com/attachment.cgi?id=872372&action=edit Output of dmesg The kernel crashes approx every 5 minutes. I reverted back to kernel 5.14.21-150500.55.19-default because with that one it crashes approx once a day. Operating System: openSUSE Leap 15.5 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 5.14.21-150500.55.44-default (64-bit) Graphics Platform: X11 Processors: 32 × 13th Gen Intel Core i9-13900K Memory: 31.0 GiB of RAM Graphics Processor: AMD Radeon Pro W6600 Manufacturer: HP Product Name: HP Z2 Tower G9 Workstation Desktop PC dmesg | grep amdgpu [ 1.540640] [drm] amdgpu kernel modesetting enabled. [ 1.540703] amdgpu: CRAT table not found [ 1.540705] amdgpu: Virtual CRAT table created for CPU [ 1.540712] amdgpu: Topology: Add CPU node [ 1.542670] amdgpu 0000:03:00.0: amdgpu: Fetched VBIOS from VFCT [ 1.542671] amdgpu: ATOM BIOS: 113-D5330400-100 [ 1.542770] amdgpu 0000:03:00.0: vgaarb: deactivate vga console [ 1.542771] amdgpu 0000:03:00.0: amdgpu: Trusted Memory Zone (TMZ) feature disabled as experimental (default) [ 1.542799] amdgpu 0000:03:00.0: amdgpu: VRAM: 8176M 0x0000008000000000 - 0x00000081FEFFFFFF (8176M used) [ 1.542800] amdgpu 0000:03:00.0: amdgpu: GART: 512M 0x0000000000000000 - 0x000000001FFFFFFF [ 1.542801] amdgpu 0000:03:00.0: amdgpu: AGP: 267894784M 0x0000008400000000 - 0x0000FFFFFFFFFFFF [ 1.542845] [drm] amdgpu: 8176M of VRAM memory ready [ 1.542845] [drm] amdgpu: 15892M of GTT memory ready. [ 1.548699] amdgpu 0000:03:00.0: amdgpu: PSP runtime database doesn't exist [ 1.548704] amdgpu 0000:03:00.0: amdgpu: PSP runtime database doesn't exist [ 2.854516] amdgpu 0000:03:00.0: amdgpu: STB initialized to 2048 entries [ 2.895100] amdgpu 0000:03:00.0: amdgpu: Will use PSP to load VCN firmware [ 3.094413] amdgpu 0000:03:00.0: amdgpu: RAS: optional ras ta ucode is not available [ 3.115717] amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available [ 3.115740] amdgpu 0000:03:00.0: amdgpu: smu driver if version = 0x0000000f, smu fw if version = 0x00000013, smu fw program = 0, version = 0x003b2b00 (59.43.0) [ 3.115745] amdgpu 0000:03:00.0: amdgpu: SMU driver if version not matched [ 3.115777] amdgpu 0000:03:00.0: amdgpu: use vbios provided pptable [ 3.165133] amdgpu 0000:03:00.0: amdgpu: SMU is initialized successfully! [ 3.268063] kfd kfd: amdgpu: Allocated 3969056 bytes on gart [ 3.268478] amdgpu: sdma_bitmap: ffff [ 3.302091] amdgpu: HMM registered 8176MB device memory [ 3.302135] amdgpu: SRAT table not found [ 3.302136] amdgpu: Virtual CRAT table created for GPU [ 3.302599] amdgpu: Topology: Add dGPU node [0x73e3:0x1002] [ 3.302601] kfd kfd: amdgpu: added device 1002:73e3 [ 3.302617] amdgpu 0000:03:00.0: amdgpu: SE 2, SH per SE 2, CU per SH 8, active_cu_number 28 [ 3.302658] amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0 [ 3.302659] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0 [ 3.302659] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0 [ 3.302660] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0 [ 3.302660] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0 [ 3.302661] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0 [ 3.302661] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0 [ 3.302662] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0 [ 3.302662] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0 [ 3.302663] amdgpu 0000:03:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0 [ 3.302663] amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0 [ 3.302664] amdgpu 0000:03:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0 [ 3.302665] amdgpu 0000:03:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 1 [ 3.302665] amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 1 [ 3.302666] amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 1 [ 3.302666] amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 1 [ 3.303573] [drm] Initialized amdgpu 3.49.0 20150101 for 0000:03:00.0 on minor 0 [ 3.308709] fbcon: amdgpudrmfb (fb0) is primary device [ 3.505728] amdgpu 0000:03:00.0: amdgpu: [mmhub] page fault (src_id:0 ring:157 vmid:0 pasid:0, for process pid 0 thread pid 0) [ 3.505731] amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x0000000006004000 from client 0x12 (VMC) [ 3.505733] amdgpu 0000:03:00.0: amdgpu: MMVM_L2_PROTECTION_FAULT_STATUS:0x0000073A [ 3.505733] amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: DCEDMC (0x3) [ 3.505734] amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x0 [ 3.505735] amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x5 [ 3.505735] amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [ 3.505735] amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x1 [ 3.505736] amdgpu 0000:03:00.0: amdgpu: RW: 0x0 [ 3.524299] amdgpu 0000:03:00.0: [drm] fb0: amdgpudrmfb frame buffer device [ 4.537456] snd_hda_intel 0000:03:00.1: bound 0000:03:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) [ 5.416287] amdgpu 0000:03:00.0: amdgpu: [mmhub] page fault (src_id:0 ring:157 vmid:0 pasid:0, for process pid 0 thread pid 0) [ 5.416312] amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x0000000006004000 from client 0x12 (VMC) [ 5.416319] amdgpu 0000:03:00.0: amdgpu: MMVM_L2_PROTECTION_FAULT_STATUS:0x00000000 [ 5.416324] amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: unknown (0x0) [ 5.416329] amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x0 [ 5.416333] amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x0 [ 5.416336] amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x0 [ 5.416340] amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x0 [ 5.416343] amdgpu 0000:03:00.0: amdgpu: RW: 0x0 [ 73.156519] amdgpu 0000:03:00.0: amdgpu: [mmhub] page fault (src_id:0 ring:157 vmid:0 pasid:0, for process pid 0 thread pid 0) [ 73.156538] amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x0000000006004000 from client 0x12 (VMC) [ 73.156546] amdgpu 0000:03:00.0: amdgpu: MMVM_L2_PROTECTION_FAULT_STATUS:0x0000073A [ 73.156551] amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: DCEDMC (0x3) [ 73.156562] amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x0 [ 73.156566] amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x5 [ 73.156570] amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [ 73.156578] amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x1 [ 73.156582] amdgpu 0000:03:00.0: amdgpu: RW: 0x0 uname -a 5.14.21-150500.55.44-default #1 SMP PREEMPT_DYNAMIC Mon Jan 15 10:03:40 UTC 2024 (cc7d8b6) x86_64 x86_64 x86_64 GNU/Linux lspci VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 WKS-XL [Radeon PRO W6600] -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 1229020] Zypper dup installed kernels which reboot immediately
by bugzilla_noreply＠suse.com 21 Oct '24

21 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1229020 https://bugzilla.suse.com/show_bug.cgi?id=1229020#c11 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com Flags| |needinfo?(wwonko(a)rdwarf.com | |) --- Comment #11 from Jiri Slaby <jslaby(a)suse.com> --- Could you add initcall_debug ignore_loglevel kernel parameters to see what the kernel is actually doing right before reboot? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231825] Kernel 6.11.4 bluetooth scan stops working
by bugzilla_noreply＠suse.com 21 Oct '24

21 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231825 https://bugzilla.suse.com/show_bug.cgi?id=1231825#c1 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(novell@tower-net. | |de) CC| |novell(a)tower-net.de --- Comment #1 from Jiri Slaby <jslaby(a)suse.com> --- 6.11.4 contains: 98ccd44002d8 Bluetooth: hci_conn: Fix UAF in hci_enhanced_setup_sync e63125eec47d Bluetooth: btusb: Don't fail external suspend requests 4cb9807c9b53 Bluetooth: RFCOMM: FIX possible deadlock in rfcomm_sk_state_change I've committed to stable few moments ago: 4084286151fc Bluetooth: btusb: Fix not being able to reconnect after suspend 2c1dda2acc41 Bluetooth: btusb: Fix regression with fake CSR controllers 0a12:0001 which is supposed to fix one of the above. So could you recheck :Backport once it builds? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231832] [Build 20241020] openQA test fails in podman_netavark
by bugzilla_noreply＠suse.com 21 Oct '24

21 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231832 https://bugzilla.suse.com/show_bug.cgi?id=1231832#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: https://lore.kernel.org/all/20241019-xtables-typos-v3-1-66dd2eaacf2f@0upti.… into stable. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231813] New: [riscv64][Unmatched][regression] Hard lockup on reboot/poweroff with 6.11
by bugzilla_noreply＠suse.com 19 Oct '24

19 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231813 Bug ID: 1231813 Summary: [riscv64][Unmatched][regression] Hard lockup on reboot/poweroff with 6.11 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: RISC-V OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: afaerber(a)suse.com QA Contact: qa-bugs(a)suse.de CC: ddavis(a)suse.com, jeffm(a)suse.com, schwab(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Reboot or poweroff on HiFive Unmatched board is no longer working at 20241016/17 (was working with 20240828; its 6.10.5 kernel with 20241017 does not help) and runs into a hard CPU lockup kernel panic: [ 56.329837][ T1379] sifive-serial 10010000.serial: BREAK detection not supported [ 57.664396][ T1] reboot: Power down [ 72.030230][ C3] watchdog: Watchdog detected hard LOCKUP on cpu 0 [ 96.026864][ C2] watchdog: Watchdog detected hard LOCKUP on cpu 3 [ 96.026873][ C2] Modules linked in: af_packet rfkill nf_tables libcrc32c snd_hda_codec_hdmi snd_hda_intel mscc snd_intel_dspcfg macsec snd_hda_codec nls_iso8859_1 nls_cp437 snd_hda_core vfat macb fat snd_hwdep phylink snd_pcm ofpart of_mdio snd_timer fixed_phy fwnode_mdio libphy snd spi_nor ptp at24 soundcore da9063_onkey pps_core mtd uio_pdrv_genirq uio fuse dm_mod nvme_fabrics nvme_keyring loop efi_pstore configfs nfnetlink dmi_sysfs ip_tables x_tables ext4 mbcache jbd2 xe hid_apple hid_generic usbhid apple_mfi_fastcharge xhci_pci mmc_block xhci_pci_renesas xhci_hcd drm_ttm_helper ttm i2c_algo_bit gpu_sched drm_buddy video drm_suballoc_helper drm_gpuvm mmc_spi crc_itu_t crc7 drm_exec of_mmc_spi usbcore drm_display_helper mmc_core rtc_da9063 da9063_regulator nvme cec lm90 da9063 mfd_core regmap_i2c rc_core nvme_core usb_common nvme_auth i2c_ocores pwm_sifive spi_sifive efivarfs [ 96.027165][ C2] Kernel panic - not syncing: Hard LOCKUP [ 96.027178][ C2] CPU: 2 UID: 0 PID: 0 Comm: swapper/2 Tainted: G U 6.11.3-1-default #1 openSUSE Tumbleweed 1400000003000000474e55005c3864d57907faa4 [ 96.027195][ C2] Tainted: [U]=USER [ 96.027198][ C2] Hardware name: sifive SiFive HiFive Unmatched A00/SiFive HiFive Unmatched A00, BIOS 2024.10 10/01/2024 [ 96.027204][ C2] Call Trace: [ 96.027211][ C2] [<ffffffff80006b4a>] dump_backtrace+0x1c/0x24 [ 96.027236][ C2] [<ffffffff80a00178>] show_stack+0x2c/0x38 [ 96.027251][ C2] [<ffffffff80a0cd7c>] dump_stack_lvl+0x50/0x72 [ 96.027270][ C2] [<ffffffff80a0cdb2>] dump_stack+0x14/0x1c [ 96.027279][ C2] [<ffffffff80a00410>] panic+0x106/0x312 [ 96.027288][ C2] [<ffffffff80022c0a>] add_taint+0x0/0x8c [ 96.027302][ C2] [<ffffffff80123204>] watchdog_hardlockup_check+0x170/0x1b4 [ 96.027322][ C2] [<ffffffff80123ca8>] watchdog_buddy_check_hardlockup+0x4c/0x5c [ 96.027334][ C2] [<ffffffff80122e98>] watchdog_timer_fn+0x70/0x238 [ 96.027344][ C2] [<ffffffff800d0540>] __hrtimer_run_queues+0xfe/0x240 [ 96.027364][ C2] [<ffffffff800d133a>] hrtimer_interrupt+0xca/0x1d6 [ 96.027374][ C2] [<ffffffff807b5e58>] riscv_timer_interrupt+0x3a/0x52 [ 96.027387][ C2] [<ffffffff800a1e0a>] handle_percpu_devid_irq+0x8a/0x1c0 [ 96.027403][ C2] [<ffffffff8009c6b0>] generic_handle_domain_irq+0x1c/0x2a [ 96.027423][ C2] [<ffffffff8055d908>] riscv_intc_irq+0x26/0x60 [ 96.027441][ C2] [<ffffffff80a0ce20>] handle_riscv_irq+0x4c/0x76 [ 96.027451][ C2] [<ffffffff80a1b106>] call_on_irq_stack+0x32/0x40 [ 96.788253][ C2] SMP: failed to stop secondary CPUs 0,2-3 [ 96.788264][ C2] Kernel Offset: 0x0 from 0xffffffff80000000 After some minutes it then reboots (also for poweroff). I've manually updated the two U-Boot partitions to latest Factory 2024.10, to no improvement. The taint is from xe.force_probe (bug #1231756); happens without as well. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1196835] [riscv64][Unmatched] CPU#0 stuck forever while trying to reboot the board.
by bugzilla_noreply＠suse.com 19 Oct '24

19 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1196835 Andreas Färber <afaerber(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.opensuse.o | |rg/show_bug.cgi?id=1231813 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1229020] Zypper dup installed kernels which reboot immediately
by bugzilla_noreply＠suse.com 19 Oct '24

19 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1229020 https://bugzilla.suse.com/show_bug.cgi?id=1229020#c10 Louis Erickson <wwonko(a)rdwarf.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(wwonko(a)rdwarf.com | |) | --- Comment #10 from Louis Erickson <wwonko(a)rdwarf.com> --- Created attachment 878105 --> https://bugzilla.suse.com/attachment.cgi?id=878105&action=edit Screenshot before reboot. Sorry about the delay. Travel and a case of COVID slowed me down. Back in the saddle now, and getting you that screenshot with quiet and splash disabled. The boot pauses here for a bit, then cold boots itself. -- 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 18 Oct '24

18 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1227144 https://bugzilla.suse.com/show_bug.cgi?id=1227144#c15 --- Comment #15 from Takashi Iwai <tiwai(a)suse.com> --- Then retest with the latest upstream kernel in OBS Kernel:stable:Backport repo again and see whether the issue appears with it or not. Honestly speaking, there is little thing we can do from the distro side for such a bug unless it's addressed in the upstream; it's a device-specific, mostly a firmware-related bug. -- 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 18 Oct '24

18 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1227144 https://bugzilla.suse.com/show_bug.cgi?id=1227144#c14 --- Comment #14 from Andreas <opendreas(a)gmail.com> --- Created attachment 878078 --> https://bugzilla.suse.com/attachment.cgi?id=878078&action=edit dmesg-6.4.0-150600.23.25-2 the errors started appearing again. Here is the log when the laptop came out of standby and, while watching YouTube, wifi began to reconnect. Now the laptop is frozen, I turned it off and on, after starting Firefox (Flatpak) from Youtube, the wifi starts to reconnect again. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189456] Add ashmem and binder drivers
by bugzilla_noreply＠suse.com 18 Oct '24

18 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1189456 https://bugzilla.suse.com/show_bug.cgi?id=1189456#c14 --- Comment #14 from Takashi Iwai <tiwai(a)suse.com> --- Not yet. Rust for Linux requires CONFIG_MODVERSION to be disabled, but it's a mandatory feature for (open)SUSE kernels, hence R4L can't be enabled. Once after it's addressed in the upstream, we might consider enabling Rust for Linux for Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 0

[Bug 1189456] Add ashmem and binder drivers
by bugzilla_noreply＠suse.com 17 Oct '24

17 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1189456 https://bugzilla.suse.com/show_bug.cgi?id=1189456#c13 llyyr <llyyr.public(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |llyyr.public(a)gmail.com --- Comment #13 from llyyr <llyyr.public(a)gmail.com> --- ashmem is not required anymore, since memfd exists now. And there's ongoing effort on a rust_binder driver to replace the old insecure binder driver. Will TW enable the rust_binder driver in the default kernel? -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.

1 0

[Bug 1229999] High idle power usage on Lenovo Slim 7 16" AMD
by bugzilla_noreply＠suse.com 17 Oct '24

17 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1229999 https://bugzilla.suse.com/show_bug.cgi?id=1229999#c11 --- Comment #11 from varval761 <variable_valuables761(a)simplelogin.com> --- I tested a few other distros, including Kubuntu and previous versions of Fedora and Tumbleweed, and they all had similar minimum idle power draw as the latest Tumbleweed/Krypton (25W+). So it seems so far that only recent Fedora versions have lower power draw (~14W). Does this maybe have any relevant info? https://fedoraproject.org/wiki/Changes/TunedAsTheDefaultPowerProfileManagem… (Fedora had less power draw even when replacing tuned with p-p-d or tlp though, in my previously mentioned tests) -- 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#c33 --- Comment #33 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Jiri Slaby from comment #32) > (In reply to Felix Niederwanger from comment #31) > > I forgot the KASAN sequence: > > > > > (poweroff) > > > 6.11.3-5-KASAN: error > > > 6.11.3-5-KASAN: error > > > 6.11.3-5-KASAN: error > > > > This kernel fails to boot from cold. FWIW I enabled kasan in my kernel, so that it contains both the workaround and KASAN: home:jirislaby:kernel-bsc1231465 It might be worth trying too. -- 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#c32 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(felix.niederwange | |r(a)suse.com) --- Comment #32 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Felix Niederwanger from comment #31) > I forgot the KASAN sequence: > > > (poweroff) > > 6.11.3-5-KASAN: error > > 6.11.3-5-KASAN: error > > 6.11.3-5-KASAN: error > > This kernel fails to boot from cold. It might die well due to the bug. Or not. Did you boot with "quiet" in cmdline? Can you see any messages if not? Or any chance it managed to store the kernel messages into the journal? Or would it be possible to boot with init=/bin/bash and look into the dmesg directly (I am not sure if it's not too late -- perhaps boot with rd.break, but that might be too late too)? But you at least confirmed 6.11.0 is ok and 6.11.2 is not. What about 6.12? And I've just pushed 6.11.4 -- still the same? Sorry, but I am not clever from this bug at all. -- 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#c48 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #48 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Guillaume GARDET from comment #47) > (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 Also affecting 15.5 and 15.6 again. Can you check the serial log? Maybe it's the same cause again, maybe something else. -- 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#c29 --- Comment #29 from Vlastimil Babka <vbabka(a)suse.com> --- Some parts of the following comment don't match the current theory for me. Is it because of imprecise wording or is something else happening? (In reply to Felix Niederwanger from comment #12) > Another observation: kernel 6.12.0-rc2-3.g4f5e31e-default only works on the > first boot. This part is ok. > When the machine is powered down, then also with this kernel the > machine only detects 1.3 GiB of memory. "powered down" would mean another cold boot? That wouldn't match the theory. If there was "rebooted", it would. > I powered the machine on this morning with the same kernel as Friday > (6.12.0-rc2-3.g4f5e31e) and run into the OOM issues. Running into the OOM issue immediately on cold boot doesn't match the theory? > I rolled back to the > 6.11.0-1 kernel and everything was fine. Then I re-installed the current > kernel:HEAD (now 6.12.0-rc3-1gefb99), rebooted and the system was running > fine with 32 GiB. This means here 6.11.0 would not corrupt EFI memory if a reboot from that to 6.12.0 was fine? > Then I powered off the laptop and the same kernel then > detected only 1.3 GiB of memory. I rebooted 3 times with this kernel, always > 1.3 GiB. Again if it's "powered off" the first boot should have been ok? > I used then an older snapshot with the 6.11.0-1 kernel and everything was > fine again (32 GiB memory). From there rebooting into the 6.12.0-rc3 kernel > only shows again 1.3 GiB of memory. But here it seems 6.11.0 is corrupting the EFI memory, so it's a different result than above? Maybe the corruption is not completely deterministic? -- 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#c28 --- Comment #28 from Vlastimil Babka <vbabka(a)suse.com> --- (In reply to Felix Niederwanger from comment #12) > I used then an older snapshot with the 6.11.0-1 kernel and everything was > fine again (32 GiB memory). From there rebooting into the 6.12.0-rc3 kernel > only shows again 1.3 GiB of memory. This suggests 6.11.0 itself already was corrupting the EFI memory? -- 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#c27 --- Comment #27 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Jiri Slaby from comment #26) > (In reply to Felix Niederwanger from comment #20) > > To cross-check I needed 2 reboot attempts with the 6.11.2 kernel to end up > > with only 1.3 GiB. > > Side note: you have to boot each tested kernel twice to actually *see* the > behavior. The first boot corrupts the EFI memory, the second one loads the > memory. And cold-boot/shutdown in between to reset to the original BIOS/EFI state. > Having that in mind, you still confirm 6.12 is fine, 6.11 is fine, but > 6.11.2 is not? -- 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#c26 --- Comment #26 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Felix Niederwanger from comment #20) > To cross-check I needed 2 reboot attempts with the 6.11.2 kernel to end up > with only 1.3 GiB. Side note: you have to boot each tested kernel twice to actually *see* the behavior. The first boot corrupts the EFI memory, the second one loads the memory. Having that in mind, you still confirm 6.12 is fine, 6.11 is fine, but 6.11.2 is not? -- You are receiving this mail because: You are the assignee for the bug.

1 0