April 2024 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1223544] New: kernel config: enable CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG
by bugzilla_noreply＠suse.com 29 May '24

29 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223544 Bug ID: 1223544 Summary: kernel config: enable CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG 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: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Systemd wants to have CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG to enable signed Verity images: https://github.com/systemd/systemd/blob/main/README#L131 Any chance we can enable that (and potentially other settings we missed) in TW kernels to leverage systemd's full potential? -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1211428] New: Steam deck speaker is quiet.
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1211428 Bug ID: 1211428 Summary: Steam deck speaker is quiet. 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: monkeyboyted(a)yahoo.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi everyone, Steam deck speakers finally works in both speakers. Speaker-test works. However, I also notice the sound is quiet compared to SteamOS. Can you fix it? speaker-test -Dplughw:1,1 -c2 Linux steamdeck.lan 6.4.0-rc2-1.g679133f-default #1 SMP PREEMPT_DYNAMIC Sun May 14 21:09:47 UTC 2023 (679133f) x86_64 x86_64 x86_64 GNU/Linux LSB Version: n/a Distributor ID: openSUSE Description: openSUSE Tumbleweed Release: 20230514 Codename: n/a -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 1219132] New: [Build 20240123] [6.7.1] Sysctl Sysctl_kernel_sched_energy_aware
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1219132 Bug ID: 1219132 Summary: [Build 20240123] [6.7.1] Sysctl Sysctl_kernel_sched_energy_aware Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3889391/modules/Sysc tl/steps/136 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 Target Milestone: --- Found By: openQA Blocker: Yes ## Observation # Test messages # Sysctl_kernel_sched_energy_aware # failure: ValueError: invalid literal for int() with base 10: '' Possibly this is a kernel issue - possibly the kernel just no longer exposes this and the test should not care. Please advise openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-sys-param-check@64bit fails in [Sysctl](https://openqa.opensuse.org/tests/3889391/modules/Sysctl/steps/136) ## Test suite description RAM size is set to 2048, some kernel parameters change with total RAM https://github.com/openSUSE/sys-param-check ## Reproducible Fails since (at least) Build [20240123](https://openqa.opensuse.org/tests/3888589) ## Expected result Last good: [20240122](https://openqa.opensuse.org/tests/3886345) (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 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 17 May '24

17 May '24

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 1

[Bug 1223109] New: Booting issue after upgrade to kernel-default-6.8.6-1.1
by bugzilla_noreply＠suse.com 16 May '24

16 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223109 Bug ID: 1223109 Summary: Booting issue after upgrade to kernel-default-6.8.6-1.1 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: bkaczynski(a)posteo.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 874370 --> https://bugzilla.suse.com/attachment.cgi?id=874370&action=edit hwinfo Disclaimer: This is my first bug report on Bugzilla and I may not have the necessary technical knowledge to address all concerns. The response on the forum led me here [1] I am experiencing a problem with booting the system after updating the kernel to the kernel-default-6.8.6-1.1 version. I am attaching a picture of the moment when the system hangs. I am also including results of the `inxi -Faz` command[2] from after restoring to the previous version of the system. [1] https://forums.opensuse.org/t/boot-issue-following-recent-kernel-update/174… [2] https://paste.opensuse.org/pastes/2db537ab61eb -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1213148] New: Atomisp results in tumbleweed being unable to boot on some atom computers since kernel 6.2
by bugzilla_noreply＠suse.com 02 May '24

02 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1213148 Bug ID: 1213148 Summary: Atomisp results in tumbleweed being unable to boot on some atom computers since kernel 6.2 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: catice567(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Since kernel 6.2, my Tumbleweed refuses to boot because of intel isp. Ubuntu had this problem but they fixed it by disabling atomisp. I have a request to the openSUSE kernel maintainers: Can you please disable atomisp in your kernel, especially since this will affect Leap later on next year? -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1214133] bluetooth disabled after update to 20230808, firmware load for mediatek/BT_RAM_CODE_MT7922_1_1_hdr.bin failes
by bugzilla_noreply＠suse.com 30 Apr '24

30 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1214133 Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206843] Lenovo T14s Gen3 AMD resume from sleep broken
by bugzilla_noreply＠suse.com 30 Apr '24

30 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1206843 Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1198835] Wrong work of Wi-Fi card MT7921
by bugzilla_noreply＠suse.com 30 Apr '24

30 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1198835 Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193064] Elan Touchpad doesn't work on Lenovo Yoga Slim7
by bugzilla_noreply＠suse.com 30 Apr '24

30 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1193064 Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188896] "BUG: Bad rss-counter state mm:00000000e555b579 type:MM_FILEPAGES val:-256" during build of cross-epiphany-gcc11-bootstrap
by bugzilla_noreply＠suse.com 30 Apr '24

30 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1188896 Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193124] tumbleweed release 20211124 with kernel 5.15.3 bluetooth fail
by bugzilla_noreply＠suse.com 30 Apr '24

30 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1193124 Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1186320] Current driver (module pl2303.ko) for Prolific chip 23a3 does not work on Leap 15.2 kernel
by bugzilla_noreply＠suse.com 30 Apr '24

30 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1186320 Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1175296] network regression with a Realtek RTL8111E network chip
by bugzilla_noreply＠suse.com 30 Apr '24

30 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1175296 Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189946] [trackerbug] Ancient patch cleanup
by bugzilla_noreply＠suse.com 30 Apr '24

30 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1189946 Bug 1189946 depends on bug 1189970, which changed state. Bug 1189970 Summary: cleanup: remove or document patches.suse/scsi-retry-alua-transition-in-progress https://bugzilla.suse.com/show_bug.cgi?id=1189970 What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1222345] Laptop wakes from suspend once the user closes the lid
by bugzilla_noreply＠suse.com 30 Apr '24

30 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222345 https://bugzilla.suse.com/show_bug.cgi?id=1222345#c14 --- Comment #14 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Jiri Slaby from comment #13) > It is usually the touchpad. Was in my case (T14s and P14s) too. > > https://wiki.archlinux.org/title/ > Lenovo_ThinkPad_T14s_(AMD)_Gen_3#Disable_wakeup_from_sleep_on_touchpad_activi > ty Do you mean that it can be touchpad that incorrectly wakes up at the lid close? My T14s gen 3 doesn't seem showing the problem by some reason. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1222345] Laptop wakes from suspend once the user closes the lid
by bugzilla_noreply＠suse.com 30 Apr '24

30 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222345 https://bugzilla.suse.com/show_bug.cgi?id=1222345#c13 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com --- Comment #13 from Jiri Slaby <jslaby(a)suse.com> --- It is usually the touchpad. Was in my case (T14s and P14s) too. https://wiki.archlinux.org/title/Lenovo_ThinkPad_T14s_(AMD)_Gen_3#Disable_w… -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1223109] Booting issue after upgrade to kernel-default-6.8.6-1.1
by bugzilla_noreply＠suse.com 30 Apr '24

30 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1223109 https://bugzilla.suse.com/show_bug.cgi?id=1223109#c4 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bkaczynski(a)posteo.net Flags| |needinfo?(bkaczynski@posteo | |.net) Status|NEW |IN_PROGRESS --- Comment #4 from Jiri Slaby <jslaby(a)suse.com> --- The fix is at: https://lore.kernel.org/intel-wired-lan/20240417190320.3159360-1-vitaly.lif… Now pushing. Could you test Kernel:stable once it builds? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193599] intel_dp_detect [i915]] *ERROR* LSPCON init failed on port D
by bugzilla_noreply＠suse.com 29 Apr '24

