Re: Boot still broken from r349133-r349160 - Was re:(Problem with USB after r349133)

On 13/08/2019 16:31, Hans Petter Selasky wrote: > 1) AcpiUtAcquireMutex() doesn't support recursion, but also fails to > report an error when such a condition is occurring. Here is the > backtrace of the illegal mutex recursion. I have an old patch that replaces hand-rolled ACPI platform

Re: Boot still broken from r349133-r349160 - Was re:(Problem with USB after r349133)

Hi, After tearing ACPI apart, there appears to be an issue like following: 1) AcpiUtAcquireMutex() doesn't support recursion, but also fails to report an error when such a condition is occurring. Here is the backtrace of the illegal mutex recursion. > AcpiUtAcquireMutex() at

Re: Boot still broken from r349133-r349160 - Was re:(Problem with USB after r349133)

I’m 99% sure that the boot breakage is due to this commit: Author: jkim Date: Tue Jul 9 18:02:36 2019 New Revision: 349863 URL: https://svnweb.freebsd.org/changeset/base/349863 Log: MFV: r349861 Import ACPICA 20190703. I have two systems now that are affected, and both of them are “fixed”

Re: Boot still broken from r349133-r349160 - Was re:(Problem with USB after r349133)

Sorry boot is broken from harddrive or iso(as cdrom) for some users(at least 3) since somewhere in the revisions listed above and that still stands as of the Head snapshot of 072519. Sorry for lack of clarity. There was a thread under Problem with USB after r349133 but I decided to rename it to

Re: Boot still broken from r349133-r349160 - Was re:(Problem with USB after r349133)

Rodney, you are right that the .iso "should work", and a lot of other projects, from Microsoft Windows 10 to Trident BSD only a furnish an iso, and no img file. FreeBSD is one of the few that give you both choices. The problem goes deeper than any one operating system. If you've ever used the

Re: Boot still broken from r349133-r349160 - Was re:(Problem with USB after r349133)

> The .iso files are for a dvd install. If you want to use a usb, download > the .img files. > > FreeBSD-13.0-CURRENT-amd64-20190725-r350322-memstick.img > The

Re: Boot still broken from r349133-r349160 - Was re:(Problem with USB after r349133)

The .iso files are for a dvd install. If you want to use a usb, download the .img files. FreeBSD-13.0-CURRENT-amd64-20190725-r350322-memstick.img ( or get the .xz

Boot still broken from r349133-r349160 - Was re:(Problem with USB after r349133)

I just tested the snapshot from 20190725 and still am getting the root mount rating for "boot on boot. I think something deeper broke between r349133 and r349160 because even when I turn off wait for Root Mount on usb root via a loader variable boot just get's stuck later on in the process. This