April 2024 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[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