29 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1193599 https://bugzilla.suse.com/show_bug.cgi?id=1193599#c49 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Flags|needinfo?(opendreas(a)gmail.c | |om) | --- Comment #49 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Andreas from comment #44) > > I'm building a test kernel for SLE15-SP6 in OBS home:tiwai:bsc1193599-sp6 > > repo. > > The package will appear later at > > http://download.opensuse.org/repositories/home:/tiwai:/bsc1193599-sp6/pool/ > > > > Please give it a try later. > The patch works, the errors have disappeared. OK, now I pushed those two patches to SLE15-SP6 branch, so that they'll be included in the Leap 15.6 update kernel. (They'll be missing in the installer kernel, though.) If any other crashes happen even with those patches, they are basically different issues, and better to be tracked in other bug reports. Please open another report in such a case. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1221607] New: Slowroll keeps reinstalling kernel and virtualbox on every zypper dup
by bugzilla_noreply＠suse.com 29 Apr '24

29 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1221607 Bug ID: 1221607 Summary: Slowroll keeps reinstalling kernel and virtualbox on every zypper dup 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: llrainey15(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- zypper dup keeps installing the same 2 entries over and over slowroll:~ # zypper ref ; zypper -n dup Repository 'base-non-oss' is up to date. Repository 'base-oss' is up to date. Repository 'h264' is up to date. Repository 'packman' is up to date. Repository 'update' is up to date. All repositories have been refreshed. Loading repository data... Reading installed packages... Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Computing distribution upgrade... The following 2 NEW packages are going to be installed: kernel-default-6.7.4-1.1 virtualbox-kmp-default-7.0.14_k6.7.4_1-2.1 The following package requires a system reboot: kernel-default-6.7.4-1.1 2 new packages to install. Overall download size: 166.3 MiB. Already cached: 0 B. After the operation, additional 242.7 MiB will be used. Note: System reboot required. Continue? [y/n/v/...? shows all options] (y): y Retrieving: kernel-default-6.7.4-1.1.x86_64 (base-oss) (1/2), 165.8 MiB Retrieving: kernel-default-6.7.4-1.1.x86_64.rpm .............[done (39.2 MiB/s)] Retrieving: virtualbox-kmp-default-7.0.14_k6.7.4_1-2.1.x86_64 (base-oss) (2/2), 546.5 KiB Retrieving: virtualbox-kmp-default-7.0.14_k6.7.4_1-2.1.x86_64.[done (1.9 MiB/s)] Checking for file conflicts: .............................................[done] dracut[I]: Executing: /usr/bin/dracut -f /boot/initrd-6.7.4-1-default 6.7.4-1-default Lines delete dracut[I]: *** Creating initramfs image file '/boot/initrd-6.7.4-1-default' done *** CA enrolled. Skip /etc/uefi/certs/1F673297.crt (1/2) Installing: kernel-default-6.7.4-1.1.x86_64 ........................[done] (2/2) Installing: virtualbox-kmp-default-7.0.14_k6.7.4_1-2.1.x86_64 ......[done] Running post-transaction scripts .........................................[done] Loading repository data... Reading installed packages... Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Computing distribution upgrade... Nothing to do. Mon Mar 18 07:15:26 CDT 2024 slowroll:~ # Broadcast message from root@slowroll on pts/5 (Mon 2024-03-18 07:16:41 CDT): The system will reboot now! Connection to llr2 closed by remote host. Connection to llr2 closed. llrainey@LLR2:~> t2x 06 Last login: Sun Mar 17 06:43:50 CDT 2024 from 10.0.2.2 on ssh Have a lot of fun... slowroll:~ # zypper ref ; zypper -n dup Repository 'base-non-oss' is up to date. Repository 'base-oss' is up to date. Repository 'h264' is up to date. Repository 'packman' is up to date. Repository 'update' is up to date. All repositories have been refreshed. Loading repository data... Reading installed packages... Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Computing distribution upgrade... The following 2 NEW packages are going to be installed: kernel-default-6.7.4-1.1 virtualbox-kmp-default-7.0.14_k6.7.4_1-2.1 The following package requires a system reboot: kernel-default-6.7.4-1.1 2 new packages to install. Overall download size: 166.3 MiB. Already cached: 0 B. After the operation, additional 242.7 MiB will be used. Note: System reboot required. Continue? [y/n/v/...? shows all options] (y): y Retrieving: kernel-default-6.7.4-1.1.x86_64 (base-oss) (1/2), 165.8 MiB Retrieving: kernel-default-6.7.4-1.1.x86_64.rpm .............[done (39.2 MiB/s)] Retrieving: virtualbox-kmp-default-7.0.14_k6.7.4_1-2.1.x86_64 (base-oss) (2/2), 546.5 KiB Retrieving: virtualbox-kmp-default-7.0.14_k6.7.4_1-2.1.x86_64.[done (1.9 MiB/s)] Checking for file conflicts: .............................................[done] dracut[I]: Executing: /usr/bin/dracut -f /boot/initrd-6.7.4-1-default 6.7.4-1-default Lines delete dracut[I]: *** Creating initramfs image file '/boot/initrd-6.7.4-1-default' done *** CA enrolled. Skip /etc/uefi/certs/1F673297.crt (1/2) Installing: kernel-default-6.7.4-1.1.x86_64 ........................[done] (2/2) Installing: virtualbox-kmp-default-7.0.14_k6.7.4_1-2.1.x86_64 ......[done] Running post-transaction scripts .........................................[done] Loading repository data... Reading installed packages... Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Computing distribution upgrade... Nothing to do. Mon Mar 18 07:15:26 CDT 2024 slowroll:~ # Broadcast message from root@slowroll on pts/5 (Mon 2024-03-18 07:16:41 CDT): The system will reboot now! Connection to llr2 closed by remote host. Connection to llr2 closed. llrainey@LLR2:~> t2x 06 Last login: Mon Mar 18 07:14:23 CDT 2024 from 10.0.2.2 on ssh Have a lot of fun... slowroll:~ # zypper ref ; zypper -n dup Repository 'base-non-oss' is up to date. Repository 'base-oss' is up to date. Repository 'h264' is up to date. Repository 'packman' is up to date. Repository 'update' is up to date. All repositories have been refreshed. Loading repository data... Reading installed packages... Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Computing distribution upgrade... The following 2 NEW packages are going to be installed: kernel-default-6.7.4-1.1 virtualbox-kmp-default-7.0.14_k6.7.4_1-2.1 The following package requires a system reboot: kernel-default-6.7.4-1.1 2 new packages to install. Overall download size: 166.3 MiB. Already cached: 0 B. After the operation, additional 242.7 MiB will be used. Note: System reboot required. Continue? [y/n/v/...? shows all options] (y): y Retrieving: kernel-default-6.7.4-1.1.x86_64 (base-oss) (1/2), 165.8 MiB Retrieving: kernel-default-6.7.4-1.1.x86_64.rpm .............[done (30.6 MiB/s)] Retrieving: virtualbox-kmp-default-7.0.14_k6.7.4_1-2.1.x86_64 (base-oss) (2/2), 546.5 KiB Retrieving: virtualbox-kmp-default-7.0.14_k6.7.4_1-2.1.x86_64.[done (2.1 MiB/s)] Checking for file conflicts: .............................................[done] dracut[I]: Executing: /usr/bin/dracut -f /boot/initrd-6.7.4-1-default 6.7.4-1-default Lines Delete dracut[I]: *** Creating initramfs image file '/boot/initrd-6.7.4-1-default' done *** CA enrolled. Skip /etc/uefi/certs/1F673297.crt (1/2) Installing: kernel-default-6.7.4-1.1.x86_64 ........................[done] (2/2) Installing: virtualbox-kmp-default-7.0.14_k6.7.4_1-2.1.x86_64 ......[done] Running post-transaction scripts .........................................[done] Loading repository data... Reading installed packages... Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Computing distribution upgrade... Nothing to do. Mon Mar 18 07:18:32 CDT 2024 -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1222756] New: Bluetooth: auto-connected devices are not shown as connected
by bugzilla_noreply＠suse.com 27 Apr '24

27 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222756 Bug ID: 1222756 Summary: Bluetooth: auto-connected devices are not shown as connected 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: i(a)guoyunhe.me QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When a paired Bluetooth headset was auto-connected, the device works but system tray and bluetoothctl are not showing it as connected: bluetoothctl info 64:68:76:1C:E3:67 Device 64:68:76:1C:E3:67 (public) Name: 漫步者•花再 Free Pro Alias: 漫步者•花再 Free Pro Class: 0x00240404 (2360324) Icon: audio-headset Paired: yes Bonded: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: SDP (00000001-0000-1000-8000-00805f9b34fb) UUID: Serial Port (00001101-0000-1000-8000-00805f9b34fb) UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb) UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Cont.. (0000110f-0000-1000-8000-00805f9b34fb) UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb) UUID: Generic Audio (00001203-0000-1000-8000-00805f9b34fb) UUID: Vendor specific (66666666-6666-6666-6666-666666666666) UUID: Vendor specific (edf00000-edfe-dfed-fedf-edfedfedfedf) Battery Percentage: 0x32 (50) -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1221504] New: bluetooth errors on every kernel starting
by bugzilla_noreply＠suse.com 26 Apr '24

