November 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1205506] New: [Leap][15.4][transactional server] kdump service fails to start
by bugzilla_noreply＠suse.com 18 Nov '22

18 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205506 Bug ID: 1205506 Summary: [Leap][15.4][transactional server] kdump service fails to start Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: richard.fan(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The system role is transactional server, so root file system is readonly. === susetest:~ # cat /etc/*release NAME="openSUSE Leap" VERSION="15.4" ID="opensuse-leap" ID_LIKE="suse opensuse" VERSION_ID="15.4" PRETTY_NAME="openSUSE Leap 15.4" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:leap:15.4" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" DOCUMENTATION_URL="https://en.opensuse.org/Portal:Leap" LOGO="distributor-logo-Leap" susetest:~ # rpm -qa|grep kdump yast2-kdump-4.4.4-150400.3.3.1.x86_64 kdump-1.0.2+git14.gb49d4a3-150400.3.5.1.x86_64 susetest:~ # uname -r 5.14.21-150400.24.28-default === susetest:~ # systemctl restart kdump Job for kdump.service failed because the control process exited with error code. See "systemctl status kdump.service" and "journalctl -xeu kdump.service" for details. susetest:~ # journalctl -xeu kdump.service �� Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel �� An ExecStart= process belonging to unit kdump.service has exited. �� The process' exit code is 'exited' and its exit status is 1. Nov 17 01:54:16 susetest systemd[1]: kdump.service: Failed with result 'exit-code'. �� Subject: Unit failed �� Defined-By: systemd �� Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel �� The unit kdump.service has entered the 'failed' state with result 'exit-code'. Nov 17 01:54:16 susetest systemd[1]: Failed to start Load kdump kernel and initrd. �� Subject: A start job for unit kdump.service has failed �� Defined-By: systemd �� Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel �� A start job for unit kdump.service has finished with a failure. �� The job identifier is 880 and the job result is failed. Nov 17 01:56:58 susetest systemd[1]: Starting Load kdump kernel and initrd... �� Subject: A start job for unit kdump.service has begun execution �� Defined-By: systemd �� Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel �� A start job for unit kdump.service has begun execution. �� The job identifier is 1068. Nov 17 01:56:59 susetest load.sh[15275]: Regenerating kdump initrd ... Nov 17 01:56:59 susetest load.sh[15275]: dracut: Executing: /usr/bin/dracut --force --hostonly --no-hostonly-default-device --omit "plymouth resume usrmount" --compress "xz -0 --check=crc32" --add kdump /boot/initrd-5.14.21-150400.24.28-> Nov 17 01:56:59 susetest load.sh[15275]: dracut: No permission to write to /boot. Nov 17 01:56:59 susetest systemd[1]: kdump.service: Main process exited, code=exited, status=1/FAILURE �� Subject: Unit process exited �� Defined-By: systemd �� Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel �� An ExecStart= process belonging to unit kdump.service has exited. �� The process' exit code is 'exited' and its exit status is 1. Nov 17 01:56:59 susetest systemd[1]: kdump.service: Failed with result 'exit-code'. �� Subject: Unit failed �� Defined-By: systemd �� Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel �� The unit kdump.service has entered the 'failed' state with result 'exit-code'. Nov 17 01:56:59 susetest systemd[1]: Failed to start Load kdump kernel and initrd. �� Subject: A start job for unit kdump.service has failed �� Defined-By: systemd �� Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel �� A start job for unit kdump.service has finished with a failure. �� The job identifier is 1068 and the job result is failed. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1204382] New: kernel-obs-build 5.3 from SLE 15 SP3 is not loading in qemu anymore
by bugzilla_noreply＠suse.com 17 Nov '22

17 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204382 Bug ID: 1204382 Summary: kernel-obs-build 5.3 from SLE 15 SP3 is not loading in qemu anymore Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: adrian.schroeter(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- We noticed that the kernel-obs-build is not loading in KVM for armv7l anymore. This was noticed in openSUSE:Step:15.3 project, but we used this kernel also so far as default kernel for any distributions which do not bring their own kernel. Switching to SP4 has solved the issues, but SP3 kernel used to work also. It might be caused by switching to SP4 as host OS (qemu 5.3 to 6.2), not verified yet. -- You are receiving this mail because: You are the assignee for the bug.

1 15

[Bug 1205447] New: machine keyring is not enabled
by bugzilla_noreply＠suse.com 17 Nov '22

17 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205447 Bug ID: 1205447 Summary: machine keyring is not enabled 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: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- machine keyring is the upstream solution for making MOK available to the kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1204277] IPMI of power8 machine (type 8247-22L) is not accessible after firmware upgrade
by bugzilla_noreply＠suse.com 17 Nov '22

17 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204277 LTC BugProxy <bugproxy(a)us.ibm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.linux.ibm. | |com/show_bug.cgi?id=200524 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204277] IPMI of power8 machine (type 8247-22L) is not accessible after firmware upgrade
by bugzilla_noreply＠suse.com 17 Nov '22

17 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204277 https://bugzilla.suse.com/show_bug.cgi?id=1204277#c5 --- Comment #5 from G�ry Schneider <gery.schneider(a)fr.ibm.com> --- Hello SUSE, I have mirrored this bug to IBM LTC Bug 200524. The IBM team update about it will show up here. Thank you for your support. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205259] WIth kernel 6.0.7-1 on raspberry pi400 nothing displayed on HDMI ports
by bugzilla_noreply＠suse.com 17 Nov '22

17 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205259 https://bugzilla.suse.com/show_bug.cgi?id=1205259#c9 Ivan Ivanov <ivan.ivanov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |UPSTREAM --- Comment #9 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- Yep, tested on RPi4 with upcoming TW kernel 6.0.9 which has above patch, system boot to graphical login screen. Thanks! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204277] IPMI of power8 machine (type 8247-22L) is not accessible after firmware upgrade
by bugzilla_noreply＠suse.com 16 Nov '22

