July 2024 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1211761] New: vtty[1-6] nouveau framebuffers produce vast snow/raster on right and bottom border areas on the larger resolution of two displays, in the absence of both plymouth and video= on linu lines
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1211761 Bug ID: 1211761 Summary: vtty[1-6] nouveau framebuffers produce vast snow/raster on right and bottom border areas on the larger resolution of two displays, in the absence of both plymouth and video= on linu lines Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 URL: https://bugzilla.kernel.org/show_bug.cgi?id=217479 ; https://gitlab.freedesktop.org/drm/nouveau/-/issues/21 4 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: mrmazda(a)earthlink.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Original Summary: vtty[1-6] nouveau framebuffers produce vast snow/raster on right and bottom border areas on the larger resolution of two displays, in the absence of both plymouth and video= on linu lines FTR: Upstream bugs: https://bugzilla.kernel.org/show_bug.cgi?id=217479 (includes most detail, w/ dmesg) https://gitlab.freedesktop.org/drm/nouveau/-/issues/214 To reproduce: 1-connect two unequal native resolution displays to a Tesla or Firmi GPU 2-don't have plymouth in use (I don't ever have it installed, so don't know whether it impacts) 3-don't include e.g. video=1440x900@60 directive on Grub's linu lines 4-boot TW 5-switch to a vtty, e.g. Ctrl-Alt-F3 Actual behavior: 1-Both displays utilize the resolution (same pixel grid) of the lower resolution display 2-Lower resolution display behaves as expected (light text on black background) 3-Higher resolution display uses same pixels as lower resolution display, with light text on black background, leaving right side and bottom raster instead of black Expected behavior: 1-Both displays utilize the resolution (same pixel grid) of the lower resolution display 2-Lower resolution display behaves as expected 3-Entire higher resolution display's background is black instead of portions in raster Workaround: add e.g. video=1440x900@60 to Grub's linu lines, which causes both displays to use the same nominal mode on the full display space. Occurs with TW 6.3.2, 6.2.12 & 6.2.4 kernel-default, and with 6.2.15 on Fedora 38 and Mageia 9. Does not occur with TW 6.1.12 kernel-default on NVidia, or with AMD Caicos (Terascale2) GPU, or with Intel Eaglelake GPU. Tested only on legacy booting (no UEFI support). Others might describe what I call "raster" as multicolored snow. nosimplefb=1 doesn't change anything. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1227749] New: Orange PI 5 Plus limited functionality
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1227749 Bug ID: 1227749 Summary: Orange PI 5 Plus limited functionality Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: aaron.w2(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 876046 --> https://bugzilla.suse.com/attachment.cgi?id=876046&action=edit idbloader for Orange PI 5 Plus I managed to get U-Boot running on the Orange PI 5 Plus with a couple of key SUSE patches to the point where it is booting into OpenSUSE AARCH64 Rockchip version. Currently only the following are working: - PCIe - NVME - eMMC/SD - Serial port The following are not working: - USB - Realtek RTL8125 2.5G Ethernet drivers (seen on PCIe bus) - Realtek RTL8852BE (seen on PCIe bus, not driver seems to be available) Note that in U-Boot that USB also does not work and the network cards are not supported (as of 7/15). I am attaching my U-Boot and idbloader for this board which should allow it to boot, use the usual offset 64 for the idbloader and offset 16384 for U-Boot. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1222902] New: Monitor detection fails after hard reset
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1222902 Bug ID: 1222902 Summary: Monitor detection fails after hard reset 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: david.mulder(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After a hard reset (laptop locked up when I tried to suspend it), my external monitors are no longer detected. I've seen this happen 3 times in as many weeks (on several recent versions of TW), and the only solution I've found is reinstalling TW. > sudo hwinfo --monitor 45: None 00.0: 10002 LCD Monitor [Created at monitor.125] Unique ID: rdCR.iVNqLoWlvi7 Parent ID: _Znp.TcrQYGYoBS2 Hardware Class: monitor Model: "BOE CQ LCD Monitor" Vendor: BOE "BOE CQ" Device: eisa 0x0a7d Serial ID: "0" Resolution: 1920x1200@60Hz Size: 345x215 mm Year of Manufacture: 2021 Week of Manufacture: 27 Detailed Timings #0: Resolution: 1920x1200 Horizontal: 1920 1968 2000 2140 (+48 +80 +220) -hsync Vertical: 1200 1203 1209 1260 (+3 +9 +60) +vsync Frequencies: 161.79 MHz, 75.60 kHz, 60.00 Hz Driver Info #0: Max. Resolution: 1920x1200 Vert. Sync Range: 40-60 Hz Hor. Sync Range: 76-76 kHz Bandwidth: 161 MHz Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #39 (VGA compatible controller) -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1219522] New: Kernel panic with 6.7.x version
by bugzilla_noreply＠suse.com 30 Dec '24

30 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1219522 Bug ID: 1219522 Summary: Kernel panic with 6.7.x version Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: e.kleinmentink(a)zonnet.nl QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 872422 --> https://bugzilla.suse.com/attachment.cgi?id=872422&action=edit dmesg 6.6.11-1 kernel I get a kernel panic since the 6.7.x kernels. The capslock key is flickering and if i use the "recovery mode" i usually see: [T8] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.16, id: 0x1e2b1, caps: 0xf01fa3/0x940300/0x12e800/0x400000, board id: 3276, fw id: 2700068 [T8] psmouse serio1: synaptics: serio: Synaptics pass-through port at isa0060/serio1/input0 [T8] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input2 I have no idea how to debug this. No error message. In the past i applied a kernel bisect (for debian i think) but i could not find a guide for Tumbleweed. Hardware: Lenovo T580 Grub menu contains: * 6.7.2-1 * 6.7.1-2 * 6.6.11-1 Included a "dmesg" output of a normal boot with the "6.6.11-1" kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 25

[Bug 1220119] New: Some tests on o3 triggers dmesg "clocksource: timekeeping watchdog on CPU0: Marking clocksource 'tsc' as unstable because the skew is too large:"
by bugzilla_noreply＠suse.com 27 Dec '24

27 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1220119 Bug ID: 1220119 Summary: Some tests on o3 triggers dmesg "clocksource: timekeeping watchdog on CPU0: Marking clocksource 'tsc' as unstable because the skew is too large:" 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: petr.vorel(a)suse.com QA Contact: qa-bugs(a)suse.de CC: jwiesner(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Some tests running on o3 (openQA instance on https://openqa.opensuse.org/) triggers in dmesg. All tests run in VM via qemu. This is on x86_64 on my private openQA worker by ltp_net_tcp_cmds, triggered for 2 tests: arp and host (both tests did not fail): OpenQA::run_ltp.pm: Starting ipneigh01_arp [ 410.818828][ C0] clocksource: timekeeping watchdog on CPU0: Marking clocksource 'tsc' as unstable because the skew is too large: [ 410.820365][ C0] clocksource: 'kvm-clock' wd_nsec: 506724586 wd_now: 610448443a wd_last: 60e6144350 mask: ffffffffffffffff [ 410.821824][ C0] clocksource: 'tsc' cs_nsec: 49302930542 cs_now: 17c1364ba0a cs_last: 153fdc32526 mask: ffffffffffffffff [ 410.823293][ C0] clocksource: Clocksource 'tsc' skewed 48796205956 ns (48796 ms) over watchdog 'kvm-clock' interval of 506724586 ns (506 ms) [ 410.824843][ C0] clocksource: 'kvm-clock' (not 'tsc') is current clocksource. [ 410.825707][ C0] tsc: Marking TSC unstable due to clocksource watchdog [ 411.109710][T28135] Initializing XFRM netlink socket OpenQA::run_ltp.pm: Starting ipneigh01_ip OpenQA::run_ltp.pm: Starting arping01 OpenQA::run_ltp.pm: Starting clockdiff01 OpenQA::run_ltp.pm: Starting ftp OpenQA::run_ltp.pm: Starting host [ 410.818845][ C0] clocksource: timekeeping watchdog on CPU0: Marking clocksource 'tsc' as unstable because the skew is too large: [ 410.820687][ C0] clocksource: 'kvm-clock' wd_nsec: 506741379 wd_now: 61044885d3 wd_last: 60e6144350 mask: ffffffffffffffff [ 410.821794][ C0] clocksource: 'tsc' cs_nsec: 804834172 cs_now: 154a546a082 cs_last: 153fdc32526 mask: ffffffffffffffff [ 410.822919][ C0] clocksource: Clocksource 'tsc' skewed 298092793 ns (298 ms) over watchdog 'kvm-clock' interval of 506741379 ns (506 ms) [ 410.824088][ C0] clocksource: 'kvm-clock' (not 'tsc') is current clocksource. [ 410.824768][ C0] tsc: Marking TSC unstable due to clocksource watchdog [ 411.126759][T28138] Initializing XFRM netlink socket Also, originally I noted this on ltp_net_tcp_cmds running on ppc64le on o3 (kernel tests in https://openqa.opensuse.org/group_overview/32) where host test keeps failing (but arp test is working), I don't see it on ltp_net_tcp_cmds on x86_64 on o3. I was not able to trigger this on VM on my laptop (x86_64). Others found that systemd-networkd test on Tumbleweed on x86_64 (https://openqa.opensuse.org/group_overview/1) [ 570.754611][ C0] Showing busy workqueues and worker pools: [ 570.755654][ C0] workqueue events: flags=0x0 [ 570.756580][ C0] pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=1/256 refcnt=2 [ 570.756586][ C0] pending: drm_fb_helper_damage_work [ 570.759551][ C0] sysrq: Show Blocked State zDBFr-0- [ 311.682306][ C0] clocksource: timekeeping watchdog on CPU0: Marking clocksource 'tsc' as unstable because the skew is too large: [ 311.684482][ C0] clocksource: 'kvm-clock' wd_nsec: 621509306 wd_now: 49d9caac63 wd_last: 49b4bf31a9 mask: ffffffffffffffff [ 311.686513][ C0] clocksource: 'tsc' cs_nsec: 952336665 cs_now: a3a422af12 cs_last: a327415f8e mask: ffffffffffffffff [ 311.688559][ C0] clocksource: Clocksource 'tsc' skewed 330827359 ns (330 ms) over watchdog 'kvm-clock' interval of 621509306 ns (621 ms) [ 311.690452][ C0] clocksource: 'kvm-clock' (not 'tsc') is current clocksource. [ 311.691559][ C0] tsc: Marking TSC unstable due to clocksource watchdog Test runs also on aarch64, but error is not there. Is it a problem of openQA setup? There are other bugs. -- You are receiving this mail because: You are the assignee for the bug.

1 37

[Bug 1212877] New: [RPi4] cannot wake up after suspend triggered
by bugzilla_noreply＠suse.com 17 Dec '24

17 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1212877 Bug ID: 1212877 Summary: [RPi4] cannot wake up after suspend triggered Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: zluo(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 867900 --> https://bugzilla.suse.com/attachment.cgi?id=867900&action=edit yast2 logs ssh to my RPi 4 Model B, later I see following -- p200300ea3707b36b055205817bcf9853:~ # Broadcast message from root@localhost (Fri 2023-06-30 06:03:37 UTC): The system will suspend now! -- then I try to wake it up by hitting keyboard and click on mouse, nothing happened on screen. attache yast2logs. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1215927] New: kernel-default-6.5.4 reboots instead of resuming from suspend
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1215927 Bug ID: 1215927 Summary: kernel-default-6.5.4 reboots instead of resuming from suspend Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: psychonaut(a)nothingisreal.com QA Contact: qa-bugs(a)suse.de CC: mrmazda(a)earthlink.net Target Milestone: --- Found By: --- Blocker: --- I upgraded from Tumbleweed 20230908 to 20230921, which included an upgrade from kernel-default-6.4.12 to kernel-default-6.5.4. I always suspend my computer at night (with systemctl suspend) and wake it the next morning. With the new kernel, the computer always restarts instead of resuming from suspend. The problem does not occur with the old kernel. Interestingly, the problem is reproducible only when I leave the computer suspended overnight. Simply suspending the computer and then waking it a few seconds later does not trigger the bug. hwinfo output (with the old kernel) is available in Attachment 869836 of Bug 1215826. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1219137] New: qemu user space builds broken with kernel 6.7
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1219137 Bug ID: 1219137 Summary: qemu user space builds broken with kernel 6.7 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: schwab(a)suse.de QA Contact: qa-bugs(a)suse.de CC: adrian.schroeter(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Since commit 1c5976ef0f7a the kernel deregisters all binfmt_misc handler when the binfmt_misc filesystem is unmounted. The build script has this: # RPM specific post checks are in /usr/lib/build/checks if test -n "$RPMS" -a -d "$BUILD_ROOT/usr/lib/build/checks" ; then # workaround for broken 13.1 check scripts which umount /proc if test -n "$RUNNING_IN_VM" -a "$BUILD_ROOT" = / ; then umount -n $BUILD_ROOT/proc/sys/fs/binfmt_misc 2>/dev/null fi This means that after this point the emulation no longer works. [ 272s] ... checking for files with abuild user/group [ 272s] /.build/build: line 1922: /bin/env: cannot execute binary file: Exec format error [ 272s] /.build/build: line 1926: /bin/rpm: cannot execute binary file: Exec format error [ 272s] /.build/build: line 1926: /bin/rpm: cannot execute binary file: Exec format error [ 272s] /.build/build: line 1926: /bin/rpm: cannot execute binary file: Exec format error [ 272s] /.build/build: line 1926: /bin/rpm: cannot execute binary file: Exec format error [ 272s] /.build/build: line 1926: /bin/rpm: cannot execute binary file: Exec format error [ 272s] /.build/build: line 1926: /bin/rpm: cannot execute binary file: Exec format error [ 272s] /.build/build: line 1926: /bin/rpm: cannot execute binary file: Exec format error [ 272s] /.build/build: line 1926: /bin/rpm: cannot execute binary file: Exec format error [ 272s] /.build/build: line 1926: /bin/rpm: cannot execute binary file: Exec format error [ 272s] /.build/build: line 1926: /bin/rpm: cannot execute binary file: Exec format error According to the commit, this should be reported as a regression so that this behaviour is reverted for the initial binfmt_misc mount. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1217314] New: [LenovoX13s] Unable to boot from USB
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1217314 Bug ID: 1217314 Summary: [LenovoX13s] Unable to boot from USB Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de CC: chester.lin(a)suse.com Target Milestone: --- Found By: --- Blocker: --- On the Lenovo X13s laptop, we are able to boot DVD ISO from USB and install openSUSE Tumbleweed on a 2nd USB stick, but on reboot, the system hangs after grub loaded kernel+initrd. Live images and JeOS images are not able to boot from USB either. Fedora wiki suggests to blacklist 'modprobe.blacklist=qcom_q6v5_pas' to keep the USB from being reset/renamed. [0] But this does not work in my tests. [0]: https://fedoraproject.org/wiki/Thinkpad_X13s#Rawhide_hacking -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1214969] New: r8169: transmit queue 0 timed out
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1214969 Bug ID: 1214969 Summary: r8169: transmit queue 0 timed out Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jbaier(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I hit a possible regression in kernel 6.4.x, it seems to me that this is a very similar (or same) issue like bsc#1106833 and similar. After some time (depending on the network usage, usually within 24 hours) the kernel panic happens and the network interface becomes unusable (in fact it probably generates some nonsense on the line as it also takes down the whole network segment). This behavior can be observed in 6.4.3-1-default, 6.4.6-1-default, 6.4.9-1-default and now in 6.4.11-1-default. The issue is not happening in 6.3.9-1-default which I am using right now as a workaround. --- zář 04 21:39:12 valiant kernel: ------------[ cut here ]------------ zář 04 21:39:12 valiant kernel: NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 timed out 8160 ms zář 04 21:39:12 valiant kernel: WARNING: CPU: 11 PID: 0 at net/sched/sch_generic.c:525 dev_watchdog+0x21e/0x230 zář 04 21:39:12 valiant kernel: Modules linked in: tun rfcomm snd_seq_dummy snd_hrtimer snd_seq snd_seq_device af_packet vboxnetadp(O) vboxnetflt(O) vboxdrv(O) cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 nls_cp437 vfat fat snd_sof_amd_rembrandt snd_sof_amd_renoir snd_sof_amd_acp snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_hda_codec_realtek snd_sof_utils snd_hda_codec_generic mt7921e snd_hda_codec_hdmi snd_soc_core mt7921_common mt76_connac_lib snd_compress intel_rapl_msr btusb mt76 snd_hda_intel snd_pcm_dmaengine intel_rapl_common btrtl snd_intel_dspcfg btbcm snd_intel_sdw_acpi snd_pci_ps btintel edac_mce_amd snd_hda_codec btmtk asus_nb_wmi eeepc_wmi mac80211 asus_wmi snd_rpl_pci_acp6x r8169 snd_hda_core snd_acp_pci battery snd_pci_acp6x kvm_amd snd_hwdep ledtrig_audio bluetooth snd_pcm libarc4 snd_pci_acp5x sparse_keymap realtek kvm joydev ecdh_generic platform_profile snd_rn_pci_acp3x snd_timer snd_acp_config mdio_devres irqbypass wmi_bmof cfg80211 pcspkr snd acpi_cpufreq snd_soc_acpi tiny_power_button efi_pstore soundcore zář 04 21:39:12 valiant kernel: k10temp libphy i2c_piix4 snd_pci_acp3x rfkill serial_multi_instantiate button fuse configfs dmi_sysfs ip_tables x_tables hid_generic usbhid dm_crypt essiv authenc trusted asn1_encoder tee amdgpu crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic gf128mul ghash_clmulni_intel sha512_ssse3 i2c_algo_bit drm_ttm_helper ttm drm_suballoc_helper iommu_v2 drm_buddy xhci_pci xhci_pci_renesas gpu_sched xhci_hcd aesni_intel drm_display_helper nvme crypto_simd ucsi_acpi usbcore cryptd typec_ucsi cec nvme_core roles ccp rc_core sp5100_tco typec video wmi btrfs blake2b_generic libcrc32c crc32c_intel xor raid6_pq sg br_netfilter bridge stp llc dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua msr efivarfs zář 04 21:39:12 valiant kernel: CPU: 11 PID: 0 Comm: swapper/11 Tainted: G O 6.4.11-1-default #1 openSUSE Tumbleweed b71e9da2e7bdf20ad15c36d48af8b3d0ec2bfcc0 zář 04 21:39:12 valiant kernel: Hardware name: ASUSTeK COMPUTER INC. MINIPC PN52/PN52, BIOS 11800 09/07/2022 zář 04 21:39:12 valiant kernel: RIP: 0010:dev_watchdog+0x21e/0x230 zář 04 21:39:12 valiant kernel: Code: ff ff ff 48 89 df c6 05 ba 31 5d 01 01 e8 fa 38 fa ff 45 89 f8 44 89 f1 48 89 de 48 89 c2 48 c7 c7 70 16 cb a6 e8 12 d9 5e ff <0f> 0b e9 2d ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 90 90 90 90 zář 04 21:39:12 valiant kernel: RSP: 0018:ffffb3a180438ea0 EFLAGS: 00010282 zář 04 21:39:12 valiant kernel: RAX: 0000000000000000 RBX: ffff942ec3f90000 RCX: 0000000000000000 zář 04 21:39:12 valiant kernel: RDX: ffff943af5db4528 RSI: ffff943af5da74c0 RDI: 0000000000000300 zář 04 21:39:12 valiant kernel: RBP: ffff942ec3f904c8 R08: 0000000000000000 R09: ffffb3a180438d48 zář 04 21:39:12 valiant kernel: R10: 0000000000000003 R11: ffff943b2e0fcfe8 R12: ffff942e08ca6000 zář 04 21:39:12 valiant kernel: R13: ffff942ec3f9041c R14: 0000000000000000 R15: 0000000000001fe0 zář 04 21:39:12 valiant kernel: FS: 0000000000000000(0000) GS:ffff943af5d80000(0000) knlGS:0000000000000000 zář 04 21:39:12 valiant kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 zář 04 21:39:12 valiant kernel: CR2: 00007f1ff7fec980 CR3: 00000000bbc36000 CR4: 0000000000750ee0 zář 04 21:39:12 valiant kernel: PKRU: 55555554 zář 04 21:39:12 valiant kernel: Call Trace: zář 04 21:39:12 valiant kernel: <IRQ> zář 04 21:39:12 valiant kernel: ? dev_watchdog+0x21e/0x230 zář 04 21:39:12 valiant kernel: ? __warn+0x81/0x130 zář 04 21:39:12 valiant kernel: ? dev_watchdog+0x21e/0x230 zář 04 21:39:12 valiant kernel: ? report_bug+0x171/0x1a0 zář 04 21:39:12 valiant kernel: ? handle_bug+0x3c/0x80 zář 04 21:39:12 valiant kernel: ? exc_invalid_op+0x17/0x70 zář 04 21:39:12 valiant kernel: ? asm_exc_invalid_op+0x1a/0x20 zář 04 21:39:12 valiant kernel: ? dev_watchdog+0x21e/0x230 zář 04 21:39:12 valiant kernel: ? __pfx_dev_watchdog+0x10/0x10 zář 04 21:39:12 valiant kernel: ? __pfx_dev_watchdog+0x10/0x10 zář 04 21:39:12 valiant kernel: call_timer_fn+0x27/0x130 zář 04 21:39:12 valiant kernel: __run_timers.part.0+0x1d8/0x280 zář 04 21:39:12 valiant kernel: ? __x86_return_thunk+0x9/0x10 zář 04 21:39:12 valiant kernel: ? __x86_return_thunk+0x9/0x10 zář 04 21:39:12 valiant kernel: ? ktime_get+0x3c/0xa0 zář 04 21:39:12 valiant kernel: ? __x86_return_thunk+0x9/0x10 zář 04 21:39:12 valiant kernel: run_timer_softirq+0x2a/0x50 zář 04 21:39:12 valiant kernel: __do_softirq+0xca/0x2a5 zář 04 21:39:12 valiant kernel: __irq_exit_rcu+0xae/0xe0 zář 04 21:39:12 valiant kernel: sysvec_apic_timer_interrupt+0x72/0x90 zář 04 21:39:12 valiant kernel: </IRQ> zář 04 21:39:12 valiant kernel: <TASK> zář 04 21:39:12 valiant kernel: asm_sysvec_apic_timer_interrupt+0x1a/0x20 zář 04 21:39:12 valiant kernel: RIP: 0010:cpuidle_enter_state+0xcc/0x440 zář 04 21:39:12 valiant kernel: Code: 2a ea 47 ff e8 d5 f1 ff ff 8b 53 04 49 89 c5 0f 1f 44 00 00 31 ff e8 b3 f6 46 ff 45 84 ff 0f 85 56 02 00 00 fb 0f 1f 44 00 00 <45> 85 f6 0f 88 85 01 00 00 49 63 d6 48 8d 04 52 48 8d 04 82 49 8d zář 04 21:39:12 valiant kernel: RSP: 0018:ffffb3a1801d7e90 EFLAGS: 00000246 zář 04 21:39:12 valiant kernel: RAX: ffff943af5dba080 RBX: ffff942e08d7bc00 RCX: 000000000000045a zář 04 21:39:12 valiant kernel: RDX: 000000000000000b RSI: 000011088cb991b0 RDI: 0000000000000000 zář 04 21:39:12 valiant kernel: RBP: 0000000000000003 R08: ffffffffffcd2371 R09: 000000002690b399 zář 04 21:39:12 valiant kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffffffffa7632be0 zář 04 21:39:12 valiant kernel: R13: 000011088cb991b0 R14: 0000000000000003 R15: 0000000000000000 zář 04 21:39:12 valiant kernel: cpuidle_enter+0x2d/0x40 zář 04 21:39:12 valiant kernel: do_idle+0x20d/0x270 zář 04 21:39:12 valiant kernel: cpu_startup_entry+0x1d/0x20 zář 04 21:39:12 valiant kernel: start_secondary+0x12e/0x150 zář 04 21:39:12 valiant kernel: secondary_startup_64_no_verify+0x10b/0x10b zář 04 21:39:12 valiant kernel: </TASK> zář 04 21:39:12 valiant kernel: ---[ end trace 0000000000000000 ]--- --- 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05) Subsystem: ASUSTeK Computer Inc. Device 87d7 Flags: bus master, fast devsel, latency 0, IRQ 36, IOMMU group 12 I/O ports at f000 [size=256] Memory at fce00000 (64-bit, non-prefetchable) [size=64K] Memory at fce10000 (64-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+ Capabilities: [70] Express Endpoint, MSI 01 Capabilities: [b0] MSI-X: Enable+ Count=32 Masked- Capabilities: [d0] Vital Product Data Capabilities: [100] Advanced Error Reporting Capabilities: [148] Virtual Channel Capabilities: [168] Device Serial Number 01-00-00-00-68-4c-e0-00 Capabilities: [178] Transaction Processing Hints Capabilities: [204] Latency Tolerance Reporting Capabilities: [20c] L1 PM Substates Capabilities: [21c] Vendor Specific Information: ID=0002 Rev=4 Len=100 <?> Kernel driver in use: r8169 Kernel modules: r8169 -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1215251] New: BTRFS: transaction aborted, forced readonly
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1215251 Bug ID: 1215251 Summary: BTRFS: transaction aborted, forced readonly Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: lmb(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- My laptop hit this today (latest TW): Sep 12 11:26:53 hermes.in-addr.de kernel: ------------[ cut here ]------------ Sep 12 11:26:53 hermes.in-addr.de kernel: BTRFS: Transaction aborted (error -17) Sep 12 11:26:53 hermes.in-addr.de kernel: WARNING: CPU: 3 PID: 1289 at fs/btrfs/delayed-inode.c:1158 __btrfs_run_delayed_items+0x27d/0x290 [btrfs] Sep 12 11:26:53 hermes.in-addr.de kernel: Modules linked in: tun ccm michael_mic snd_seq_dummy snd_hrtimer snd_seq af_packet algif_hash af_alg r8153_ecm cdc_ether usbnet r8152 mii snd_usb_audio snd_usbmidi_lib snd_rawmidi snd_seq_device nft_masq nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nf_log_syslog nft_log nft_ct nft_chain_nat iscsi_ibft iscsi_boot_sysfs 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 cdc_acm ip_set nfnetlink ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter qrtr_mhi uvcvideo videobuf2_vmalloc uvc videobuf2_memops videobuf2_v4l2 videobuf2_common bnep binfmt_misc snd_ctl_led snd_soc_skl_hda_dsp snd_soc_intel_hda_dsp_common snd_soc_hdac_hdmi snd_sof_probes snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_soc_dmic snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel Sep 12 11:26:53 hermes.in-addr.de kernel: soundwire_cadence snd_sof_intel_hda_mlink snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda nls_iso8859_1 snd_hda_ext_core snd_soc_acpi_intel_match nls_cp437 snd_soc_acpi soundwire_generic_allocation soundwire_bus vfat xxhash_generic fat snd_soc_core qrtr snd_compress snd_pcm_dmaengine ath11k_pci hid_multitouch ath11k spi_nor snd_hda_intel iTCO_wdt snd_intel_dspcfg snd_intel_sdw_acpi mtd x86_pkg_temp_thermal intel_pmc_bxt intel_powerclamp iTCO_vendor_support qmi_helpers mei_pxp snd_hda_codec dell_laptop coretemp pmt_telemetry mei_hdcp kvm_intel snd_hda_core intel_rapl_msr pmt_class dell_smm_hwmon snd_hwdep hci_uart mac80211 btqca dell_wmi snd_pcm kvm btrtl btbcm snd_timer dell_smbios pcspkr efi_pstore btintel irqbypass dcdbas libarc4 dell_wmi_ddv cfg80211 bluetooth dell_wmi_sysman ledtrig_audio dell_wmi_descriptor firmware_attributes_class wmi_bmof snd processor_thermal_device_pci_legacy i2c_i801 spi_intel_pci processor_thermal_device hid_sensor_als spi_intel Sep 12 11:26:53 hermes.in-addr.de kernel: i2c_smbus mhi soundcore hid_sensor_trigger tiny_power_button processor_thermal_rfim mei_me hid_sensor_iio_common processor_thermal_mbox industrialio_triggered_buffer processor_thermal_rapl kfifo_buf thunderbolt mei intel_rapl_common industrialio intel_lpss_pci ecdh_generic intel_vsec intel_lpss intel_soc_dts_iosf igen6_edac idma64 int3403_thermal button rfkill int340x_thermal_zone intel_skl_int3472_tps68470 intel_hid tps68470_regulator intel_skl_int3472_discrete int3400_thermal sparse_keymap acpi_thermal_rel intel_pmc_core acpi_tad ac acpi_pad joydev nfsd auth_rpcgss nfs_acl lockd grace sunrpc fuse configfs dmi_sysfs ip_tables x_tables dm_crypt essiv authenc trusted asn1_encoder tee uas usb_storage hid_logitech_hidpp hid_logitech_dj typec_displayport usbhid hid_sensor_hub hid_generic intel_ishtp_hid nvme nvme_core i915 crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic gf128mul ghash_clmulni_intel sha512_ssse3 i2c_algo_bit drm_buddy drm_display_helper rtsx_pci_sdmmc xhci_pci xhci_pci_renesas Sep 12 11:26:53 hermes.in-addr.de kernel: mmc_core cec xhci_hcd rc_core aesni_intel ucsi_acpi typec_ucsi intel_ish_ipc crypto_simd cryptd usbcore roles rtsx_pci intel_ishtp vmd ttm typec video battery i2c_hid_acpi i2c_hid wmi pinctrl_tigerlake serio_raw btrfs blake2b_generic libcrc32c crc32c_intel xor raid6_pq dm_mirror dm_region_hash dm_log v4l2loopback(O) videodev mc sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua br_netfilter bridge stp llc msr efivarfs Sep 12 11:26:53 hermes.in-addr.de kernel: Unloaded tainted modules: bbswitch(O):2 Sep 12 11:26:53 hermes.in-addr.de kernel: CPU: 3 PID: 1289 Comm: btrfs-transacti Tainted: G O 6.4.12-1-default #1 openSUSE Tumbleweed 90d5a85b7d5cd5540ea49c35d1d7246e55e75794 Sep 12 11:26:53 hermes.in-addr.de kernel: Hardware name: Dell Inc. XPS 13 9310/0F7M4C, BIOS 3.17.0 07/12/2023 Sep 12 11:26:53 hermes.in-addr.de kernel: RIP: 0010:__btrfs_run_delayed_items+0x27d/0x290 [btrfs] Sep 12 11:26:53 hermes.in-addr.de kernel: Code: e9 49 fe ff ff 49 8b 7c 24 50 44 89 fa 48 c7 c6 50 f7 7a c0 e8 c4 73 04 00 eb ac 44 89 fe 48 c7 c7 20 f7 7a c0 e8 73 64 ff f9 <0f> 0b eb 99 41 bf f4 ff ff ff e9 f0 fe ff ff 0f 1f 40 00 90 90 90 Sep 12 11:26:53 hermes.in-addr.de kernel: RSP: 0018:ffffbbb60212be18 EFLAGS: 00010286 Sep 12 11:26:53 hermes.in-addr.de kernel: RAX: 0000000000000000 RBX: ffff95de205f2918 RCX: 0000000000000027 Sep 12 11:26:53 hermes.in-addr.de kernel: RDX: ffff95e32f5a74c8 RSI: 0000000000000001 RDI: ffff95e32f5a74c0 Sep 12 11:26:53 hermes.in-addr.de kernel: RBP: ffff95de205f28c0 R08: 0000000000000000 R09: ffffbbb60212bcc0 Sep 12 11:26:53 hermes.in-addr.de kernel: R10: 0000000000000003 R11: ffff95e34f7401e8 R12: ffff95dbf8902a90 Sep 12 11:26:53 hermes.in-addr.de kernel: R13: ffff95de778c1850 R14: ffff95dc00467800 R15: 00000000ffffffef Sep 12 11:26:53 hermes.in-addr.de kernel: FS: 0000000000000000(0000) GS:ffff95e32f580000(0000) knlGS:0000000000000000 Sep 12 11:26:53 hermes.in-addr.de kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 12 11:26:53 hermes.in-addr.de kernel: CR2: 00007f3e63a04960 CR3: 00000001796c4001 CR4: 0000000000f70ee0 Sep 12 11:26:53 hermes.in-addr.de kernel: PKRU: 55555554 Sep 12 11:26:53 hermes.in-addr.de kernel: Call Trace: Sep 12 11:26:53 hermes.in-addr.de kernel: <TASK> Sep 12 11:26:53 hermes.in-addr.de kernel: ? __btrfs_run_delayed_items+0x27d/0x290 [btrfs 0cfc88295dbffd2ce4d9688602336acd1498cf39] Sep 12 11:26:53 hermes.in-addr.de kernel: ? __warn+0x81/0x130 Sep 12 11:26:53 hermes.in-addr.de kernel: ? __btrfs_run_delayed_items+0x27d/0x290 [btrfs 0cfc88295dbffd2ce4d9688602336acd1498cf39] Sep 12 11:26:53 hermes.in-addr.de kernel: ? report_bug+0x171/0x1a0 Sep 12 11:26:53 hermes.in-addr.de kernel: ? handle_bug+0x3c/0x80 Sep 12 11:26:53 hermes.in-addr.de kernel: ? exc_invalid_op+0x17/0x70 Sep 12 11:26:53 hermes.in-addr.de kernel: ? asm_exc_invalid_op+0x1a/0x20 Sep 12 11:26:53 hermes.in-addr.de kernel: ? __btrfs_run_delayed_items+0x27d/0x290 [btrfs 0cfc88295dbffd2ce4d9688602336acd1498cf39] Sep 12 11:26:53 hermes.in-addr.de kernel: ? __btrfs_run_delayed_items+0x27d/0x290 [btrfs 0cfc88295dbffd2ce4d9688602336acd1498cf39] Sep 12 11:26:53 hermes.in-addr.de kernel: btrfs_commit_transaction+0x15f/0xe90 [btrfs 0cfc88295dbffd2ce4d9688602336acd1498cf39] Sep 12 11:26:53 hermes.in-addr.de kernel: ? start_transaction+0xc5/0x5d0 [btrfs 0cfc88295dbffd2ce4d9688602336acd1498cf39] Sep 12 11:26:53 hermes.in-addr.de kernel: transaction_kthread+0x141/0x1b0 [btrfs 0cfc88295dbffd2ce4d9688602336acd1498cf39] Sep 12 11:26:53 hermes.in-addr.de kernel: ? __pfx_transaction_kthread+0x10/0x10 [btrfs 0cfc88295dbffd2ce4d9688602336acd1498cf39] Sep 12 11:26:53 hermes.in-addr.de kernel: kthread+0xe5/0x120 Sep 12 11:26:53 hermes.in-addr.de kernel: ? __pfx_kthread+0x10/0x10 Sep 12 11:26:53 hermes.in-addr.de kernel: ret_from_fork+0x29/0x50 Sep 12 11:26:53 hermes.in-addr.de kernel: </TASK> Sep 12 11:26:53 hermes.in-addr.de kernel: ---[ end trace 0000000000000000 ]--- Sep 12 11:26:53 hermes.in-addr.de kernel: BTRFS: error (device dm-4: state A) in __btrfs_run_delayed_items:1158: errno=-17 Object already exists Sep 12 11:26:53 hermes.in-addr.de kernel: BTRFS info (device dm-4: state EA): forced readonly Sep 12 11:26:53 hermes.in-addr.de kernel: BTRFS warning (device dm-4: state EA): Skipping commit of aborted transaction. Sep 12 11:26:53 hermes.in-addr.de kernel: BTRFS: error (device dm-4: state EA) in cleanup_transaction:1984: errno=-17 Object already exists Sep 12 11:27:03 hermes.in-addr.de wireplumber[18046]: could not save restore-stream: Failed to create file “/home/lmb/.local/state/wireplumber/restore-stream.EN8MB2”: Read-only file system After a subsequent reboot, btrfs check did not find any errors on the file system, and the system has been up and running since. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1215665] New: Lenovo ThinkPad T14s Gen 2a intermittent freezing / "your system is too slow"
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1215665 Bug ID: 1215665 Summary: Lenovo ThinkPad T14s Gen 2a intermittent freezing / "your system is too slow" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: georg.pfuetzenreuter(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, said machine will randomly freeze for a marginal period of time (1-5 seconds). This is particularly noticeable while performing touch-typing, where the short freezes result in irregular text input (missing, duplicate, or infinite characters). I attempted booting with `amd_pstate=active` with no change in behavior. My desktop environment is openSUSEway (Sway/Wayland). This problem started occurring some Tumbleweed snapshots ago, though I don't recall exactly - there were other freezing issues with this hardware model before, though not in the current form where it happens consistently for short periods throughout the day. There's nothing printed in the kernel log when this happens, but the system journal is spammed with the following: ``` Sep 25 13:09:44 dreamland sway[2704]: 25:10:18.402 [ERROR] [wlr] [libinput] event5 - Microsoft Microsoft Ergonomic Mouse: WARNING: log rate limit exceeded (5 msgs per 60min). Discarding future messages. Sep 25 13:10:03 dreamland sway[2704]: 25:10:36.590 [ERROR] [wlr] [libinput] event6 - Logitech K350: client bug: event processing lagging behind by 26ms, your system is too slow ``` Currently I am running: ``` $ grep ^VERSION /etc/os-release ; uname -r ; cpupower frequency-info --driver VERSION_ID="20230921" 6.5.4-1-default analyzing CPU 15: driver: amd-pstate-epp ``` Note that the behavior happens both under load and when idle, directly after rebooting. Happy to test any other constellations or provide more information as needed. I entered this in the Kernel component as there seem to have been other kernel issues with this machine in the past, however feel free to route elsewhere should this not apply here. Would appreciate any help, Georg -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1226346] New: No audio in Controller Intel Tiger Lake-LP
by bugzilla_noreply＠suse.com 04 Dec '24

04 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1226346 Bug ID: 1226346 Summary: No audio in Controller Intel Tiger Lake-LP Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: rhusdel(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Multimedia audio controller Intel Corporation Tiger Lake-LP Smart Sound Technology Audio Controller Hardware is not detected. lspci | grep -i audio 00:1f.3 Multimedia audio controller: Intel Corporation Tiger Lake-LP Smart Sound Technology Audio Controller (rev 20) -- You are receiving this mail because: You are the assignee for the bug.

1 9

[kernel-bugs] Account verification
by noreply＠suse.de 18 Nov '24

18 Nov '24

Dear user opensuse-kernelbugs, we have received your email verification request. To verify your email address, please follow this link: https://idp-portal.suse.com/univention/self-service/#page=verifyaccount&tok… If the link does not work, you can go to https://idp-portal.suse.com/univention/self-service/#page=verifyaccount and enter the following token manually: vNjCDHqnMwqYa48z3RokLQTpZdp3sYBxddU7iGJR9UhboG8guN3hssVvHHxVARWo -- To unsubscribe, e-mail: kernel-bugs+unsubscribe(a)opensuse.org To contact the owner, e-mail: kernel-bugs+owner(a)opensuse.org

2 1

[kernel-bugs] [Bug 1172181] test bug for assignee change
by bugzilla_noreply＠suse.com 18 Nov '24

18 Nov '24

http://bugzilla.suse.com/show_bug.cgi?id=1172181 Jeff Mahoney <jeffm(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|jeffm(a)suse.com |kernel-bugs(a)opensuse.org -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

2 1

[Bug 1211985] New: kernel: RTNL: assertion failed at net/core/dev.c (2879)
by bugzilla_noreply＠suse.com 15 Nov '24

15 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1211985 Bug ID: 1211985 Summary: kernel: RTNL: assertion failed at net/core/dev.c (2879) 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: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 867393 --> https://bugzilla.suse.com/attachment.cgi?id=867393&action=edit stack trace openSUSE Tumbleweed 20230601 Linux 6.3.4-1-default kernel stack trace: kernel: RTNL: assertion failed at net/core/dev.c (2879) see log There was nothing special going on, when this happened. The akonadiserver message 3 minutes before was the latest, before the crash occurred. Afterwards the igb net device was gone. After a reboot everything seems to work again. -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1213139] New: [Build 20230706] openQA test fails in consoletest_setup: vmalloc error in kernel
by bugzilla_noreply＠suse.com 15 Nov '24

15 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1213139 Bug ID: 1213139 Summary: [Build 20230706] openQA test fails in consoletest_setup: vmalloc error in kernel Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3412937/modules/cons oletest_setup/steps/52 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: openQA Blocker: Yes Randomly (currently every ~4th run), the test fails because systemd-vconsole-setup fails to complete. The kernel spits out an allocation failure: [ 519.853569] systemd-vconsol: vmalloc error: size 0, page order 9, failed to allocate pages, mode:0xcc2(GFP_KERNEL|__GFP_HIGHMEM), nodemask=(null),cpuset=/,mems_allowed=0 [ 519.854619] CPU: 0 PID: 11361 Comm: systemd-vconsol Not tainted 6.3.9-1-default #1 openSUSE Tumbleweed 4b767630dbc263131e96e89ef291fd4fd2951892 [ 519.855385] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 0.0.0 02/06/2015 [ 519.855860] Call Trace: [ 519.856047] <TASK> [ 519.856208] dump_stack_lvl+0x47/0x60 [ 519.856455] warn_alloc+0x13a/0x1b0 [ 519.856693] ? __alloc_pages+0x32d/0x350 [ 519.857009] __vmalloc_node_range+0x631/0x8b0 [ 519.857343] ? con_font_op+0x193/0x430 [ 519.857593] kvmalloc_node+0xa6/0xd0 [ 519.857857] ? con_font_op+0x193/0x430 [ 519.858105] con_font_op+0x193/0x430 [ 519.858346] ? __pfx_bpf_lsm_capable+0x10/0x10 [ 519.858631] ? security_capable+0x44/0x70 [ 519.858891] vt_ioctl+0x834/0x1380 [ 519.859126] tty_ioctl+0x4b1/0x870 [ 519.859355] __x64_sys_ioctl+0x94/0xd0 [ 519.859601] do_syscall_64+0x60/0x90 [ 519.859871] ? exc_page_fault+0x6e/0x150 [ 519.860129] entry_SYSCALL_64_after_hwframe+0x72/0xdc [ 519.860447] RIP: 0033:0x7f1144d0c2cf [ 519.860710] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00 [ 519.861757] RSP: 002b:00007ffe520b5af0 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [ 519.862201] RAX: ffffffffffffffda RBX: 00007ffe520b5c10 RCX: 00007f1144d0c2cf [ 519.862843] RDX: 00007ffe520b5bf0 RSI: 0000000000004b72 RDI: 0000000000000003 [ 519.863463] RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000001 [ 519.864093] R10: 0000000000000004 R11: 0000000000000246 R12: 0000000000000008 [ 519.864705] R13: 0000000000000003 R14: 0000000000000000 R15: 0000000000000000 [ 519.865317] </TASK> [ 519.865681] Mem-Info: [ 519.866038] active_anon:34752 inactive_anon:94983 isolated_anon:0 active_file:120769 inactive_file:114642 isolated_file:0 unevictable:3088 dirty:1160 writeback:0 slab_reclaimable:23978 slab_unreclaimable:21653 mapped:30383 shmem:4200 pagetables:3497 sec_pagetables:0 bounce:0 kernel_misc_reclaimable:0 free:66953 free_pcp:198 free_cma:0 [ 519.881932] Node 0 active_anon:139008kB inactive_anon:379932kB active_file:483076kB inactive_file:458568kB unevictable:12352kB isolated(anon):0kB isolated(file):0kB mapped:121532kB dirty:4640kB writeback:0kB shmem:16800kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 61440kB writeback_tmp:0kB kernel_stack:8040kB pagetables:13988kB sec_pagetables:0kB all_unreclaimable? no [ 519.893364] Node 0 DMA free:8220kB boost:0kB min:328kB low:408kB high:488kB reserved_highatomic:0KB active_anon:32kB inactive_anon:1908kB active_file:1564kB inactive_file:2136kB unevictable:0kB writepending:0kB present:15000kB managed:14364kB mlocked:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB [ 519.903019] lowmem_reserve[]: 0 1889 1889 1889 1889 [ 519.905153] Node 0 DMA32 free:259592kB boost:0kB min:44724kB low:55904kB high:67084kB reserved_highatomic:16384KB active_anon:138976kB inactive_anon:378024kB active_file:481512kB inactive_file:456432kB unevictable:12352kB writepending:4640kB present:2076960kB managed:1966804kB mlocked:16kB bounce:0kB free_pcp:792kB local_pcp:792kB free_cma:0kB [ 519.915738] lowmem_reserve[]: 0 0 0 0 0 [ 519.917815] Node 0 DMA: 31*4kB (UME) 13*8kB (UME) 10*16kB (UM) 21*32kB (UME) 20*64kB (UM) 10*128kB (UME) 2*256kB (UE) 2*512kB (UE) 1*1024kB (E) 1*2048kB (E) 0*4096kB = 8228kB [ 519.920264] Node 0 DMA32: 20402*4kB (UMEH) 7366*8kB (UMEH) 2957*16kB (UMEH) 1109*32kB (UMEH) 359*64kB (UMEH) 66*128kB (UMEH) 11*256kB (MH) 4*512kB (MH) 0*1024kB 0*2048kB 0*4096kB = 259624kB [ 519.922145] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB [ 519.923229] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB [ 519.924415] 262294 total pagecache pages [ 519.925139] 22685 pages in swap cache [ 519.925777] Free swap = 1663652kB [ 519.926439] Total swap = 2097148kB [ 519.927082] 522990 pages RAM [ 519.927676] 0 pages HighMem/MovableOnly [ 519.928332] 27698 pages reserved [ 519.929181] 0 pages cma reserved [ 519.929828] 0 pages hwpoisoned If the system was actually out of RAM, I'd expect it to fail earlier in random places already. ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-upgrade_Leap_15.2_cryptlvm@uefi fails in [consoletest_setup](https://openqa.opensuse.org/tests/3412937/modules/consol… ## Test suite description Upgrade scenario with cryptlvm for Leap 15.2 Set QEMUVGA=virtio due to bsc#1210555 ## Reproducible Fails since (at least) Build [20230401](https://openqa.opensuse.org/tests/3205451) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1212937] New: Kernel panic when booting up tumbleweed 20230629
by bugzilla_noreply＠suse.com 15 Nov '24

15 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1212937 Bug ID: 1212937 Summary: Kernel panic when booting up tumbleweed 20230629 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dheidler(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 867932 --> https://bugzilla.suse.com/attachment.cgi?id=867932&action=edit screenshot When I booted my tw system today, I ran into a kernel panic. Kernel: Linux 6.3.9-1-default Architecture: x86-64 Hardware Vendor: Lenovo Hardware Model: ThinkPad T14s Gen 2a The issue happened once and after a reboot I was able to boot up fine. The standby issue with the laptop hanging up on resume and eventually rebooting automatically is back again and sadly reproducible always. Not sure if that could be related. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1211380] New: Keyboard not working on laptop ASUS TUF FA507NU
by bugzilla_noreply＠suse.com 15 Nov '24

15 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1211380 Bug ID: 1211380 Summary: Keyboard not working on laptop ASUS TUF FA507NU Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: julien.colinet(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 867003 --> https://bugzilla.suse.com/attachment.cgi?id=867003&action=edit lsmod output Hello, I have an issue with my laptop keyboard. The keyboard is not working, only a few keys are working, the mic mute, keyboard backlight and screen brightness. I have to use an USB keyboard for the moment. ASUS TUF A15 FA507NU AMD 7735HS nVidia RTX 4050 Keyboard vas working on Xubuntu with kernel 5.19. With kernel 6.2 it doesn't work with Xubuntu, Endeavour and Leap/Tumbleweed. I installed a newer snapshot of Tumbleweed with 6.3 kernel but it doesn't change anything. The bug is similar to this one: https://bugzilla.kernel.org/show_bug.cgi?id=217336 The keyboard is working fine under Windows 11, so for now I use my laptop on Windows but it would be great if this bug can be solved so I can use Tumbleweed -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 1211352] New: ThinkPad T14s Gen 2a hangs up on s2ram resume
by bugzilla_noreply＠suse.com 15 Nov '24

15 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1211352 Bug ID: 1211352 Summary: ThinkPad T14s Gen 2a hangs up on s2ram resume Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dheidler(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 866978 --> https://bugzilla.suse.com/attachment.cgi?id=866978&action=edit hwinfo.txt The suspend mode selector that can be set to windows or linux is set to linux via UEFI/BIOS setup. The suspend seems to work fine. The system suspends and the power led begins to flash. On resume the screen stays dark - the backlight does light up, though. It it not possible to switch to a tty. ``` cat /etc/systemd/logind.conf | grep -v '^#' [Login] HandlePowerKey=suspend HandleLidSwitch=ignore ``` -- You are receiving this mail because: You are the assignee for the bug.

1 5

[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 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 1216851] New: kernel BUG at ../mm/slub.c:379!
by bugzilla_noreply＠suse.com 30 Sep '24

30 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1216851 Bug ID: 1216851 Summary: kernel BUG at ../mm/slub.c:379! Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: obs(a)akr.yagii.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Observed today first time when doing day-to-day work with firefox on a laptop logged in as plain user. Potential dupe #1190482 [226385.604827] kernel BUG at ../mm/slub.c:379! [226385.604844] invalid opcode: 0000 [#1] PREEMPT SMP NOPTI [226385.604853] CPU: 4 PID: 765 Comm: irq/176-iwlwifi Kdump: loaded Tainted: G N 5.14.21-150400.24.88-default #1 SLE15-SP4 bd2f624c6b628ccd74aec14e859f7b291002e62d [226385.604866] Hardware name: LENOVO 20W000ATGE/20W000ATGE, BIOS N34ET53W (1.53 ) 08/31/2022 [226385.604872] RIP: 0010:__slab_free+0x2ba/0x4b0 [226385.604884] Code: 85 8e 00 00 00 45 85 c9 0f 84 b6 00 00 00 48 81 c4 88 00 00 00 5b 41 5c 41 5d 41 5e 41 5f 5d 49 8d 65 f0 41 5d c3 cc cc cc cc <0f> 0b 65 ff 05 fd 17 31 79 f0 49 0f ba 2c 24 00 0f 83 31 ff ff ff [226385.604894] RSP: 0018:ffffb92c80234aa0 EFLAGS: 00010246 [226385.604902] RAX: ffff9ad50daf4070 RBX: 000000008020001a RCX: ffff9ad50daf4000 [226385.604908] RDX: ffff9ad50daf4000 RSI: fffffaff0736bd00 RDI: ffff9ad49b881c00 [226385.604914] RBP: ffffb92c80234b50 R08: 0000000000000001 R09: ffffffff872564b3 [226385.604919] R10: ffff9ad4821d0840 R11: ffff9ad50daf4000 R12: fffffaff0736bd00 [226385.604924] R13: ffff9ad50daf4000 R14: ffff9ad49b881c00 R15: ffff9ad50daf4000 [226385.604930] FS: 0000000000000000(0000) GS:ffff9ad79f500000(0000) knlGS:0000000000000000 [226385.604937] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [226385.604942] CR2: 00007f4cc3e6c000 CR3: 0000000159c10006 CR4: 0000000000770ee0 [226385.604949] PKRU: 55555554 [226385.604953] Call Trace: [226385.604958] <IRQ> [226385.604966] ? iwl_mvm_tx_mpdu+0x204/0x580 [iwlmvm 8cc7b51ab5d521e96ea680d180f15f69cb14c62f] [226385.605002] ? kmem_cache_free+0x3c0/0x410 [226385.605011] ? kfree_skb_list+0x13/0x30 [226385.605021] ? kmem_cache_free+0x3c0/0x410 [226385.605029] kmem_cache_free+0x3c0/0x410 [226385.605037] kfree_skb_list+0x13/0x30 [226385.605045] ieee80211_report_used_skb+0xaf/0x490 [mac80211 27f3494b511335547355ff5927e7ac5c52c3181a] [226385.605098] ieee80211_tx_status_ext+0x510/0xb30 [mac80211 27f3494b511335547355ff5927e7ac5c52c3181a] [226385.605145] ieee80211_tx_status+0x7c/0xb0 [mac80211 27f3494b511335547355ff5927e7ac5c52c3181a] [226385.605192] iwl_mvm_tx_reclaim+0x376/0x3f0 [iwlmvm 8cc7b51ab5d521e96ea680d180f15f69cb14c62f] [226385.605224] iwl_mvm_rx_ba_notif+0x187/0x360 [iwlmvm 8cc7b51ab5d521e96ea680d180f15f69cb14c62f] [226385.605251] iwl_mvm_rx_common+0xe3/0x2e0 [iwlmvm 8cc7b51ab5d521e96ea680d180f15f69cb14c62f] [226385.605277] iwl_pcie_rx_handle+0x4db/0x8f0 [iwlwifi 1d7ba350faa5c4a5226540622d76fe15ddc58664] [226385.605309] iwl_pcie_napi_poll_msix+0x29/0xc0 [iwlwifi 1d7ba350faa5c4a5226540622d76fe15ddc58664] [226385.605335] __napi_poll+0x2a/0x180 [226385.605344] net_rx_action+0x24c/0x2a0 [226385.605352] __do_softirq+0xd2/0x2c0 [226385.605360] ? irq_forced_thread_fn+0x80/0x80 [226385.605371] do_softirq+0x71/0x80 [226385.605381] </IRQ> [226385.605385] <TASK> [226385.605389] __local_bh_enable_ip+0x64/0x70 [226385.605398] iwl_pcie_irq_rx_msix_handler+0xc2/0x120 [iwlwifi 1d7ba350faa5c4a5226540622d76fe15ddc58664] [226385.605425] irq_thread_fn+0x1e/0x60 [226385.605437] irq_thread+0xec/0x1a0 [226385.605446] ? wake_threads_waitq+0x30/0x30 [226385.605459] ? irq_thread_check_affinity+0xe0/0xe0 [226385.605468] kthread+0x154/0x180 [226385.605480] ? set_kthread_struct+0x50/0x50 [226385.605492] ret_from_fork+0x1f/0x30 [226385.605507] </TASK> [226385.605513] Modules linked in: nf_conntrack_netbios_ns nf_conntrack_broadcast ccm rfcomm xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT xt_tcpudp bridge stp llc cmac algif_hash algif_skcipher af_alg nf_nat_tftp nft_objref af_packet nf_conntrack_tftp nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_tables ebtable_nat ebtable_broute ip6table_nat ip6table_mangle mhi_net(N) ip6table_raw mhi_wwan_ctrl(N) ip6table_security iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle bnep iptable_raw iptable_security ip_set btusb nfnetlink btrtl btbcm btintel uvcvideo bluetooth videobuf2_vmalloc ebtable_filter videobuf2_memops videobuf2_v4l2 videobuf2_common ebtables videodev mc ecdh_generic crc16 ip6table_filter ip6_tables iptable_filter bpfilter dmi_sysfs snd_ctl_led snd_soc_skl_hda_dsp snd_soc_intel_hda_dsp_common snd_soc_hdac_hdmi snd_soc_dmic iTCO_wdt intel_pmc_bxt [226385.605600] nls_iso8859_1 iTCO_vendor_support mei_hdcp(N) mfd_core nls_cp437 intel_rapl_msr snd_hda_codec_hdmi vfat snd_hda_codec_realtek fat snd_hda_codec_generic intel_tcc_cooling(N) xfs snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match x86_pkg_temp_thermal snd_soc_acpi intel_powerclamp iwlmvm kvm_intel soundwire_bus snd_soc_core mac80211 kvm libarc4 snd_compress irqbypass snd_pcm_dmaengine joydev think_lmi(N) mhi_pci_generic(N) efi_pstore(N) pcspkr snd_hda_intel wmi_bmof firmware_attributes_class(N) ucsi_acpi mhi(N) typec_ucsi snd_intel_dspcfg typec snd_intel_sdw_acpi roles thermal iwlwifi snd_hda_codec thinkpad_acpi snd_hda_core ledtrig_audio cfg80211 snd_hwdep platform_profile ac int3403_thermal snd_pcm processor_thermal_device_pci_legacy(N) processor_thermal_device snd_timer i2c_i801 [226385.605696] processor_thermal_rfim processor_thermal_mbox processor_thermal_rapl mei_me e1000e intel_rapl_common snd intel_hid(N) int340x_thermal_zone sparse_keymap mei soundcore intel_pmc_core i2c_smbus rfkill acpi_tad(N) intel_soc_dts_iosf(N) int3400_thermal igen6_edac acpi_thermal_rel acpi_pad button fuse configfs ip_tables x_tables dm_crypt essiv authenc i915 crc32_pclmul i2c_algo_bit ttm ghash_clmulni_intel drm_kms_helper syscopyarea sysfillrect aesni_intel nvme xhci_pci xhci_pci_renesas xhci_hcd crypto_simd sysimgblt fb_sys_fops sdhci_pci cec rc_core cqhci cryptd sdhci drm mmc_core usbcore nvme_core serio_raw nvme_common t10_pi wmi battery video pinctrl_tigerlake btrfs blake2b_generic libcrc32c crc32c_intel xor raid6_pq coretemp sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua scsi_mod msr efivarfs [226385.605820] Supported: No, Unsupported modules are loaded -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1225159] New: OpenSUSE installation support for RZ/G3S and RZ/V2H
by bugzilla_noreply＠suse.com 30 Sep '24

30 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1225159 Bug ID: 1225159 Summary: OpenSUSE installation support for RZ/G3S and RZ/V2H 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: john.vincent.xa(a)bp.renesas.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, Please enable Renesas RZ/V2H & RZ/G3S SOM device support in openSUSE by updating the following configurations in "config/arm64/default" file CONFIG_ARCH_R9A09G057=y #RZ/V2H CONFIG_ARCH_R9A08G045=y #RZ/G3S Best Regards John -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1225147] New: Kernel hard lockup under mild GPU load
by bugzilla_noreply＠suse.com 26 Sep '24

26 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1225147 Bug ID: 1225147 Summary: Kernel hard lockup under mild GPU load 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: llyyr.public(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:126.0) Gecko/20100101 Firefox/126.0 Build Identifier: Randomly get hard lockups with no errors or dmesg logs, can't ssh into the system either. Reproducible: Always Steps to Reproduce: 1. Record the screen with vaapi encoding on amdgpu Actual Results: Kernel hard lockup some time after 5-30 minutes Expected Results: System should be stable With i5-13600k and RX 6600 XT. I'm running sway and the screen recording tool doesn't matter as long as it's using vaapi encoding. The Mesa version also doesn't matter. This happens on Kernel versions 6.7 or newer, I just tried 6.9.1 and can reproduce it there as well. It does not happen on 6.6.x. I'm currently running 6.6.31-lts. I'd go ahead and bisect the kernel but I'm not sure how to build and install the kernel in a way that it appears in the grub menu. -- You are receiving this mail because: You are the assignee for the bug.

1 4