26 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1221504 Bug ID: 1221504 Summary: bluetooth errors on every kernel starting Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: opendreas(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I have a Dell Precision 7530 with Intel Wireless-AC 9260 Bluetooth Adapter and kernel 6.4.0-150600.9.2. Errors constantly appear when booting the system, but bluetooth works with my headphones, although there are some audio artifacts at the beginning when playing sound. Mär 16 17:49:38 precision bluetoothd[1073]: Bluetooth daemon 5.71 Mär 16 17:49:38 precision bluetoothd[1073]: Starting SDP server Mär 16 17:49:38 precision bluetoothd[1073]: src/plugin.c:plugin_init() System does not support csip plugin Mär 16 17:49:38 precision bluetoothd[1073]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled Mär 16 17:49:38 precision bluetoothd[1073]: src/plugin.c:plugin_init() System does not support micp plugin Mär 16 17:49:38 precision bluetoothd[1073]: src/plugin.c:plugin_init() System does not support vcp plugin Mär 16 17:49:38 precision bluetoothd[1073]: src/plugin.c:plugin_init() System does not support mcp plugin Mär 16 17:49:38 precision bluetoothd[1073]: src/plugin.c:plugin_init() System does not support bass plugin Mär 16 17:49:38 precision bluetoothd[1073]: src/plugin.c:plugin_init() System does not support bap plugin Mär 16 17:49:38 precision bluetoothd[1073]: src/plugin.c:plugin_init() System does not support admin plugin Mär 16 17:49:38 precision bluetoothd[1073]: Bluetooth management interface 1.22 initialized Mär 16 17:49:38 precision dbus-daemon[1074]: [system] Activating systemd to hand-off: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.1' (uid=0 pid=1073 comm="/usr/lib/bluetooth/bluetoothd ") Mär 16 17:49:38 precision bluetoothd[1073]: src/adapter.c:reset_adv_monitors_complete() Failed to reset Adv Monitors: Failed (0x03) Mär 16 17:49:38 precision bluetoothd[1073]: Battery Provider Manager created Mär 16 17:49:38 precision bluetoothd[1073]: src/device.c:device_set_wake_support() Unable to set wake_support without RPA resolution Mär 16 17:49:38 precision bluetoothd[1073]: Failed to clear UUIDs: Failed (0x03) Mär 16 17:49:38 precision bluetoothd[1073]: Failed to add UUID: Failed (0x03) Mär 16 17:49:38 precision bluetoothd[1073]: Failed to add UUID: Failed (0x03) Mär 16 17:49:38 precision bluetoothd[1073]: Failed to add UUID: Failed (0x03) Mär 16 17:49:38 precision bluetoothd[1073]: Failed to add UUID: Failed (0x03) Mär 16 17:49:38 precision bluetoothd[1073]: Failed to add UUID: Failed (0x03) Mär 16 17:49:38 precision bluetoothd[1073]: Too small Add Device complete event Mär 16 17:49:38 precision bluetoothd[1073]: Failed to add UUID: Failed (0x03) Mär 16 17:49:38 precision (smartd)[1105]: smartd.service: Referenced but unset environment variable evaluates to an empty string: smartd_opts Looks like this is the error https://bugzilla.kernel.org/show_bug.cgi?id=217651 Here's a fix https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.gi… -- You are receiving this mail because: You are the assignee for the bug.

1 21

[Bug 1222946] New: raise default inotify instance limit
by bugzilla_noreply＠suse.com 26 Apr '24

26 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222946 Bug ID: 1222946 Summary: raise default inotify instance limit 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: obs(a)akr.yagii.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- especially when running Unison, I quite often experienced the following error: `Fatal error: exception Unix.Unix_error(Unix.EBADF, "set_nonblock", "")` Running "strace unison-fsmonitor" yielded: ``` fcntl(0, F_GETFL) = 0x802 (flags O_RDWR|O_NONBLOCK) fcntl(0, F_SETFL, O_RDWR|O_NONBLOCK) = 0 fcntl(1, F_GETFL) = 0x802 (flags O_RDWR|O_NONBLOCK) fcntl(1, F_SETFL, O_RDWR|O_NONBLOCK) = 0 inotify_init() = -1 EMFILE (Too many open files) fcntl(-1, F_GETFL) = -1 EBADF (Bad file descriptor) write(2, "Fatal error: exception Unix.Unix"..., 71Fatal error: exception Unix.Unix_error(Unix.EBADF, "set_nonblock", "")) = 71 exit_group(2) = ? +++ exited with 2 +++ ``` Sometimes closing open IDEs or Firefox has helped, but the culprit seems to be the standard value of fs.inotify.max_user_instances = 128 After doubling the number, I was able to use Unison, again. Others have observed this issue, too: https://intellij-support.jetbrains.com/hc/en-us/articles/15268110231826-Ino… ---quote For an intelligent IDE, it is essential to be in the know about any external changes in files it working with - e.g. changes made by VCS, or build tools, or code generators, etc. For that reason, the IntelliJ platform spins a background process to monitor such changes. The method it uses is platform-specific, and on Linux, it is the Inotify facility. Before operating, inotify requires an "instance" to be initialized. While the default per-user limit of instances used to be high enough, a growing number of programs that also use inotify may lead to instance shortage - in which case file watcher will be unable to start. If this is the case, the limit may be temporarily increased by the following command: sudo sh -c "echo 256 > /proc/sys/fs/inotify/max_user_instances" Don't forget to restart the IDE afterward. ---quote My workaround at present is: `sysctl -w fs.inotify.max_user_instances=256 >> /etc/sysctl.d/unison.conf` This is also documented at https://github.com/bcpierce00/unison/issues/1019 -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1222946] raise default inotify instance limit
by bugzilla_noreply＠suse.com 26 Apr '24

26 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222946 https://bugzilla.suse.com/show_bug.cgi?id=1222946#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- The default value is hardcoded to 128 even in the latest upstream code, and I see no big gain to have an extra kernel config for defining it when an easy tuning knob with sysctl is already present. I bet the suggestion to the upstream would be declined by that reason, too. You can statically set the value in /etc/sysctl.d/* instead. e.g. unison package may contain such a sysctl snippet. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1223164] New: Unplugging charger while in s2idle sleep causes laptop to stop responding
by bugzilla_noreply＠suse.com 21 Apr '24

21 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1223164 Bug ID: 1223164 Summary: Unplugging charger while in s2idle sleep causes laptop to stop responding 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: misawalach00(a)seznam.cz QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Specs: Laptop Model: Lenovo Ideapad 5 PRO 14ARH7 CPU: Ryzen 7 6800HS Creator Edition GPU: Integrated: AMD Radeon 680M RAM: 16 GB Wifi Card: MEDIATEK MT7921 802.11ax PCI Express Wireless Network Adapter Storage: 1TB M.2 NVME WD PC SN810 SDCPNRY-1T00-1101 This laptop supports s2idle sleep only. When the laptop is in sleep mode, everything works properly, there is almost no battery drain. However, when I plug in or unplug my charger, the laptop will no longer responds to any inputs and can no longer be woken up. The keyboard backlight briefly flashes and the laptop starts producing heat and the only way to get out of sleep mode is to hold the power button for 5 seconds to forcefully shut it down. Alt + Sysrq + b does nothing. I have tried setting TLP_ENABLE=0 and rebooting. That does not seem to help. The only thing that changes is that now the fans spin up once the laptop gets stuck and the keyboard backlight no longer flashes. There are no errors present in journalctl -b -1 after rebooting. The last message is that the laptop successfully entered s2idle sleep mode. I have tried the Live environment of a different distribution according to a few tips online. Fedora 39 live environment does not have this issue. Either this bug is specific to this distribution or I messed something up with my installation. I could not figure out what could cause this. This issue is present on kernel versions 6.5, 6.6, 6.7 and 6.8. I haven't tried any other versions. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1222917] [Kernel Bug] Wrong bluetooth connection status in KDE Applet
by bugzilla_noreply＠suse.com 21 Apr '24

21 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222917 https://bugzilla.suse.com/show_bug.cgi?id=1222917#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Flags|needinfo?(egor.kuznetsov.26 | |(a)gmail.com) | Resolution|--- |FIXED --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- OK, let's close now :) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1222917] New: [Kernel Bug] Wrong bluetooth connection status in KDE Applet
by bugzilla_noreply＠suse.com 21 Apr '24

21 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222917 Bug ID: 1222917 Summary: [Kernel Bug] Wrong bluetooth connection status in KDE Applet 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: egor.kuznetsov.26(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Summary: After some kernel updates (seems from 6.8.2) bluetooth connection in KDE applet shows wrong status. If device connected, it works, but applet show, that device disconnected. Possible fix: I research kernel bugzilla and found this bug https://bugzilla.kernel.org/show_bug.cgi?id=218680 and see that patch was created, but at this moment it is not in upstream kernel branches. Can openSUSE kernel maintainers apply patch from Bagas Sanjaya (https://lore.kernel.org/all/20240404185022.1.Ic27505c8f1ca7d4a653b1dcc1b08c…) to openSUSE kernel? Thanks in advance for the answer! -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1220814] New: kernel 6.7.6-1-default Oops: unable to handle page faults and workqueue lockup (udev related?)
by bugzilla_noreply＠suse.com 21 Apr '24

21 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1220814 Bug ID: 1220814 Summary: kernel 6.7.6-1-default Oops: unable to handle page faults and workqueue lockup (udev related?) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: michael.burge77(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 873182 --> https://bugzilla.suse.com/attachment.cgi?id=873182&action=edit full journalctl of the third crash I have an old portable with a wonky dc power jack which tends to generate a few quick AC0<->BAT0 events in succession. Starting with kernel 6.7.6-1-default the system locks up. Log is full of ``` Mar 01 17:34:02 ost (udev-worker)[23694]: AC0: Process '/usr/sbin/tlp auto' terminated by signal KILL. Mar 01 17:34:02 ost (udev-worker)[23694]: AC0: Failed to wait for spawned command '/usr/sbin/tlp auto': Input/output error Mar 01 17:34:02 ost (udev-worker)[23694]: AC0: Failed to execute '/usr/sbin/tlp auto', ignoring: Input/output error Mar 01 17:34:17 ost (udev-worker)[24044]: AC0: Process '/usr/sbin/tlp auto' terminated by signal KILL. Mar 01 17:34:17 ost (udev-worker)[24044]: AC0: Failed to wait for spawned command '/usr/sbin/tlp auto': Input/output error Mar 01 17:34:17 ost (udev-worker)[24044]: AC0: Failed to execute '/usr/sbin/tlp auto', ignoring: Input/output error Mar 01 17:34:17 ost plasmashell[2682]: plasma-pk-updates: acPluggedChanged onBattery: false -> true Mar 01 17:34:17 ost kernel: BUG: unable to handle page fault for address: 0000000000007b8a Mar 01 17:34:17 ost kernel: #PF: supervisor read access in kernel mode Mar 01 17:34:17 ost kernel: #PF: error_code(0x0000) - not-present page ``` until it locks up with ``` Mar 01 18:11:29 ost kernel: note: kworker/11:5[23457] exited with irqs disabled Mar 01 18:11:50 ost systemd-logind[1443]: Power key pressed short. Mar 01 18:11:54 ost systemd-logind[1443]: Power key pressed short. Mar 01 18:11:55 ost systemd-logind[1443]: Power key pressed short. Mar 01 18:11:58 ost plasmashell[5912]: [5912:0301/181158.744595:ERROR:command_buffer_proxy_impl.cc(128)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer. Mar 01 18:12:05 ost systemd-logind[1443]: Power key pressed short. Mar 01 18:12:06 ost kernel: BUG: workqueue lockup - pool cpus=11 node=0 flags=0x0 nice=0 stuck for 37s! ``` at which point only holding down the power button works. -- You are receiving this mail because: You are the assignee for the bug.

1 14

[Bug 1222756] Bluetooth: auto-connected devices are not shown as connected
by bugzilla_noreply＠suse.com 20 Apr '24

20 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222756 https://bugzilla.suse.com/show_bug.cgi?id=1222756#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |i(a)guoyunhe.me, | |tiwai(a)suse.com Flags| |needinfo?(i(a)guoyunhe.me) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Could you try the latest 6.8.x kernel in OBS Kernel:stable repo? http://download.opensuse.org/repositories/Kernel:/stable/standard/ A possible fix has been already included in 6.8.7. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1222917] [Kernel Bug] Wrong bluetooth connection status in KDE Applet
by bugzilla_noreply＠suse.com 20 Apr '24

20 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222917 https://bugzilla.suse.com/show_bug.cgi?id=1222917#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(egor.kuznetsov.26 | |(a)gmail.com) CC| |egor.kuznetsov.26(a)gmail.com | |, tiwai(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- The fix is already contained in 6.8.7 kernel. Could you try the latest one in OBS Kernel:stable repo? http://download.opensuse.org/repositories/Kernel:/stable/standard/ -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1223083] Kernel:HEAD 6.9rc breaks iwlwifi on Thinkpad T480
by bugzilla_noreply＠suse.com 20 Apr '24

20 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1223083 https://bugzilla.suse.com/show_bug.cgi?id=1223083#c4 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |UPSTREAM Status|NEW |RESOLVED --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- Thanks for the info! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1223083] New: Kernel:HEAD 6.9rc breaks iwlwifi on Thinkpad T480
by bugzilla_noreply＠suse.com 20 Apr '24

20 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1223083 Bug ID: 1223083 Summary: Kernel:HEAD 6.9rc breaks iwlwifi on Thinkpad T480 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: seife(a)novell.slipkontur.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I'm running current Tumbleweed on my "new" Thinkpad T480 using iwlwifi. I have both KOTD kernel-default-6.9-rc and Tumbleweed's kernel-vanilla-6.8.x installed, the latter as a way to recover if KOTD breaks :-) Since the first 6.9-rc releases, my WIFI does not work. mixi:~ # uname -a Linux mixi 6.9.0-rc4-2.g4804f5c-default #1 SMP PREEMPT_DYNAMIC Mon Apr 15 08:48:25 UTC 2024 (4804f5c) x86_64 x86_64 x86_64 GNU/Linux mixi:~ # ip link set up dev wlp3s0 RTNETLINK answers: Invalid argument mixi:~ # rfkill ID TYPE DEVICE SOFT HARD 0 bluetooth tpacpi_bluetooth_sw blocked unblocked 1 wlan phy0 unblocked unblocked mixi:~ # ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host noprefixroute valid_lft forever preferred_lft forever 2: wlp3s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 92:df:96:3e:36:0b brd ff:ff:ff:ff:ff:ff permaddr 38:ba:f8:f4:ed:63 3: enp0s31f6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether 8c:16:45:fc:09:b0 brd ff:ff:ff:ff:ff:ff seife@mixi:~> dmesg|grep iwl [ 9.948811] iwlwifi 0000:03:00.0: Detected crf-id 0xbadcafe, cnv-id 0x10 wfpm id 0x80000000 [ 9.948978] iwlwifi 0000:03:00.0: PCI dev 24fd/0010, rev=0x230, rfid=0xd55555d5 [ 10.187732] iwlwifi 0000:03:00.0: loaded firmware version 36.ca7b901d.0 8265-36.ucode op_mode iwlmvm [ 10.637788] iwlwifi 0000:03:00.0: Detected Intel(R) Dual Band Wireless AC 8265, REV=0x230 [ 10.701153] iwlwifi 0000:03:00.0: base HW address: 38:ba:f8:f4:ed:63, OTP minor version: 0x4 [ 10.779246] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs' [ 10.784000] iwlwifi 0000:03:00.0 wlp3s0: renamed from wlan0 [ 17.419360] iwlwifi 0000:03:00.0: Registered PHC clock: iwlwifi-PTP, with index: 1 The dmesg regarding anything wifi (not only iwlwifi) does not differ from the working 6.8.x kernels, no additional error or missing line or anything. I have no idea how to debug this any further, I would not even know what to report upstream ;-) The Thinkpad T480 should still be in use in high numbers, so I wonder how I can be the only one seeing this issue? hwinfo for the card: 41: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: Mqes.ndpeucax6V1 Parent ID: hAO_.xdVuDfcpKg9 SysFS ID: /class/net/wlp3s0 SysFS Device Link: /devices/pci0000:00/0000:00:1c.6/0000:03:00.0 Hardware Class: network interface Model: "Ethernet network interface" Driver: "iwlwifi" Driver Modules: "iwlwifi" Device File: wlp3s0 HW Address: 92:df:96:3e:36:0b Permanent HW Address: 38:ba:f8:f4:ed:63 Link detected: no Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #1 (Ethernet controller) -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1223131] New: Disable WAN drivers
by bugzilla_noreply＠suse.com 19 Apr '24

19 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1223131 Bug ID: 1223131 Summary: Disable WAN drivers Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- We do not provide WAN in SLE at all (it lives in the -optional subpackage, so is Leap only). Provided: * no our customer apparently uses this, * is poorly maintained upstream (hdlc in particular), * it's unlikely TW/Leap users run this (but not impossible), * we diverge from SLE configs, we should consider disabling whole WAN in TW and Leap too. The proposed config change is: @@ -4217,20 +4217,7 @@ CONFIG_QTNFMAC=m CONFIG_QTNFMAC_PCIE=m CONFIG_MAC80211_HWSIM=m CONFIG_VIRT_WIFI=m -CONFIG_WAN=y -CONFIG_HDLC=m -CONFIG_HDLC_RAW=m -CONFIG_HDLC_RAW_ETH=m -CONFIG_HDLC_CISCO=m -CONFIG_HDLC_FR=m -CONFIG_HDLC_PPP=m -CONFIG_HDLC_X25=m -CONFIG_FRAMER=m -CONFIG_PCI200SYN=m -CONFIG_WANXL=m -CONFIG_PC300TOO=m -CONFIG_FARSYNC=m -CONFIG_LAPBETHER=m +# CONFIG_WAN is not set CONFIG_IEEE802154_DRIVERS=m CONFIG_IEEE802154_FAKELB=m # CONFIG_IEEE802154_AT86RF230 is not set @@ -4658,7 +4645,7 @@ CONFIG_SERIAL_MCTRL_GPIO=y CONFIG_SERIAL_NONSTANDARD=y # CONFIG_MOXA_INTELLIO is not set CONFIG_MOXA_SMARTIO=m -CONFIG_N_HDLC=m +# CONFIG_N_HDLC is not set CONFIG_IPWIRELESS=m CONFIG_N_GSM=m CONFIG_NOZOMI=m -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1221884] Kernel panics kworker/3:2
by bugzilla_noreply＠suse.com 19 Apr '24

19 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1221884 https://bugzilla.suse.com/show_bug.cgi?id=1221884#c3 Anthony Iliopoulos <ailiopoulos(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Anthony Iliopoulos <ailiopoulos(a)suse.com> --- closing as dup of 1220814. *** This bug has been marked as a duplicate of bug 1220814 *** -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1223109] Booting issue after upgrade to kernel-default-6.8.6-1.1
by bugzilla_noreply＠suse.com 19 Apr '24

19 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1223109 https://bugzilla.suse.com/show_bug.cgi?id=1223109#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |BjAlvestad(a)gmail.com --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- *** Bug 1222945 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1223083] Kernel:HEAD 6.9rc breaks iwlwifi on Thinkpad T480
by bugzilla_noreply＠suse.com 19 Apr '24

19 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1223083 https://bugzilla.suse.com/show_bug.cgi?id=1223083#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(seife(a)novell.slip | |kontur.de) CC| |seife(a)novell.slipkontur.de, | |tiwai(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- As it's a 6.9-rc regression, the best would be to contact with the upstream devs. Care to post to linux-wireless ML? You can get the regression tracking involved, too (for catching more attention). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1223134] New: Disable N_GSM
by bugzilla_noreply＠suse.com 19 Apr '24

19 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1223134 Bug ID: 1223134 Summary: Disable N_GSM Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- N_GSM is almost unmaintained and full of bugs: https://lore.kernel.org/all/DB9PR10MB5881D2170678C169FB42A423E0082@DB9PR10M… Esp. the 0day reported recently (bug 1222619). It is supposed to be used on special embedded devices only. So let's disable the line discipline. There is jsc#PED-8240 about the same for SLE. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1223109] Booting issue after upgrade to kernel-default-6.8.6-1.1
by bugzilla_noreply＠suse.com 19 Apr '24

19 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1223109 https://bugzilla.suse.com/show_bug.cgi?id=1223109#c2 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com --- Comment #2 from Jiri Slaby <jslaby(a)suse.com> --- Great report if this is your first one. It's e1000e's fault. It takes a spin lock in e1000_watchdog_task(): spin_lock(&adapter->stats64_lock); e1000e_update_stats(adapter); -> e1000e_update_phy_stats() -> e1000e_read_phy_reg_mdic() -> usleep_range() ----> Boom. Caused by 6.8.5 commit: commit 0a4e3c2d976aa4dd38951afd6267f74ef3fade0e Author: Vitaly Lifshits <vitaly.lifshits(a)intel.com> Date: Thu Jan 4 16:16:52 2024 +0200 e1000e: Workaround for sporadic MDI error on Meteor Lake systems commit 6dbdd4de0362c37e54e8b049781402e5a409e7d0 upstream. Reported upstream: https://lore.kernel.org/all/809b5785-e65f-47f4-b52b-f9d2af0a3484@kernel.org/ -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1222345] Laptop wakes from suspend once the user closes the lid
by bugzilla_noreply＠suse.com 19 Apr '24

19 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222345 https://bugzilla.suse.com/show_bug.cgi?id=1222345#c12 --- Comment #12 from Takashi Iwai <tiwai(a)suse.com> --- The former. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1222345] Laptop wakes from suspend once the user closes the lid
by bugzilla_noreply＠suse.com 18 Apr '24

18 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222345 https://bugzilla.suse.com/show_bug.cgi?id=1222345#c11 --- Comment #11 from Tristan Miller <psychonaut(a)nothingisreal.com> --- Do you mean the kernel maintainers, or the hardware manufacturer? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1222345] Laptop wakes from suspend once the user closes the lid
by bugzilla_noreply＠suse.com 18 Apr '24

18 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222345 https://bugzilla.suse.com/show_bug.cgi?id=1222345#c10 --- Comment #10 from Takashi Iwai <tiwai(a)suse.com> --- The best would be to report your issue to the upstream devs, I suppose. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1223025] New: CPU soft lockup when suspending
by bugzilla_noreply＠suse.com 18 Apr '24

18 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1223025 Bug ID: 1223025 Summary: CPU soft lockup when suspending 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: badshah400(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 874349 --> https://bugzilla.suse.com/attachment.cgi?id=874349&action=edit Full journal log from problematic session Laptop went into CPU soft lockup look upon closing lid (expecting suspend) until battery died. Here is the relevant section of the log from `journalctl -b -1`: /me goes to bed at the healthy, healthy time of 01:26:56 and the madness starts: > Apr 18 01:26:56 systemd[1]: Reached target Sleep. > Apr 18 01:26:56 systemd[1]: Starting System Suspend... > Apr 18 01:26:56 systemd-sleep[4069]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend > Apr 18 01:26:56 systemd-sleep[4064]: Performing sleep operation 'suspend'... > Apr 18 01:26:56 kernel: PM: suspend entry (s2idle) > Apr 18 01:26:56 kernel: Filesystems sync: 0.017 seconds > Apr 18 01:26:56 goa-daemon[3630]: g_socket_client_connect_to_host() failed: Error resolving “mail.ulg.ac.be”: Name or service not known (g-resolver-error-quark, 0) > Apr 18 01:26:57 goa-daemon[3630]: g_socket_client_connect_to_host() failed: Error resolving “mail.ulg.ac.be”: Name or service not known (g-resolver-error-quark, 0) > Apr 18 01:26:58 dbus-daemon[1409]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.96' (uid=1000 pid=3498 comm="/usr/bin/gnome-software --gapplication-service") > Apr 18 01:27:20 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 26s! [systemd-sleep:4064] > Apr 18 01:27:20 kernel: Modules linked in: uinput exfat ccm snd_seq_dummy snd_hrtimer snd_seq snd_seq_device rfcomm cmac algif_hash algif_skcipher af_alg af_packet uvcvideo videobuf2_vmalloc uvc videobuf2_memops videobuf2_v4l2 videodev nf_conntrack_netbios_ns nf_conntrack_broadcast videobuf2_common nft_fib_inet mc 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_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables bnep btusb btrtl btintel btbcm btmtk bluetooth ecdh_generic qrtr binfmt_misc snd_acp_legacy_mach snd_acp_mach snd_soc_nau8821 snd_acp3x_pdm_dma snd_soc_dmic snd_acp3x_rn snd_sof_amd_acp63 snd_sof_amd_vangogh snd_sof_amd_rembrandt snd_sof_amd_renoir snd_sof_amd_acp snd_sof_pci snd_sof_xtensa_dsp snd_ctl_led snd_sof snd_hda_codec_realtek snd_sof_utils snd_hda_codec_generic mt7921e snd_soc_core mt7921_common snd_hda_codec_hdmi mt792x_lib snd_compress nls_iso8859_1 snd_pcm_dmaengine mt76_connac_lib snd_pci_ps nls_cp437 snd_rpl_pci_acp6x mt76 snd_hda_intel > Apr 18 01:27:20 kernel: snd_acp_pci vfat fat snd_acp_legacy_common snd_intel_dspcfg snd_intel_sdw_acpi snd_pci_acp6x snd_hda_codec snd_pci_acp5x xfs mac80211 intel_rapl_msr snd_hda_core libarc4 snd_hwdep snd_rn_pci_acp3x intel_rapl_common snd_acp_config snd_pcm think_lmi snd_soc_acpi thinkpad_acpi edac_mce_amd pcspkr cfg80211 efi_pstore firmware_attributes_class wmi_bmof snd_timer snd_pci_acp3x k10temp i2c_piix4 ledtrig_audio thermal tiny_power_button platform_profile nxp_nci_i2c nxp_nci snd ac nci soundcore nfc rfkill i2c_scmi amd_pmc button joydev nvme_fabrics fuse loop dm_mod configfs nfnetlink dmi_sysfs ip_tables x_tables mmc_block amdgpu crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic gf128mul amdxcp i2c_algo_bit ghash_clmulni_intel drm_ttm_helper sha512_ssse3 ttm drm_exec gpu_sched sha256_ssse3 xhci_pci drm_suballoc_helper rtsx_pci_sdmmc sha1_ssse3 xhci_pci_renesas drm_buddy mmc_core nvme aesni_intel drm_display_helper xhci_hcd video crypto_simd cec ucsi_acpi cryptd nvme_core typec_ucsi usbcore roles > Apr 18 01:27:20 kernel: nvme_auth rc_core rtsx_pci sp5100_tco t10_pi typec battery wmi serio_raw btrfs blake2b_generic libcrc32c crc32c_intel xor raid6_pq r8169 realtek mdio_devres libphy br_netfilter bridge stp llc msr kvm_amd ccp kvm irqbypass efivarfs > Apr 18 01:27:20 kernel: CPU: 1 PID: 4064 Comm: systemd-sleep Not tainted 6.8.5-1-default #1 openSUSE Tumbleweed 633d4bc373b32029af03848d6d101f997828843f > Apr 18 01:27:20 kernel: Hardware name: LENOVO 21A0CTO1WW/21A0CTO1WW, BIOS R1MET55W (1.25 ) 10/30/2023 > Apr 18 01:27:20 kernel: RIP: 0010:smp_call_function_many_cond+0x11f/0x4e0 > Apr 18 01:27:20 kernel: Code: 63 d0 e8 14 67 48 00 3b 05 2e 11 f1 01 73 25 48 63 d0 49 8b 37 48 03 34 d5 a0 5c 2c af 8b 56 08 83 e2 01 74 0a f3 90 8b 4e 08 <83> e1 01 75 f6 83 c0 01 eb c1 48 83 c4 40 5b 5d 41 5c 41 5d 41 5e > Apr 18 01:27:20 kernel: RSP: 0018:ffffb992cfa2bc70 EFLAGS: 00000202 > Apr 18 01:27:20 kernel: RAX: 0000000000000008 RBX: 0000000000000001 RCX: 0000000000000011 > Apr 18 01:27:20 kernel: RDX: 0000000000000001 RSI: ffffa07e92041440 RDI: ffffa07880073848 > Apr 18 01:27:20 kernel: RBP: 0000000000000246 R08: ffffa07880073c50 R09: ffffa07880073c50 > Apr 18 01:27:20 kernel: R10: ffffffffb05ba598 R11: 0000000000000000 R12: ffffa07e91cbbbc0 > Apr 18 01:27:20 kernel: R13: 0000000000000001 R14: 0000000000000001 R15: ffffa07e91cbbbc0 > Apr 18 01:27:20 kernel: FS: 00007f7251605900(0000) GS:ffffa07e91c80000(0000) knlGS:0000000000000000 > Apr 18 01:27:20 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > Apr 18 01:27:20 kernel: CR2: 00007fafe6eccfe8 CR3: 0000000461cce000 CR4: 0000000000750ef0 > Apr 18 01:27:20 kernel: PKRU: 55555554 > Apr 18 01:27:20 kernel: Call Trace: > Apr 18 01:27:20 kernel: <IRQ> > Apr 18 01:27:20 kernel: ? watchdog_timer_fn+0x1e6/0x270 > Apr 18 01:27:20 kernel: ? __pfx_watchdog_timer_fn+0x10/0x10 > Apr 18 01:27:20 kernel: ? __hrtimer_run_queues+0x10f/0x2b0 > Apr 18 01:27:20 kernel: ? hrtimer_interrupt+0xf8/0x230 > Apr 18 01:27:20 kernel: ? __sysvec_apic_timer_interrupt+0x4d/0x140 > Apr 18 01:27:20 kernel: ? sysvec_apic_timer_interrupt+0x6d/0x90 > Apr 18 01:27:20 kernel: </IRQ> > Apr 18 01:27:20 kernel: <TASK> > Apr 18 01:27:20 kernel: ? asm_sysvec_apic_timer_interrupt+0x1a/0x20 > Apr 18 01:27:20 kernel: ? smp_call_function_many_cond+0x11f/0x4e0 > Apr 18 01:27:20 kernel: ? __pfx_do_sync_core+0x10/0x10 > Apr 18 01:27:20 kernel: on_each_cpu_cond_mask+0x24/0x40 > Apr 18 01:27:20 kernel: text_poke_bp_batch+0xbe/0x2f0 > Apr 18 01:27:20 kernel: ? arch_jump_label_transform_queue+0x57/0x80 > Apr 18 01:27:20 kernel: text_poke_finish+0x1f/0x30 > Apr 18 01:27:20 kernel: arch_jump_label_transform_apply+0x1a/0x30 > Apr 18 01:27:20 kernel: jump_label_update+0x9c/0x100 > Apr 18 01:27:20 kernel: static_key_slow_inc_cpuslocked+0x51/0x90 > Apr 18 01:27:20 kernel: static_key_slow_inc+0x1a/0x30 > Apr 18 01:27:20 kernel: freeze_processes+0xae/0xc0 > Apr 18 01:27:20 kernel: pm_suspend+0x1bd/0x590 > Apr 18 01:27:20 kernel: state_store+0x6c/0xd0 > Apr 18 01:27:20 kernel: kernfs_fop_write_iter+0x133/0x1d0 > Apr 18 01:27:20 kernel: vfs_write+0x261/0x430 > Apr 18 01:27:20 kernel: ksys_write+0x67/0xe0 > Apr 18 01:27:20 kernel: do_syscall_64+0x83/0x170 > Apr 18 01:27:20 kernel: ? exc_page_fault+0x71/0x160 > Apr 18 01:27:20 kernel: entry_SYSCALL_64_after_hwframe+0x78/0x80 > Apr 18 01:27:20 kernel: RIP: 0033:0x7f72515069c4 > Apr 18 01:27:20 kernel: Code: 84 00 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 90 90 80 3d e5 6f 0f 00 00 74 13 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 c3 0f 1f 00 48 83 ec 28 48 89 54 24 18 48 > Apr 18 01:27:20 kernel: RSP: 002b:00007ffce66ccec8 EFLAGS: 00000202 ORIG_RAX: 0000000000000001 > Apr 18 01:27:20 kernel: RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 00007f72515069c4 > Apr 18 01:27:20 kernel: RDX: 0000000000000004 RSI: 000055ebc0f530c0 RDI: 0000000000000005 > Apr 18 01:27:20 kernel: RBP: 000055ebc0f530c0 R08: 0000000000000000 R09: 0000000000000001 > Apr 18 01:27:20 kernel: R10: 0000000000000003 R11: 0000000000000202 R12: 0000000000000004 > Apr 18 01:27:20 kernel: R13: 000055ebc0f4f2d0 R14: 00007f72515edee0 R15: 00000000fffffff7 > Apr 18 01:27:20 kernel: </TASK> > Apr 18 01:27:21 gsd-power[3460]: Failed to acquire idle monitor proxy: Timeout was reached > Apr 18 01:27:21 gsd-power[3460]: Failed to acquire idle monitor proxy: Timeout was reached > Apr 18 01:27:21 gsd-power[3460]: Failed to acquire idle monitor proxy: Timeout was reached > Apr 18 01:27:21 gsd-power[3460]: Failed to acquire idle monitor proxy: Timeout was reached > Apr 18 01:27:21 gsd-power[3460]: Error setting property 'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: Timeout was reached (g-io-error-quark, 24) > Apr 18 01:27:21 gnome-session[2977]: gnome-session-binary[2977]: GnomeDesktop-WARNING: Failed to acquire idle monitor proxy: Timeout was reached > Apr 18 01:27:21 gnome-session-binary[2977]: GnomeDesktop-WARNING: Failed to acquire idle monitor proxy: Timeout was reached > Apr 18 01:27:23 dbus-daemon[1409]: [system] Failed to activate service 'org.freedesktop.PackageKit': timed out (service_start_timeout=25000ms) > Apr 18 01:27:26 kernel: lockdown_is_locked_down: 6 callbacks suppressed > Apr 18 01:27:26 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 > Apr 18 01:27:48 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 52s! [systemd-sleep:4064] and on and on until 03:44:40 when apparently the battery dies and the logging stops. openSUSE info ============= * NAME="openSUSE Tumbleweed" * VERSION="20240412" Kernel info (uname -a) ====================== * Linux ABThinkPadP14s2 6.8.5-1-default #1 SMP PREEMPT_DYNAMIC Thu Apr 11 04:31:19 UTC 2024 (542f698) x86_64 x86_64 x86_64 GNU/Linux Full journal log attached. Happy to help with any other info as needed. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1221884] Kernel panics kworker/3:2
by bugzilla_noreply＠suse.com 17 Apr '24

17 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1221884 https://bugzilla.suse.com/show_bug.cgi?id=1221884#c2 --- Comment #2 from Anthony Iliopoulos <ailiopoulos(a)suse.com> --- I think upstream commit 4207b556e62f ("kernfs: RCU protect kernfs_nodes and avoid kernfs_idr_lock in kernfs_find_and_get_node_by_id()") fixes this issue, and this was backported to v6.8.6 which is now available in TW. Could you please give it a try and see if this is still reproducible? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1222902] Monitor detection fails after hard reset
by bugzilla_noreply＠suse.com 17 Apr '24

17 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222902 https://bugzilla.suse.com/show_bug.cgi?id=1222902#c1 Felix Miata <mrmazda(a)earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mrmazda(a)earthlink.net --- Comment #1 from Felix Miata <mrmazda(a)earthlink.net> --- X11 session? Wayland session? What GPU? Gnome? KDE? XFCE? Other? Input/Ouput from inxi -GSaz will provide answers to all and more. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1222902] New: Monitor detection fails after hard reset
by bugzilla_noreply＠suse.com 16 Apr '24

16 Apr '24

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 0

[Bug 1219180] New: Missing framebuffer during boot on aarch64
by bugzilla_noreply＠suse.com 16 Apr '24

16 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1219180 Bug ID: 1219180 Summary: Missing framebuffer during boot on aarch64 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3891664/modules/ansi ble/steps/31 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 CC: tzimmermann(a)suse.com Target Milestone: --- Found By: openQA Blocker: --- Unless the initrd is built with the platform native DRM driver (e.g. virtio_gpu), there is no graphical output during boot. This also means that entering a passphrase for unlocking the root fs is not possible. On x86 it uses the EFI framebuffer successfully, but on aarch64 dmesg has no trace of efifb/simplefb/simpledrm. ## Observation openQA test in scenario microos-Tumbleweed-MicroOS-Image-sdboot-aarch64-microos-wizard@aarch64 fails in [ansible](https://openqa.opensuse.org/tests/3891664/modules/ansible/steps/31) ## Test suite description Like MicroOS, but use neither combustion nor ignition for the intial configuration, so jeos-firstboot runs. ## Reproducible Fails since (at least) Build [20231129](https://openqa.opensuse.org/tests/3771195) ## Expected result Last good: [20231127](https://openqa.opensuse.org/tests/3763820) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=microo… -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1220541] New: kexec does a full reboot with kernel 6.7.6-1.1
by bugzilla_noreply＠suse.com 15 Apr '24

15 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1220541 Bug ID: 1220541 Summary: kexec does a full reboot with kernel 6.7.6-1.1 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: me(a)pavinjoseph.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Tested on identical systems with kexec-tools 2.0.27-3.2 (on both) and kernel 6.7.5-1.1 (on working system) and 6.7.6-1.1 (on faulty system). Faulty system (fully updated as of Feb 28 2024) is on Tumbleweed release 20240226. Working system is on release 20240222. Issue reproduced on working system by doing zypper ref and zypper in kernel-default to upgrade just the kernel to the latest version. Issue happens after the next cold boot and persists. -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1222345] Laptop wakes from suspend once the user closes the lid
by bugzilla_noreply＠suse.com 15 Apr '24

15 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222345 https://bugzilla.suse.com/show_bug.cgi?id=1222345#c9 --- Comment #9 from Tristan Miller <psychonaut(a)nothingisreal.com> --- I tried toggling the lid wakeup as you suggested. No matter whether it shows as enabled or disabled in /proc/acpi/wakeup, and no matter whether I put the laptop to sleep using the KDE Plasma GUI or with "echo mem > /sys/power/state", the laptop wakes up once I close the lid. I don't see any settings in the BIOS menu that seem relevant. Is there anything else I can try? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1222816] New: BTRFS_IOC_SNAP_CREATE_V2 return error but did some of the work
by bugzilla_noreply＠suse.com 15 Apr '24

15 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222816 Bug ID: 1222816 Summary: BTRFS_IOC_SNAP_CREATE_V2 return error but did some of the work 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: aschnell(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- While working on bug #1222674 I noticed that the BTRFS_IOC_SNAP_CREATE_V2 ioctl when passed a non existing qgroup does create the snapshot but also reports an error (ENOENT). Is that desired behavior? Can I really on that it (ioctl does everything except adding to the qgroup)? -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1222818] New: Kernel Configuration Breakage (regulators) in config/arm64/default for MediaTek boards when merge from master to stable
by bugzilla_noreply＠suse.com 15 Apr '24

15 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222818 Bug ID: 1222818 Summary: Kernel Configuration Breakage (regulators) in config/arm64/default for MediaTek boards when merge from master to stable Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: macpaul.lin(a)mediatek.com QA Contact: qa-bugs(a)suse.de CC: 95kreaninw95(a)gmail.com, chester.lin(a)suse.com, dmueller(a)suse.com, forgotten_0079121656(a)user.net, ivan.ivanov(a)suse.com, m4ng4n(a)gmx.de, macpaul.lin(a)mediatek.com, mgorman(a)suse.com, mhocko(a)suse.com, qa-bugs(a)suse.de, tiwai(a)suse.com, vbabka(a)suse.com Depends on: 1215335 Target Milestone: --- Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1215335 +++ Reference: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035591 ## Description A regression has been identified in the kernel configuration file `config/arm64/default` that appears to have been introduced during a merge from the master branch to the stable branch. The issue affected genio-mt8395 boards and removed settings of enabling regulators by this commit. [b197b3604a7b1542574ed75ee9e5f708eaa9772c] Update config files: enable arm64 regulator modules for mediatek boards (bsc#1215335) ## Affected Commits - **Bad Commit**: [a26e308341f11d0300a8bef13e97c9d213c6722a] Merge branch 'master' into stable - **Last Known Good Commit**: [18231664d40aa6b0efdc96714d3d1de0519bb460] Merge remote-tracking branch 'origin/users/vkarasulli/stable/for-next' into stable ## Removed configurations which leads board boot up fail. git checkout a26e308341f11d0300a8bef13e97c9d213c6722a git diff HEAD~1 | grep MT63 -CONFIG_PINCTRL_MT6397=y -# CONFIG_POWER_RESET_MT6323 is not set CONFIG_MFD_MT6360=m # CONFIG_MFD_MT6370 is not set -CONFIG_MFD_MT6397=m +# CONFIG_MFD_MT6397 is not set # CONFIG_REGULATOR_MT6311 is not set CONFIG_REGULATOR_MT6315=m -# CONFIG_REGULATOR_MT6323 is not set -# CONFIG_REGULATOR_MT6331 is not set -# CONFIG_REGULATOR_MT6332 is not set -CONFIG_REGULATOR_MT6357=m -CONFIG_REGULATOR_MT6358=m -CONFIG_REGULATOR_MT6359=m CONFIG_REGULATOR_MT6360=m CONFIG_REGULATOR_MT6380=m -CONFIG_REGULATOR_MT6397=m CONFIG_SND_SOC_MT6797_MT6351=m CONFIG_SND_SOC_MT8183_MT6358_TS3A227E_MAX98357A=m -# CONFIG_LEDS_MT6323 is not set -CONFIG_RTC_DRV_MT6397=m ## Expected Behavior and suggested fix Please help to add these settings in both master and stable branch in config/arm64/default CONFIG_PINCTRL_MT6397=y CONFIG_MFD_MT6397=m CONFIG_REGULATOR_MT6357=m CONFIG_REGULATOR_MT6358=m CONFIG_REGULATOR_MT6359=m CONFIG_REGULATOR_MT6397=m CONFIG_RTC_DRV_MT6397=m ## Additional Information Boot fail log using openSuse openSUSE-Tumbleweed-NET-aarch64-20240410.iso (This issue has been reported more earlier.) Error log: /var/log/boot.msg:509:<6>[ 25.667557][ T10] platform 11290000.usb: deferred probe pending: platform: wait for supplier /soc/pwrap@10024000/pmic/regulators/ldo_vusb /var/log/boot.msg:510:<6>[ 25.669208][ T10] platform 112a0000.usb: deferred probe pending: platform: wait for supplier /soc/pwrap@10024000/pmic/regulators/ldo_vusb /var/log/boot.msg:511:<6>[ 25.670850][ T10] platform 11230000.mmc: deferred probe pending: platform: wait for supplier /soc/pwrap@10024000/pmic/regulators/ldo_vufs /var/log/boot.msg:512:<6>[ 25.672507][ T10] platform 112b0000.usb: deferred probe pending: platform: wait for supplier /soc/pwrap@10024000/pmic/regulators/ldo_vusb /var/log/boot.msg:513:<6>[ 25.674149][ T10] spi spi0.0: deferred probe pending: spi: wait for supplier /soc/pwrap@10024000/pmic/regulators/ldo_vcn33_2_bt Thanks! Macpaul Lin -- You are receiving this mail because: You are the assignee for the bug.

1 1