Date: Fri, 08 Mar 2024 01:06:33 +0000 From: bugzilla-noreply@freebsd.org To: acpi@FreeBSD.org Subject: [Bug 270707] Installer media doesn't boot on Thinkpad T14s Gen 3 (Ryzen 7 Pro 6850U) Message-ID: <bug-270707-16045-OJpmoMOala@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-270707-16045@https.bugs.freebsd.org/bugzilla/> References: <bug-270707-16045@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D270707 --- Comment #30 from John Baldwin <jhb@FreeBSD.org> --- Generally speaking, the last line of dmesg is not always a good indicator of the source of a hang once the kernel has finished its attach of devices. In particular, most sysinits aside from probing devices do not generate any ou= tput on the console, so once the kernel has finished its attach of devices, the = last line will just be the last device probed until single user starts. One option that can work is to set 'debug.verbose_sysinit=3D1' from the loa= der.=20 This will generate a lot of output, but if the kernel hangs during boot it = will print out the last SYSINIT function the kernel called before the hang. It's not clear from the various followups though if this is one bug or many= , or if disabling uart1 works only for some cases but not others? Also, it's not clear if the internal keyboard not working is true for everyone, or only so= me folks. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-270707-16045-OJpmoMOala>