> Date: Mon, 5 Jan 2026 10:23:17 +0000 > From: Crystal Kolipe <[email protected]> > > On Mon, Jan 05, 2026 at 10:03:14AM +0000, requiem. wrote: > > On Sun, 4 Jan 2026 14:50:34 +0000 > > Crystal Kolipe <[email protected]> wrote: > > > > > On Sun, Jan 04, 2026 at 01:50:35PM +0000, requiem. wrote: > > > > Thank you Crystal for taking the time to offer a recap of the issue. > > > > > > > > > > 0x000000003F7BE000 000040 [ 1.000004] ACPI: ???? > > > > > > 0x00000000FFFD5600 FFFFFFFF (v255 ?????? ???????? FFFFFFFF ???? > > > > > > FFFFFFFF) > > > > > > > > > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > > > > This looks suspicious. > > > > > > > > Is there anything I can do to help explore this? > > > > > > Yes, if you could boot NetBSD with the stock BIOS, (the later F.16 > > > one is fine for this test), and see if the same line appears in the > > > dmesg output. > > > > > > If it does, we can eliminate that being the cause. > > > > > > If it doesn't, then it's likely that which is causing the crash on > > > OpenBSD. > > > > > > > It seems you've hit the nail on the head, the line isn't in the NetBSD > > dmesg when I flash the stock BIOS. > > > > Can I supply anything else? Like I have BIOS rom dumps but I don't know > > how useful that is to you presently. > > We probably have enough info already to create a work-around for this. > > I'll try to look in to it later on today.
I don't really want to add workarounds in the ACPI for random old crap.
