Date: Mon, 24 Jun 2019 01:00:00 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 238729] head -r347549 on aorus gaming 7 F12e BIOS (Threadripper 1950X): boot attempts hang (but boots for fedora/Windows 10 Pro) Message-ID: <bug-238729-227-PTb7padveF@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-238729-227@https.bugs.freebsd.org/bugzilla/> References: <bug-238729-227@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=3D238729 --- Comment #13 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Mark Millard from comment #12) Well adding ACPI_LV_DISPATCH ACPI_LV_NAMES still gets the same last line, although it had more lines output before that: hw.acpi.verbose=3D1 debug.acpi.layer=3D"ACPI_ALL_COMPONENTS ACPI_ALL_DRIVERS" debug.acpi.level=3D"ACPI_LV_ALL_EXCEPTIONS ACPI_LV_DISPATCH ACPI_LV_NAMES ACPI_LV_OPREGION ACPI_LV_TABLES ACPI_LV_VALUES ACPI_LV_OBJECTS ACPI_LV_RESOURCES ACPI_LV_USER_REQUESTS ACPI_LV_PACKAGE" The other additions that I've tried, such as ACPI_LV_EXEC , kept going long= er then I waited. I've no if it had got past that previously-last-line or not. (I only see about 30 lines on screen and it goes by too fast to read.) I've not figured out a way to further narrow the range for what the boot hangs up on --so I'm not trying anything new any more. The above levels are not reporting anything once the boot is hung up (relat= ive to seeing messages). The hang up seems to be too early to allow normal ddb use via the keyboard. --=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-238729-227-PTb7padveF>