Date: Wed, 3 May 2023 15:24:42 -0700 From: Michael Dexter <editor@callfortesting.org> To: freebsd-current@freebsd.org Subject: Boot failure on a ThinkPad T14/Ryzen 7 Pro 6850U Message-ID: <8267eee1-e5f6-d1f2-6fc0-b759d0c91bcc@callfortesting.org>
next in thread | raw e-mail | index | archive | help
Hello all! I confess that this issue exists on 13.1 and 13.2 in addition to the 14-CURRENT snapshot from last week but hopefully there is more to try. This Pr covers the fundamental issue and I have been updating it a I try suggestions: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270707 In short, stock kernels, non-verbose stop at: ... psm0: model Generic PS/2 mouse, device ID 0 battery0: <ACPI Control Method Battery> on acpi0 acpi_acad0: <AD Adapter> on acpi0 <Block cursor, no blink, keyboard input ignored> A verbose boot stops at: ... pcib0: allocated type 4 (0x3f8-0x3f8) for rid 0 of uart0 uart0 failed to probe at port 0x3f8 irq 4 on isa0 pcib0: allocated type 4 (0x2f8-0x2f8) for rid 0 of uart1 <Block cursor, no blink, keyboard input ignored, no mention of acpi_acad0> A kernel built with options ACPI_DEBUG with these boot parameters: set debug.acpi.layer="ACPI_ALL_COMPONENTS ACPI_ALL_DRIVERS" set debug.acpi.level="ACPI_LV_ALL_EXCEPTIONS" Stops at: ... exregion-059 ExSystemMemorySpaceHan: System-Memory (width 8) R/W 0 Address=00000000777770F3 ... nsxfeval-0386 EvaluateObject : Null handle with relative pathname [_PRW] nsxfeval-0386 EvaluateObject... Related suggestion: Should 'options ACPI_DEBUG' be built into the snapshot kernels along with WITNESS etc? Any additional suggestions? Thank you! Michael
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8267eee1-e5f6-d1f2-6fc0-b759d0c91bcc>