16 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204277 Mark Cowley <mcowley(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hector.oron(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205259] WIth kernel 6.0.7-1 on raspberry pi400 nothing displayed on HDMI ports
by bugzilla_noreply＠suse.com 16 Nov '22

16 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205259 https://bugzilla.suse.com/show_bug.cgi?id=1205259#c8 Stefan Wahren <stefan.wahren(a)i2se.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |stefan.wahren(a)i2se.com --- Comment #8 from Stefan Wahren <stefan.wahren(a)i2se.com> --- There is already a fix (mainline and in 6.0.9) which should address this issue: drm/vc4: hdmi: Fix HSM clock too low on Pi4 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205259] WIth kernel 6.0.7-1 on raspberry pi400 nothing displayed on HDMI ports
by bugzilla_noreply＠suse.com 16 Nov '22

16 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205259 https://bugzilla.suse.com/show_bug.cgi?id=1205259#c7 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ivan.ivanov(a)suse.com, | |mbrugger(a)suse.com, | |tiwai(a)suse.com, | |tzimmermann(a)suse.com --- Comment #7 from Takashi Iwai <tiwai(a)suse.com> --- Sounds like the known issue we've hit. Adding more people to Cc. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205198] LED not working on ASUS AC51 wireless USB adapter (MT7610U chipset) using Mediatek driver
by bugzilla_noreply＠suse.com 16 Nov '22

16 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205198 https://bugzilla.suse.com/show_bug.cgi?id=1205198#c5 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(ray.jantz(a)gmail.c | |om) | --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- Thanks. The thread can be seen at: https://lore.kernel.org/all/ba072331-b7db-edc3-de77-4496d402f497@gmail.com/ The problem seems to be known. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190256] Keyboard not working after cold-boot on ASUS Zenbook 14 UM425UA with Tumbleweed 20210904
by bugzilla_noreply＠suse.com 15 Nov '22

15 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1190256 https://bugzilla.suse.com/show_bug.cgi?id=1190256#c67 --- Comment #67 from Phi <comphi(a)protonmail.com> --- (In reply to Takashi Iwai from comment #66) > (In reply to Phi from comment #65) > > Hello, > > my Zenbook has the same issue. > > cat /sys/class/dmi/id/product_name gives ZenBook UX325SA_UM325SA > > cat /sys/class/dmi/id/board_vendor gives ASUSTek COMPUTER INC. > > It would be nice if you could add them to the patch as well. > > Does the problem happen with the latest TW kernel, too? Luckily, it somehow works now, at least in TW. I found out that there is a bios update so I applied it. I also disabled secure boot and did a fresh install of TW (6.0.8). Not sure which part fixed it, but the problem is gone now. I also installed arch 6.0.8, and the problem still happens there, but I guess that is a different story. Maybe 6.1 will fix it -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204705] Kernel 6.0.3: NULL pointer dereference + Plasma 5.26.1 session not working; 6.0.2 works
by bugzilla_noreply＠suse.com 15 Nov '22

15 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204705 https://bugzilla.suse.com/show_bug.cgi?id=1204705#c33 --- Comment #33 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2022:3998-1: An update that solves 37 vulnerabilities, contains 25 features and has 38 fixes is now available. Category: security (important) Bug References: 1065729,1071995,1152472,1152489,1188238,1194869,1196018,1196632,1199904,1200567,1200692,1200788,1202187,1202686,1202700,1202914,1203098,1203229,1203290,1203435,1203514,1203699,1203701,1203767,1203770,1203802,1203922,1203979,1204017,1204051,1204059,1204060,1204125,1204142,1204166,1204168,1204171,1204241,1204353,1204354,1204355,1204402,1204413,1204415,1204417,1204428,1204431,1204439,1204470,1204479,1204498,1204533,1204569,1204574,1204575,1204619,1204635,1204637,1204646,1204647,1204650,1204653,1204693,1204705,1204719,1204728,1204753,1204868,1204926,1204933,1204934,1204947,1204957,1204963,1204970 CVE References: CVE-2022-1882,CVE-2022-2153,CVE-2022-28748,CVE-2022-2964,CVE-2022-2978,CVE-2022-3169,CVE-2022-33981,CVE-2022-3424,CVE-2022-3435,CVE-2022-3521,CVE-2022-3524,CVE-2022-3526,CVE-2022-3535,CVE-2022-3542,CVE-2022-3545,CVE-2022-3565,CVE-2022-3577,CVE-2022-3586,CVE-2022-3594,CVE-2022-3619,CVE-2022-3621,CVE-2022-3625,CVE-2022-3628,CVE-2022-3629,CVE-2022-3633,CVE-2022-3640,CVE-2022-3646,CVE-2022-3649,CVE-2022-40476,CVE-2022-40768,CVE-2022-41674,CVE-2022-42703,CVE-2022-42719,CVE-2022-42720,CVE-2022-42721,CVE-2022-42722,CVE-2022-43750 JIRA References: PED-1082,PED-1084,PED-1085,PED-1096,PED-1211,PED-1649,PED-634,PED-676,PED-678,PED-679,PED-707,PED-732,PED-813,PED-817,PED-822,PED-825,PED-833,PED-842,PED-846,PED-850,PED-851,PED-856,PED-857,SLE-13847,SLE-9246 Sources used: openSUSE Leap 15.4 (src): kernel-azure-5.14.21-150400.14.21.2, kernel-source-azure-5.14.21-150400.14.21.1, kernel-syms-azure-5.14.21-150400.14.21.1 SUSE Linux Enterprise Module for Public Cloud 15-SP4 (src): kernel-azure-5.14.21-150400.14.21.2, kernel-source-azure-5.14.21-150400.14.21.1, kernel-syms-azure-5.14.21-150400.14.21.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205035] Freeze on booting, can only boot in recovery mode
by bugzilla_noreply＠suse.com 15 Nov '22

15 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205035 http://bugzilla.opensuse.org/show_bug.cgi?id=1205035#c3 Pablo Alonso <tau0(a)tutanota.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #3 from Pablo Alonso <tau0(a)tutanota.com> --- I've installed it successfully today. It was because of Ventoy -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205198] LED not working on ASUS AC51 wireless USB adapter (MT7610U chipset) using Mediatek driver
by bugzilla_noreply＠suse.com 15 Nov '22

15 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205198 https://bugzilla.suse.com/show_bug.cgi?id=1205198#c4 --- Comment #4 from Ray Jantz <ray.jantz(a)gmail.com> --- The message ID for my bug submission to linux-wireless is: <ba072331-b7db-edc3-de77-4496d402f497(a)gmail.com> -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205259] New: WIth kernel 6.0.7-1 on raspberry pi400 nothing displayed on HDMI ports
by bugzilla_noreply＠suse.com 15 Nov '22

15 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205259 Bug ID: 1205259 Summary: WIth kernel 6.0.7-1 on raspberry pi400 nothing displayed on HDMI ports 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: conde.philippe(a)skynet.be QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 862768 --> http://bugzilla.opensuse.org/attachment.cgi?id=862768&action=edit Dmesg ouput On my raspberry pi400 when I boot with kernel 6.0.7-1 I can select the boot but after display "loading initial ramdisk" the screen goes black and nothing is displayed. I can login via ssh.So the system is started correctly but nothing is displayed. If at boot I select kernel 6.0.3 the login screen is correzctly displayed n the hdmi screen and I can login. I attach the dmesg output and the Xorg.0.log logfile when booting kernel 6.0.7-1 Regards Philippe -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1205035] Freeze on booting, can only boot in recovery mode
by bugzilla_noreply＠suse.com 15 Nov '22

15 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205035 http://bugzilla.opensuse.org/show_bug.cgi?id=1205035#c2 --- Comment #2 from Pablo Alonso <tau0(a)tutanota.com> --- The history doesn't go far enough to test it. Also, I could only boot in recovery mode. I can try to install Leap and then transform it to Thumbleweed -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204705] New: KDE Plasma fails to start with Kernel 6.0.3
by bugzilla_noreply＠suse.com 15 Nov '22

15 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204705 Bug ID: 1204705 Summary: KDE Plasma fails to start with Kernel 6.0.3 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: postix(a)posteo.eu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since updating from kernel 6.0.2 to 6.0.3 on openSUSE TW, KDE Plasma 5.26.1 running X11 or Wayland fails to start, after logging in from SDDM: * The cursor works, but no panel shows up, the desktop starts to freeze, i.e. turns gray after a while * Pressing CTRL+ALT+DEL opens the power-management overlay, where logging out works * Shutting down the system does not work after having logged in once, but takes infinitely long and requires a forced shut down Going back to kernel 6.0.2 fixes the issue. An interesting part of the journalctl is likely the following: ``` 09:56:43 kernel: BUG: kernel NULL pointer dereference, address: 00000000000001c8 09:56:43 kernel: #PF: supervisor write access in kernel mode 09:56:43 kernel: #PF: error_code(0x0002) - not-present page 09:56:43 kernel: PGD 0 P4D 0 09:56:43 kernel: Oops: 0002 [#1] PREEMPT SMP NOPTI 09:56:43 kernel: CPU: 16 PID: 1419 Comm: rasdaemon Tainted: G O 6.0.3-1-default #1 openSUSE Tumbleweed 50a6ebc5cb1873d6b9c639843cdd1ed0089a1281 09:56:43 kernel: Hardware name: System manufacturer System Product Name/ROG STRIX X570-E GAMING, BIOS 4204 02/24/2022 09:56:43 kernel: RIP: 0010:ring_buffer_wake_waiters+0x1c/0xa0 09:56:43 kernel: Code: 48 39 d0 73 ed 0f 0b eb e9 0f 1f 44 00 00 55 48 89 fd 53 48 63 de 83 fb ff 74 36 48 8b 47 40 48 8b 1c d8 48 81 c3 78 01 00 00 <48> 83 43 50 01 31 c9 31 d2 48 8d 7b 20 be 03 00 00 00 e8 cd af f3 09:56:43 kernel: RSP: 0018:ffffaa7a815a7e20 EFLAGS: 00010206 09:56:43 kernel: RAX: ffff908c434db500 RBX: 0000000000000178 RCX: 0000000000000010 09:56:43 kernel: RDX: ffff908c78ed8000 RSI: 0000000000000018 RDI: ffff908c434da900 09:56:43 kernel: RBP: ffff908c434da900 R08: ffff908c50b82e00 R09: ffff908c8206b200 09:56:43 kernel: R10: 0000000000000000 R11: 0000000000000001 R12: ffff908c8206b200 09:56:43 kernel: R13: ffff908c4387ef20 R14: ffff908c90fddbc0 R15: 0000000000000000 09:56:43 kernel: FS: 00007fd7463a6340(0000) GS:ffff90934ee00000(0000) knlGS:0000000000000000 09:56:43 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 09:56:43 kernel: CR2: 00000000000001c8 CR3: 0000000105574000 CR4: 0000000000750ee0 09:56:43 kernel: PKRU: 55555554 09:56:43 kernel: Call Trace: 09:56:43 kernel: <TASK> 09:56:43 kernel: tracing_buffers_release+0x49/0x90 09:56:43 kernel: __fput+0x91/0x250 09:56:43 kernel: task_work_run+0x5c/0x90 09:56:43 kernel: exit_to_user_mode_prepare+0x1cb/0x1f0 09:56:43 kernel: syscall_exit_to_user_mode+0x17/0x40 09:56:43 kernel: do_syscall_64+0x67/0x80 09:56:43 kernel: ? syscall_exit_to_user_mode+0x17/0x40 09:56:43 kernel: ? do_syscall_64+0x67/0x80 09:56:43 kernel: ? do_syscall_64+0x67/0x80 09:56:43 kernel: ? syscall_exit_to_user_mode+0x17/0x40 09:56:43 kernel: ? do_syscall_64+0x67/0x80 09:56:43 kernel: ? do_syscall_64+0x67/0x80 09:56:43 kernel: ? do_syscall_64+0x67/0x80 09:56:43 kernel: ? do_syscall_64+0x67/0x80 09:56:43 kernel: ? do_syscall_64+0x67/0x80 09:56:43 kernel: entry_SYSCALL_64_after_hwframe+0x63/0xcd 09:56:43 kernel: RIP: 0033:0x7fd74658e014 09:56:43 kernel: Code: 00 0f 1f 44 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 90 90 80 3d 8d 09 0f 00 00 74 13 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 44 c3 0f 1f 00 48 83 ec 18 89 7c 24 0c e8 51 09:56:43 kernel: RSP: 002b:00007ffce5e64348 EFLAGS: 00000202 ORIG_RAX: 0000000000000003 09:56:43 kernel: RAX: 0000000000000000 RBX: 00007ffce5e64490 RCX: 00007fd74658e014 09:56:43 kernel: RDX: 0000000000000000 RSI: 00007ffce5e64540 RDI: 000000000000001d 09:56:43 kernel: RBP: 00007ffce5e65a10 R08: 000055939344e6c0 R09: 0000000000000000 09:56:43 kernel: R10: 0000000000000008 R11: 0000000000000202 R12: 0000000000000001 09:56:43 kernel: R13: 00007ffce5e644d8 R14: 000055939344e6c0 R15: 000055939344e6c0 09:56:43 kernel: </TASK> 09:56:43 kernel: Modules linked in: amd64_edac(-) cmac algif_hash algif_skcipher af_alg vboxdrv(O) qrtr bnep dmi_sysfs wacom nls_iso8859_1 nls_cp437 vfat fat intel_rapl_msr iwlmvm intel_rapl_common asus_ec_sensors mac80211 libarc4 snd_hda_codec_realtek snd_hda_codec_generic btusb edac_mce_amd snd_hda_codec_hdmi btrtl snd_usb_audio btbcm snd_hda_intel btintel snd_intel_dspcfg btmtk snd_intel_sdw_acpi kvm_amd snd_hda_codec snd_usbmidi_lib iwlwifi bluetooth snd_rawmidi snd_hda_core joydev snd_seq_device kvm ecdh_generic eeepc_wmi snd_hwdep asus_wmi cfg80211 battery snd_pcm irqbypass ledtrig_audio sparse_keymap r8169 platform_profile snd_timer video pcspkr wmi_bmof efi_pstore mxm_wmi realtek snd igb k10temp i2c_piix4 mdio_devres soundcore libphy rfkill dca tiny_power_button button acpi_cpufreq fuse configfs ip_tables x_tables hid_generic usbhid amdgpu crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic gf128mul xhci_pci xhci_pci_renesas drm_ttm_helper ttm xhci_hcd 09:56:43 kernel: iommu_v2 gpu_sched ghash_clmulni_intel drm_buddy aesni_intel drm_display_helper nvme usbcore crypto_simd cryptd cec ccp nvme_core sp5100_tco rc_core wmi btrfs blake2b_generic libcrc32c crc32c_intel xor raid6_pq v4l2loopback(O) videodev mc sg br_netfilter bridge stp llc dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua msr efivarfs 09:56:43 kernel: CR2: 00000000000001c8 09:56:43 kernel: ---[ end trace 0000000000000000 ]--- 09:56:43 kernel: RIP: 0010:ring_buffer_wake_waiters+0x1c/0xa0 09:56:43 kernel: Code: 48 39 d0 73 ed 0f 0b eb e9 0f 1f 44 00 00 55 48 89 fd 53 48 63 de 83 fb ff 74 36 48 8b 47 40 48 8b 1c d8 48 81 c3 78 01 00 00 <48> 83 43 50 01 31 c9 31 d2 48 8d 7b 20 be 03 00 00 00 e8 cd af f3 09:56:43 kernel: RSP: 0018:ffffaa7a815a7e20 EFLAGS: 00010206 09:56:43 kernel: RAX: ffff908c434db500 RBX: 0000000000000178 RCX: 0000000000000010 09:56:43 kernel: RDX: ffff908c78ed8000 RSI: 0000000000000018 RDI: ffff908c434da900 09:56:43 kernel: RBP: ffff908c434da900 R08: ffff908c50b82e00 R09: ffff908c8206b200 09:56:43 kernel: R10: 0000000000000000 R11: 0000000000000001 R12: ffff908c8206b200 09:56:43 kernel: R13: ffff908c4387ef20 R14: ffff908c90fddbc0 R15: 0000000000000000 09:56:43 kernel: FS: 00007fd7463a6340(0000) GS:ffff90934ee00000(0000) knlGS:0000000000000000 09:56:43 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 09:56:43 kernel: CR2: 00000000000001c8 CR3: 0000000105574000 CR4: 0000000000750ee0 09:56:43 kernel: PKRU: 55555554 ``` SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20221023 KDE Plasma Version: 5.26.1 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 6.0.2-1-default (64-bit) / 6.0.3-1-default (64-bit) Graphics Platform: Wayland Graphics Processor: AMD Radeon RX 580 Series -- You are receiving this mail because: You are the assignee for the bug.

1 26

[Bug 1190256] Keyboard not working after cold-boot on ASUS Zenbook 14 UM425UA with Tumbleweed 20210904
by bugzilla_noreply＠suse.com 14 Nov '22

14 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1190256 https://bugzilla.suse.com/show_bug.cgi?id=1190256#c66 --- Comment #66 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Phi from comment #65) > Hello, > my Zenbook has the same issue. > cat /sys/class/dmi/id/product_name gives ZenBook UX325SA_UM325SA > cat /sys/class/dmi/id/board_vendor gives ASUSTek COMPUTER INC. > It would be nice if you could add them to the patch as well. Does the problem happen with the latest TW kernel, too? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205198] LED not working on ASUS AC51 wireless USB adapter (MT7610U chipset) using Mediatek driver
by bugzilla_noreply＠suse.com 14 Nov '22

14 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205198 https://bugzilla.suse.com/show_bug.cgi?id=1205198#c3 --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- Great, could you point the URL (or Message-Id of your post) for tracking? It should be visible on lore.kernel.org. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205277] Kernel crash at full btrfs balance
by bugzilla_noreply＠suse.com 14 Nov '22

14 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205277 Goldwyn Rodrigues <rgoldwyn(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |fdmanana(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205277] Kernel crash at full btrfs balance
by bugzilla_noreply＠suse.com 13 Nov '22

13 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205277 https://bugzilla.suse.com/show_bug.cgi?id=1205277#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rgoldwyn(a)suse.com, | |tiwai(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Something for filesystem team? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205198] LED not working on ASUS AC51 wireless USB adapter (MT7610U chipset) using Mediatek driver
by bugzilla_noreply＠suse.com 12 Nov '22

12 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205198 https://bugzilla.suse.com/show_bug.cgi?id=1205198#c2 --- Comment #2 from Ray Jantz <ray.jantz(a)gmail.com> --- (In reply to Takashi Iwai from comment #1) > Unless it's a regression, it's rather a thing to be reported to the upstream. > Could you try to report it the upstream, e.g. linux-wireless ML? I submitted it to linux-wireless. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205365] New: soft lockup - CPU Stuck
by bugzilla_noreply＠suse.com 12 Nov '22

12 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205365 Bug ID: 1205365 Summary: soft lockup - CPU Stuck 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: j(a)ganomi.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After upgrading to kernel 6.x I am getting CPU Stuck errors which crash my Thinkpad laptop. This is happening intermittently. My current kernel is 6.0.6-1-default, but this has been happening with all 6.x kernels. Nov 12 15:58:18 superman kernel: watchdog: BUG: soft lockup - CPU#4 stuck for 22s! [swapper/4:0] Nov 12 15:58:18 superman kernel: Modules linked in: udp_diag tcp_diag inet_diag tun ccm rfcomm snd_seq_dummy snd_hrtimer snd_seq snd_seq_device xt_conntrack xt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype nft_compat af_packet nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib > Nov 12 15:58:18 superman kernel: iTCO_wdt snd_soc_sst_ipc intel_pmc_bxt intel_pmc_core_pltdrv intel_pmc_core iwlmvm mtd ee1004 snd_soc_sst_dsp iTCO_vendor_support mei_pxp mei_hdcp binfmt_misc intel_rapl_msr snd_soc_acpi_intel_match snd_soc_acpi intel_tcc_cooling mac80211 snd_soc_core uvcvid> Nov 12 15:58:18 superman kernel: platform_profile processor_thermal_rapl intel_rapl_common snd_timer rfkill intel_pch_thermal intel_soc_dts_iosf thermal snd soundcore int3403_thermal ac int340x_thermal_zone int3400_thermal acpi_pad acpi_thermal_rel acpi_tad tiny_power_button fuse configfs i> Nov 12 15:58:18 superman kernel: CPU: 4 PID: 0 Comm: swapper/4 Tainted: G O 6.0.6-1-default #1 openSUSE Tumbleweed 5737233048282b9b45966a5a56a5600da32aa0e8 Nov 12 15:58:18 superman kernel: Hardware name: LENOVO 20TKCTO1WW/20TKCTO1WW, BIOS N2VET39W (1.24 ) 06/27/2022 Nov 12 15:58:18 superman kernel: RIP: 0010:rb_first+0x8/0x20 Nov 12 15:58:18 superman kernel: Code: 01 c3 cc cc cc cc 48 89 50 10 c3 cc cc cc cc 48 89 42 10 c3 cc cc cc cc 66 2e 0f 1f 84 00 00 00 00 00 48 8b 07 48 85 c0 74 14 <48> 89 c2 48 8b 40 10 48 85 c0 75 f4 48 89 d0 c3 cc cc cc cc 31 d2 Nov 12 15:58:18 superman kernel: RSP: 0018:ffffb9b100250de8 EFLAGS: 00000286 Nov 12 15:58:18 superman kernel: RAX: ffff9f567e38d400 RBX: ffff9f57e9ea5780 RCX: ffff9f567e38d400 Nov 12 15:58:18 superman kernel: RDX: ffff9f567e38d400 RSI: ffff9f57e9ea58e0 RDI: ffff9f57e9ea58e0 Nov 12 15:58:18 superman kernel: RBP: 0000000000000036 R08: ffff9f57e9ea58e0 R09: ffff9f5a20130a80 Nov 12 15:58:18 superman kernel: R10: ffff9f5a201320e8 R11: 0000000000004188 R12: 0000000000000003 Nov 12 15:58:18 superman kernel: R13: 00000000000005a0 R14: 000000000000025e R15: 0000000000000002 Nov 12 15:58:18 superman kernel: FS: 0000000000000000(0000) GS:ffff9f5d1f500000(0000) knlGS:0000000000000000 Nov 12 15:58:18 superman kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Nov 12 15:58:18 superman kernel: CR2: 00007f2ca90c2000 CR3: 0000000348d06001 CR4: 00000000007706e0 Nov 12 15:58:18 superman kernel: PKRU: 55555554 Nov 12 15:58:18 superman kernel: Call Trace: Nov 12 15:58:18 superman kernel: <IRQ> Nov 12 15:58:18 superman kernel: tcp_rearm_rto+0xb5/0x130 Nov 12 15:58:18 superman kernel: tcp_event_new_data_sent+0x9e/0xb0 Nov 12 15:58:18 superman kernel: tcp_write_xmit+0x533/0x1350 Nov 12 15:58:18 superman kernel: ? tcp_write_timer_handler+0x240/0x240 Nov 12 15:58:18 superman kernel: tcp_send_loss_probe+0x170/0x1d0 Nov 12 15:58:18 superman kernel: tcp_write_timer+0x99/0xd0 Nov 12 15:58:18 superman kernel: ? tcp_write_timer_handler+0x240/0x240 Nov 12 15:58:18 superman kernel: call_timer_fn+0x24/0x130 Nov 12 15:58:18 superman kernel: __run_timers.part.0+0x1d7/0x260 Nov 12 15:58:18 superman kernel: ? __hrtimer_run_queues+0x159/0x2c0 Nov 12 15:58:18 superman kernel: ? ktime_get+0x35/0xa0 Nov 12 15:58:18 superman kernel: run_timer_softirq+0x26/0x50 Nov 12 15:58:18 superman kernel: __do_softirq+0xc2/0x2a3 Nov 12 15:58:18 superman kernel: __irq_exit_rcu+0xaa/0xe0 Nov 12 15:58:18 superman kernel: sysvec_apic_timer_interrupt+0x6e/0x90 Nov 12 15:58:18 superman kernel: </IRQ> Nov 12 15:58:18 superman kernel: <TASK> Nov 12 15:58:18 superman kernel: asm_sysvec_apic_timer_interrupt+0x16/0x20 Nov 12 15:58:18 superman kernel: RIP: 0010:cpuidle_enter_state+0xde/0x420 Nov 12 15:58:18 superman kernel: Code: 00 00 31 ff e8 13 cf 85 ff 45 84 ff 74 16 9c 58 0f 1f 40 00 f6 c4 02 0f 85 25 03 00 00 31 ff e8 c8 c4 8c ff 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 Nov 12 15:58:18 superman kernel: RSP: 0018:ffffb9b10013fe90 EFLAGS: 00000246 Nov 12 15:58:18 superman kernel: RAX: ffff9f5d1f533bc0 RBX: ffffd9b0ffb01200 RCX: 0000000000000000 Nov 12 15:58:18 superman kernel: RDX: 0000000000000004 RSI: 000064e982a14ffa RDI: 0000000000000000 Nov 12 15:58:18 superman kernel: RBP: 0000000000000002 R08: 0000000000000002 R09: 000000003161f86e Nov 12 15:58:18 superman kernel: R10: 0000000000000018 R11: 00000000000001e5 R12: ffffffff918246a0 Nov 12 15:58:18 superman kernel: R13: 000068081530de4c R14: 0000000000000002 R15: 0000000000000000 Nov 12 15:58:18 superman kernel: cpuidle_enter+0x29/0x40 Nov 12 15:58:18 superman kernel: do_idle+0x202/0x2a0 Nov 12 15:58:18 superman kernel: cpu_startup_entry+0x19/0x20 Nov 12 15:58:18 superman kernel: start_secondary+0x114/0x140 Nov 12 15:58:18 superman kernel: secondary_startup_64_no_verify+0xe5/0xeb Nov 12 15:58:18 superman kernel: </TASK> Nov 12 15:58:18 superman kernel: watchdog: BUG: soft lockup - CPU#6 stuck for 26s! [swapper/6:0] Nov 12 15:58:18 superman kernel: Modules linked in: udp_diag tcp_diag inet_diag tun ccm rfcomm snd_seq_dummy snd_hrtimer snd_seq snd_seq_device xt_conntrack xt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype nft_compat af_packet nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib > Nov 12 15:58:18 superman kernel: iTCO_wdt snd_soc_sst_ipc intel_pmc_bxt intel_pmc_core_pltdrv intel_pmc_core iwlmvm mtd ee1004 snd_soc_sst_dsp iTCO_vendor_support mei_pxp mei_hdcp binfmt_misc intel_rapl_msr snd_soc_acpi_intel_match snd_soc_acpi intel_tcc_cooling mac80211 snd_soc_core uvcvid> Nov 12 15:58:18 superman kernel: platform_profile processor_thermal_rapl intel_rapl_common snd_timer rfkill intel_pch_thermal intel_soc_dts_iosf thermal snd soundcore int3403_thermal ac int340x_thermal_zone int3400_thermal acpi_pad acpi_thermal_rel acpi_tad tiny_power_button fuse configfs i> Nov 12 15:58:18 superman kernel: CPU: 6 PID: 0 Comm: swapper/6 Tainted: G O L 6.0.6-1-default #1 openSUSE Tumbleweed 5737233048282b9b45966a5a56a5600da32aa0e8 Nov 12 15:58:18 superman kernel: Hardware name: LENOVO 20TKCTO1WW/20TKCTO1WW, BIOS N2VET39W (1.24 ) 06/27/2022 Nov 12 15:58:18 superman kernel: RIP: 0010:rb_first+0xf/0x20 Nov 12 15:58:18 superman kernel: Code: 89 50 10 c3 cc cc cc cc 48 89 42 10 c3 cc cc cc cc 66 2e 0f 1f 84 00 00 00 00 00 48 8b 07 48 85 c0 74 14 48 89 c2 48 8b 40 10 <48> 85 c0 75 f4 48 89 d0 c3 cc cc cc cc 31 d2 eb f4 48 8b 07 48 85 Nov 12 15:58:18 superman kernel: RSP: 0018:ffffb9b1002b8de8 EFLAGS: 00000286 Nov 12 15:58:18 superman kernel: RAX: ffff9f5656e41200 RBX: ffff9f57e9ea6900 RCX: ffff9f5656e41200 Nov 12 15:58:18 superman kernel: RDX: ffff9f5656e41200 RSI: ffff9f57e9ea6a60 RDI: ffff9f57e9ea6a60 Nov 12 15:58:18 superman kernel: RBP: 000000000000003d R08: ffff9f57e9ea6a60 R09: ffff9f5a20130a80 Nov 12 15:58:18 superman kernel: R10: ffff9f5a201320e8 R11: 0000000000004188 R12: 0000000000000002 Nov 12 15:58:18 superman kernel: R13: 00000000000005a8 R14: 000000000000001f R15: 0000000000000002 Nov 12 15:58:18 superman kernel: FS: 0000000000000000(0000) GS:ffff9f5d1f580000(0000) knlGS:0000000000000000 Nov 12 15:58:18 superman kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Nov 12 15:58:18 superman kernel: CR2: 00007f2c15673000 CR3: 0000000525210006 CR4: 00000000007706e0 Nov 12 15:58:18 superman kernel: PKRU: 55555554 Nov 12 15:58:18 superman kernel: Call Trace: Nov 12 15:58:18 superman kernel: <IRQ> Nov 12 15:58:18 superman kernel: tcp_rearm_rto+0xb5/0x130 Nov 12 15:58:18 superman kernel: tcp_event_new_data_sent+0x9e/0xb0 Nov 12 15:58:18 superman kernel: tcp_write_xmit+0x533/0x1350 Nov 12 15:58:18 superman kernel: ? tcp_write_timer_handler+0x240/0x240 Nov 12 15:57:40 superman kernel: iwlwifi 0000:00:14.3: 0x20000302 | FSEQ_CNVI_ID Nov 12 15:57:40 superman kernel: iwlwifi 0000:00:14.3: 0x01300504 | FSEQ_CNVR_ID Nov 12 15:57:40 superman kernel: iwlwifi 0000:00:14.3: 0x20000302 | CNVI_AUX_MISC_CHIP Nov 12 15:57:40 superman kernel: iwlwifi 0000:00:14.3: 0x01300504 | CNVR_AUX_MISC_CHIP Nov 12 15:57:40 superman kernel: iwlwifi 0000:00:14.3: 0x05B0905B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM Nov 12 15:57:40 superman kernel: iwlwifi 0000:00:14.3: 0x0000025B | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR Nov 12 15:57:40 superman kernel: iwlwifi 0000:00:14.3: Collecting data: trigger 2 fired. Nov 12 15:57:52 superman rtkit-daemon[2184]: Supervising 1 threads of 1 processes of 1 users. Nov 12 15:57:52 superman rtkit-daemon[2184]: Supervising 1 threads of 1 processes of 1 users. Nov 12 15:58:18 superman kernel: watchdog: BUG: soft lockup - CPU#4 stuck for 22s! [swapper/4:0] Nov 12 15:58:18 superman kernel: Modules linked in: udp_diag tcp_diag inet_diag tun ccm rfcomm snd_seq_dummy snd_hrtimer snd_seq snd_seq_device xt_conntrack xt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype nft_compat af_packet nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib > Nov 12 15:58:18 superman kernel: iTCO_wdt snd_soc_sst_ipc intel_pmc_bxt intel_pmc_core_pltdrv intel_pmc_core iwlmvm mtd ee1004 snd_soc_sst_dsp iTCO_vendor_support mei_pxp mei_hdcp binfmt_misc intel_rapl_msr snd_soc_acpi_intel_match snd_soc_acpi intel_tcc_cooling mac80211 snd_soc_core uvcvid> Nov 12 15:58:18 superman kernel: platform_profile processor_thermal_rapl intel_rapl_common snd_timer rfkill intel_pch_thermal intel_soc_dts_iosf thermal snd soundcore int3403_thermal ac int340x_thermal_zone int3400_thermal acpi_pad acpi_thermal_rel acpi_tad tiny_power_button fuse configfs i> Nov 12 15:58:18 superman kernel: CPU: 4 PID: 0 Comm: swapper/4 Tainted: G O 6.0.6-1-default #1 openSUSE Tumbleweed 5737233048282b9b45966a5a56a5600da32aa0e8 Nov 12 15:58:18 superman kernel: Hardware name: LENOVO 20TKCTO1WW/20TKCTO1WW, BIOS N2VET39W (1.24 ) 06/27/2022 Nov 12 15:58:18 superman kernel: RIP: 0010:rb_first+0x8/0x20 Nov 12 15:58:18 superman kernel: Code: 01 c3 cc cc cc cc 48 89 50 10 c3 cc cc cc cc 48 89 42 10 c3 cc cc cc cc 66 2e 0f 1f 84 00 00 00 00 00 48 8b 07 48 85 c0 74 14 <48> 89 c2 48 8b 40 10 48 85 c0 75 f4 48 89 d0 c3 cc cc cc cc 31 d2 Nov 12 15:58:18 superman kernel: RSP: 0018:ffffb9b100250de8 EFLAGS: 00000286 Nov 12 15:58:18 superman kernel: RAX: ffff9f567e38d400 RBX: ffff9f57e9ea5780 RCX: ffff9f567e38d400 Nov 12 15:58:18 superman kernel: RDX: ffff9f567e38d400 RSI: ffff9f57e9ea58e0 RDI: ffff9f57e9ea58e0 Nov 12 15:58:18 superman kernel: RBP: 0000000000000036 R08: ffff9f57e9ea58e0 R09: ffff9f5a20130a80 Nov 12 15:58:18 superman kernel: R10: ffff9f5a201320e8 R11: 0000000000004188 R12: 0000000000000003 Nov 12 15:58:18 superman kernel: R13: 00000000000005a0 R14: 000000000000025e R15: 0000000000000002 Nov 12 15:58:18 superman kernel: FS: 0000000000000000(0000) GS:ffff9f5d1f500000(0000) knlGS:0000000000000000 Nov 12 15:58:18 superman kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Nov 12 15:58:18 superman kernel: CR2: 00007f2ca90c2000 CR3: 0000000348d06001 CR4: 00000000007706e0 Nov 12 15:58:18 superman kernel: PKRU: 55555554 Nov 12 15:58:18 superman kernel: Call Trace: Nov 12 15:58:18 superman kernel: <IRQ> Nov 12 15:58:18 superman kernel: tcp_rearm_rto+0xb5/0x130 Nov 12 15:58:18 superman kernel: tcp_event_new_data_sent+0x9e/0xb0 Nov 12 15:58:18 superman kernel: tcp_write_xmit+0x533/0x1350 Nov 12 15:58:18 superman kernel: ? tcp_write_timer_handler+0x240/0x240 Nov 12 15:58:18 superman kernel: tcp_send_loss_probe+0x170/0x1d0 Nov 12 15:58:18 superman kernel: tcp_write_timer+0x99/0xd0 Nov 12 15:58:18 superman kernel: ? tcp_write_timer_handler+0x240/0x240 Nov 12 15:58:18 superman kernel: call_timer_fn+0x24/0x130 Nov 12 15:58:18 superman kernel: __run_timers.part.0+0x1d7/0x260 Nov 12 15:58:18 superman kernel: ? __hrtimer_run_queues+0x159/0x2c0 Nov 12 15:58:18 superman kernel: ? ktime_get+0x35/0xa0 Nov 12 15:58:18 superman kernel: run_timer_softirq+0x26/0x50 Nov 12 15:58:18 superman kernel: __do_softirq+0xc2/0x2a3 Nov 12 15:58:18 superman kernel: __irq_exit_rcu+0xaa/0xe0 Nov 12 15:58:18 superman kernel: sysvec_apic_timer_interrupt+0x6e/0x90 Nov 12 15:58:18 superman kernel: </IRQ> Nov 12 15:58:18 superman kernel: <TASK> Nov 12 15:58:18 superman kernel: asm_sysvec_apic_timer_interrupt+0x16/0x20 Nov 12 15:58:18 superman kernel: RIP: 0010:cpuidle_enter_state+0xde/0x420 Nov 12 15:58:18 superman kernel: Code: 00 00 31 ff e8 13 cf 85 ff 45 84 ff 74 16 9c 58 0f 1f 40 00 f6 c4 02 0f 85 25 03 00 00 31 ff e8 c8 c4 8c ff 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 Nov 12 15:58:18 superman kernel: RSP: 0018:ffffb9b10013fe90 EFLAGS: 00000246 Nov 12 15:58:18 superman kernel: RAX: ffff9f5d1f533bc0 RBX: ffffd9b0ffb01200 RCX: 0000000000000000 Nov 12 15:58:18 superman kernel: RDX: 0000000000000004 RSI: 000064e982a14ffa RDI: 0000000000000000 Nov 12 15:58:18 superman kernel: RBP: 0000000000000002 R08: 0000000000000002 R09: 000000003161f86e Nov 12 15:58:18 superman kernel: R10: 0000000000000018 R11: 00000000000001e5 R12: ffffffff918246a0 Nov 12 15:58:18 superman kernel: R13: 000068081530de4c R14: 0000000000000002 R15: 0000000000000000 Nov 12 15:58:18 superman kernel: cpuidle_enter+0x29/0x40 Nov 12 15:58:18 superman kernel: do_idle+0x202/0x2a0 Nov 12 15:58:18 superman kernel: cpu_startup_entry+0x19/0x20 Nov 12 15:58:18 superman kernel: start_secondary+0x114/0x140 Nov 12 15:58:18 superman kernel: secondary_startup_64_no_verify+0xe5/0xeb Nov 12 15:58:18 superman kernel: </TASK> -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205288] New: kernel-default-6.0.7-1.1 breaks wifi on Opensuse Tumbleweed
by bugzilla_noreply＠suse.com 10 Nov '22

10 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205288 Bug ID: 1205288 Summary: kernel-default-6.0.7-1.1 breaks wifi on Opensuse Tumbleweed 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: chingmichaellee2016(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 862786 --> http://bugzilla.opensuse.org/attachment.cgi?id=862786&action=edit this is the result after updating to kernel-default-6.0.7-1.1.x86_64 Wifi not working on kernel-default-6.0.7-1.1 opensuse tumbleweed KDE plasma WiFi card: Broadcom Inc. and subsidiaries BCM4322 802.11a/b/g/n Wireless LAN Controller (rev 01) Drivers and firmware are install. But no wifi adapter is shown on kde networkmanager -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1205277] New: Kernel crash at full btrfs balance
by bugzilla_noreply＠suse.com 10 Nov '22

10 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205277 Bug ID: 1205277 Summary: Kernel crash at full btrfs balance Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ralf.koelmel(a)kit.edu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 862780 --> http://bugzilla.opensuse.org/attachment.cgi?id=862780&action=edit kernel crash and detail infos of the filesystem a full btrfs balance leads reproducably to a kernel crash (on kernel 5.14.21-150400.24.28-default, 5.14.21-150400.24.18-default) and afterwards to a readonly filesystem. A reboot is necessary to get a writable filesystem again. Interesting is, that balances are running, if executed with steps (with musage or dusage) scrubs doesn't show any errors on the filesystem. The only problem could be that internal space is almost full, if i interpret the output correctly: Label: 'boot1' uuid: 42e9a4d7-878e-457a-ab99-98106b1b556c Total devices 1 FS bytes used 724.80MiB devid 1 size 1.00GiB used 927.00MiB path /dev/mapper/system-boot1 But i can't reduce the space with the incremental balances. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190256] Keyboard not working after cold-boot on ASUS Zenbook 14 UM425UA with Tumbleweed 20210904
by bugzilla_noreply＠suse.com 09 Nov '22

09 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1190256 https://bugzilla.suse.com/show_bug.cgi?id=1190256#c65 Phi <comphi(a)protonmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |comphi(a)protonmail.com --- Comment #65 from Phi <comphi(a)protonmail.com> --- Hello, my Zenbook has the same issue. cat /sys/class/dmi/id/product_name gives ZenBook UX325SA_UM325SA cat /sys/class/dmi/id/board_vendor gives ASUSTek COMPUTER INC. It would be nice if you could add them to the patch as well. Thanks -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202138] PowerPC machine crashes frequently after upgrading to Leap 15.4
by bugzilla_noreply＠suse.com 09 Nov '22

09 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1202138 https://bugzilla.suse.com/show_bug.cgi?id=1202138#c31 --- Comment #31 from Michal Suchanek <msuchanek(a)suse.com> --- What kind of hardware is powerqaworker-qam-1.qa.suse.de? So far the problematic workers were POWER8 which use the old KVM code which gets very little testing upstream. Further, the problematic workers use 'openpower' firmware. That's some specific firmware different from what most machines use, and the little testing that is done by upstream on POWER8 likely happens on different firmware that also supports PowerVM. Finally the virtualization team does not provide any support for KVM on Power at all. Any support we have is best-effort. I don't have any POWER8 hardware capable of running KVM available. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204315] [RPi] Kernel 6.0 - [drm] *ERROR* could not acquire memory range
by bugzilla_noreply＠suse.com 09 Nov '22

09 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204315 Thomas Zimmermann <tzimmermann(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |tzimmermann(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193064] New: Touchpad doesn't work on Lenovo Yoga Slim7
by bugzilla_noreply＠suse.com 09 Nov '22

09 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1193064 Bug ID: 1193064 Summary: Touchpad doesn't work on Lenovo Yoga Slim7 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: 64bit OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: suse(a)rop.cx QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Touchpad doesn't work on Lenovo Yoga Slim7 That problem on Leap 15.3 and Tumbleweed (also in RHEL 9 beta) And some bugs on Fedora (it failed to start after sleep, but at all is working), so probably problem more on kernel side -- You are receiving this mail because: You are the assignee for the bug.

1 43

[Bug 1205198] LED not working on ASUS AC51 wireless USB adapter (MT7610U chipset) using Mediatek driver
by bugzilla_noreply＠suse.com 09 Nov '22

09 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205198 https://bugzilla.suse.com/show_bug.cgi?id=1205198#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ray.jantz(a)gmail.com, | |tiwai(a)suse.com Flags| |needinfo?(ray.jantz(a)gmail.c | |om) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Unless it's a regression, it's rather a thing to be reported to the upstream. Could you try to report it the upstream, e.g. linux-wireless ML? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1194086] Touchpad scrolling is not working on some boots
by bugzilla_noreply＠suse.com 09 Nov '22

09 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1194086 https://bugzilla.suse.com/show_bug.cgi?id=1194086#c50 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED CC| |joan.torres(a)suse.com Resolution|--- |FIXED --- Comment #50 from Takashi Iwai <tiwai(a)suse.com> --- Joan kindly tested the latest status with his laptop, and 6.0.x kernel worked without the patch. So the workaround seems superfluous nowadays. Let's drop the patch now. Once when the problem reappears, we can rethink. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205198] New: LED not working on ASUS AC51 wireless USB adapter (MT7610U chipset) using Mediatek driver
by bugzilla_noreply＠suse.com 08 Nov '22

08 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205198 Bug ID: 1205198 Summary: LED not working on ASUS AC51 wireless USB adapter (MT7610U chipset) using Mediatek driver 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: ray.jantz(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:106.0) Gecko/20100101 Firefox/106.0 Build Identifier: The activity LED on my ASUS AC51 wireless USB adapter does not flash when there is link activity. Everything else works - the adapter connects to wireless networks, but the LED never flashes. The LED works fine in Windows 10. Reproducible: Always Steps to Reproduce: 1. Plug ASUS AC51 adapter into a USB port. 2. No need to install a driver (driver is in-kernel) 3.(Optional) reboot 4. Connect to wireless network. 5. Open a browser and bring up a web page. Actual Results: The activity LED on the AC51 never flashes even though there is network activity. Expected Results: The activity LED on the AC51 should flash when there is network activity. The OS is Opensuse Tumbleweed 6.0.5-1-default. The info from lsusb is: ASUSTek Computer, Inc. AC51 802.11a/b/g/n/ac Wireless Adapter [Mediatek MT7610U] Bus 001 Device 003: ID 0b05:17d1 ASUSTek Computer, Inc. AC51 802.11a/b/g/n/ac Wireless Adapter [Mediatek MT7610U] I have checked the kernel config file and CONFIG_MT76_LEDS=y is set. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189172] USB CDC-ACM device keeps disconnecting and reconnecting
by bugzilla_noreply＠suse.com 08 Nov '22

08 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1189172 https://bugzilla.suse.com/show_bug.cgi?id=1189172#c9 --- Comment #9 from Marc Balmer <marc(a)msys.ch> --- It seem somehow to be related to the USB controller in use. On an IBM SurePOS 300 with UHCI, I have not issues. On EHCI and XHCI controllers it seems not to work. Also there are two hardware versions of the 1472g base station that use different CPUs. So there is quite some variations to check... -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189172] USB CDC-ACM device keeps disconnecting and reconnecting
by bugzilla_noreply＠suse.com 08 Nov '22

08 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1189172 https://bugzilla.suse.com/show_bug.cgi?id=1189172#c8 --- Comment #8 from Marc Balmer <marc(a)msys.ch> --- The scanner is operation as long as the machine is in the grub bootloader. As soon as the kernel boots, the scanner goes into a non-operational mode. There must be a bug in the cdc_acm driver/subsystem, that was introduced with openSUSE Leap 15.3 that that persists till today. atm, the machine is running the 5.14.21-150400.24.28-default kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189172] USB CDC-ACM device keeps disconnecting and reconnecting
by bugzilla_noreply＠suse.com 08 Nov '22

08 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1189172 https://bugzilla.suse.com/show_bug.cgi?id=1189172#c7 --- Comment #7 from Marc Balmer <marc(a)msys.ch> --- Setting the ID_MM_DEVICE_IGNORE flag does not change anything. In fact, I even deinstalled ModemManager, no change either. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189172] USB CDC-ACM device keeps disconnecting and reconnecting
by bugzilla_noreply＠suse.com 08 Nov '22

08 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1189172 Marc Balmer <marc(a)msys.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|Leap 15.3 |Leap 15.4 OS|openSUSE Leap 15.3 |openSUSE Leap 15.4 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1199661] New: amd-pstate CPU Performance Scaling Driver
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1199661 Bug ID: 1199661 Summary: amd-pstate CPU Performance Scaling Driver Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Enhancement Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: reiokorn(a)tutanota.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, is there an easy way to activate the new amd-pstate driver on Tumbleweed? I've tried: kernel-parameters: amd_pstate.replace=1 and amd_pstate.shared_mem=1 additionally I created a file named /etc/modules-load.d/amd-pstate.conf inside: # Load amd pstate at boot amd_pstate However it still defaults to: cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver acpi-cpufreq Anything I'm missing here? Thanks for your help -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 1203539] New: Boot hangs with update to kernel 5.14.21-15040.24.21-default
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1203539 Bug ID: 1203539 Summary: Boot hangs with update to kernel 5.14.21-15040.24.21-default 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: jcarricksmith(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 861545 --> https://bugzilla.suse.com/attachment.cgi?id=861545&action=edit Outputs from journalctl -b -? After the latest kernel update, when booting the system the load stalls after the message "Apparmor profiles loaded" is shown on the boot screen. After a pause both the CAPS Lock and NUM Lock lights flash together. The only way to recover from the situation is to hold the power button down. Booting 5.14.21-150400.24.18-default works fine. In the attachment there is the output from a boot on ...24.21-... (badjournal) and the output from good session on ...24.18-... (goodjournal) Many thanks John -- You are receiving this mail because: You are the assignee for the bug.

1 21

[Bug 1199661] Autoload amd-pstate CPU Performance Scaling Driver
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1199661 https://bugzilla.suse.com/show_bug.cgi?id=1199661#c18 Giovanni Gherdovich <giovanni.gherdovich(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Flags|needinfo?(reiokorn@tutanota | |.com) | --- Comment #18 from Giovanni Gherdovich <giovanni.gherdovich(a)suse.com> --- Closing as per comment 17. Thanks Takashi and Boris for helping the user out. The commit fixing this problem is fbd74d16890b9f5d08ea69b5282b123c894f8860 (" ACPI: CPPC: Fix enabling CPPC on AMD systems with shared memory") from Linux v5.19, which has now been available on Tumbleweed for a while. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204786] Boot is hanging when intel Ethernet Controller I225-LM [8086:15f2] is enabled
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204786 https://bugzilla.suse.com/show_bug.cgi?id=1204786#c12 --- Comment #12 from Bechir BEN KAHLA <bechir.kahla(a)suse.com> --- Created attachment 862688 --> https://bugzilla.suse.com/attachment.cgi?id=862688&action=edit ethernet_nic_hang_issue_sysrq_logs Hello please find attached the requested logs. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204786] Boot is hanging when intel Ethernet Controller I225-LM [8086:15f2] is enabled
by bugzilla_noreply＠suse.com 04 Nov '22

04 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204786 https://bugzilla.suse.com/show_bug.cgi?id=1204786#c11 --- Comment #11 from Bechir BEN KAHLA <bechir.kahla(a)suse.com> --- Created attachment 862659 --> https://bugzilla.suse.com/attachment.cgi?id=862659&action=edit Boot logs with 15sp5 kernel Boot logs with 15sp4 kernel Linux version 5.14.21-150500.33.gc8fa035-default -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204786] Boot is hanging when intel Ethernet Controller I225-LM [8086:15f2] is enabled
by bugzilla_noreply＠suse.com 04 Nov '22

04 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204786 https://bugzilla.suse.com/show_bug.cgi?id=1204786#c10 --- Comment #10 from Bechir BEN KAHLA <bechir.kahla(a)suse.com> --- (In reply to Takashi Iwai from comment #9) > Thanks. The kernel log doesn't show anything doubtful through a quick > glance. > > Then can you try to get the stack traces of the tasks via alt-sysrq-t? > Try to enable the all sysrq beforehand (e.g. pass "sysrq_always_enabled" > boot option). I talked with Thomas Bogendoerfer about the issue and he advised me to test with the kernel from SLES15sp5 as it has a closer igc driver sources to upstream. Even with that kernel the issue is reproduced, log are attached, but does not have anything relevant on it as well. The only thing is that with the kernel from SLES15SP5 the problem is less frequent to happen. I am trying to reproduce and as soon as I reproduce the issue I will collect the stack traces from the different tasks with sysrq -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205046] New: kernel panic Hard lockup
by bugzilla_noreply＠suse.com 04 Nov '22

04 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205046 Bug ID: 1205046 Summary: kernel panic Hard lockup Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: strangerover2002(a)netscape.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 862654 --> http://bugzilla.opensuse.org/attachment.cgi?id=862654&action=edit screenshot1 Using a dell 2 in 1 laptop 12 gen intel i7-1255U Using vmlinux-5.14.21-150400.24.21-default.gz linux boots as normal Using vmlinux-5.14.21-150400.24.28-default.gz linux stops at bootup and shows the message ---[ end Kernel panic - not syncing: Hard LOCKUP ] --- The screenshot show the debug on the laptop Both kernels work on another computer, so I suspect this is specific to my brand new laptop -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 1204786] Boot is hanging when intel Ethernet Controller I225-LM [8086:15f2] is enabled
by bugzilla_noreply＠suse.com 04 Nov '22

04 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204786 https://bugzilla.suse.com/show_bug.cgi?id=1204786#c9 --- Comment #9 from Takashi Iwai <tiwai(a)suse.com> --- Thanks. The kernel log doesn't show anything doubtful through a quick glance. Then can you try to get the stack traces of the tasks via alt-sysrq-t? Try to enable the all sysrq beforehand (e.g. pass "sysrq_always_enabled" boot option). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205035] Freeze on booting, can only boot in recovery mode
by bugzilla_noreply＠suse.com 04 Nov '22

04 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205035 http://bugzilla.opensuse.org/show_bug.cgi?id=1205035#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com Flags| |needinfo?(tau0(a)tutanota.com | |) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Can you figure out which kernel version started showing the problem? You can find older packages (up to one month ago or so) in TW history repo, http://download.opensuse.org/history/ If you need older kernels, there are my kernel builds found in OBS home:tiwai:kernel:5.19, home:tiwai:kernel:5.18, home:tiwai:kernel:5.17, ... Note that my kernel packages are unofficial builds, hence you'd need to turn off Secure Boot if it's enabled. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204786] Boot is hanging when intel Ethernet Controller I225-LM [8086:15f2] is enabled
by bugzilla_noreply＠suse.com 04 Nov '22

04 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204786 https://bugzilla.suse.com/show_bug.cgi?id=1204786#c8 --- Comment #8 from Bechir BEN KAHLA <bechir.kahla(a)suse.com> --- Created attachment 862653 --> https://bugzilla.suse.com/attachment.cgi?id=862653&action=edit Boot logs with 15sp4 kernel Boot logs for the test done with latest kernel from OBS Kernel:SLE15-SP4 repo : Linux version 5.14.21-150400.271.gfcd75f5-default -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204786] Boot is hanging when intel Ethernet Controller I225-LM [8086:15f2] is enabled
by bugzilla_noreply＠suse.com 04 Nov '22

04 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204786 https://bugzilla.suse.com/show_bug.cgi?id=1204786#c7 --- Comment #7 from Bechir BEN KAHLA <bechir.kahla(a)suse.com> --- (In reply to Takashi Iwai from comment #6) > Could you check whether it's a regression in the update kernel? That is, > install the old Leap 15.4 GA kernel and confirm the behavior. > > Also, please check with the latest kernel in OBS Kernel:SLE15-SP4 repo, too. > http://download.opensuse.org/repositories/Kernel:/SLE15-SP4/pool/ Tested with the latest kernel in OBS Kernel:SLE15-SP4 repo and the issue is reproduced. Boot log attached -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205035] Freeze on booting, can only boot in recovery mode
by bugzilla_noreply＠suse.com 04 Nov '22

04 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205035 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Basesystem |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 1205032] New: [Build 20221103] LTP: test fails in setitimer01
by bugzilla_noreply＠suse.com 04 Nov '22

04 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205032 Bug ID: 1205032 Summary: [Build 20221103] LTP: test fails in setitimer01 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/2853408/modules/seti timer01/steps/7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation setitimer01.c:73: TPASS: sys_setitimer(tc->which, value, ovalue) passed setitimer01.c:80: TFAIL: Ending counters are out of range setitimer01.c:89: TPASS: Child received signal: SIGPROF Failed. Test took approximately 0.169252419000259 seconds Some test output could not be parsed: 8 lines were ignored. openQA test in scenario opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos-ltp-syscalls@uefi_virtio-2G fails in [setitimer01](https://openqa.opensuse.org/tests/2853408/modules/setitimer01/… ## Test suite description ## Reproducible Fails since (at least) Build [20221021](https://openqa.opensuse.org/tests/2826982) ## Expected result Last good: [20221020](https://openqa.opensuse.org/tests/2825305) (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 1

[Bug 1204342] MATE CPU Frequency Monitoring stuck at lowest CPU speed
by bugzilla_noreply＠suse.com 03 Nov '22

03 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204342 http://bugzilla.opensuse.org/show_bug.cgi?id=1204342#c4 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |X11 Applications Assignee|kernel-bugs(a)opensuse.org |sor.alexei(a)meowr.ru Flags|needinfo?(llrainey15@gmail. | |com) | --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- OK, then let's try to reassign to MATE OBS project maintainer. If it turned out to be a kernel issue, please reassign back. Thanks. -- You are receiving this mail because: You are the assignee for the bug.

1 0