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 primitive

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 AcpiUtAcquireMut

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

ove 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 try to catch more people's eyes/get more reports in if people run > into the issue. Don't think or

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 Rufus

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 FreeBSD

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 vers

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 i

Re: Problem with USB after r349133

Nick Wolff [darkfiber...@gmail.com] wrote: > Thomas/HPS, > > I did manage to get a boot with hw.usb.no_boot_wait=1 set in loader.conf. > So if any debugging information off a running system would be helpful let > me know. > > Thanks, > Nick: That was the same workaround that I used. I had not f

Re: Problem with USB after r349133

Nick Wolff [darkfiber...@gmail.com] wrote: > Sorry for email spam but I was wrong. Just gets stuck now during reproping > a pci device after init happens(this is actually a trueos build which is > why you see openrc). That device it's getting stuck on is "Sky Lake-E CBDMA > Registers" which shouldn

Re: Problem with USB after r349133

Hans, I'm building r350003 at the moment which is after the acpi change was moved into an unloaded module. On Mon, Jul 22, 2019 at 12:13 PM Hans Petter Selasky wrote: > On 2019-07-22 17:23, Nick Wolff wrote: > > Sorry for email spam but I was wrong. Just gets stuck now during > reproping > >

Re: Problem with USB after r349133

On 2019-07-22 17:23, Nick Wolff wrote: Sorry for email spam but I was wrong. Just gets stuck now during reproping a pci device after init happens(this is actually a trueos build which is why you see openrc). That device it's getting stuck on is "Sky Lake-E CBDMA Registers" which shouldn't have a

Re: Problem with USB after r349133

Sorry for email spam but I was wrong. Just gets stuck now during reproping a pci device after init happens(this is actually a trueos build which is why you see openrc). That device it's getting stuck on is "Sky Lake-E CBDMA Registers" which shouldn't have a driver attached. https://drive.google.com

Re: Problem with USB after r349133

Thomas/HPS, I did manage to get a boot with hw.usb.no_boot_wait=1 set in loader.conf. So if any debugging information off a running system would be helpful let me know. Thanks, Nick Wolff On Mon, Jul 22, 2019 at 10:27 AM Nick Wolff wrote: > Hello Thomas, > > Any updates? Did you get a bugzill

Re: Problem with USB after r349133

Hello Thomas, Any updates? Did you get a bugzilla ticket filed? Thanks, Nick Wolff On Sat, Jul 6, 2019 at 2:48 PM Thomas Laus wrote: > On 2019-07-06 10:17, Graham Perrin wrote: > > > > I had the almost same (different bus numbers), just once, after updating > > -CURRENT from r349099 to r34976

Re: Problem with USB after r349133

On 2019-07-06 10:17, Graham Perrin wrote: > > I had the almost same (different bus numbers), just once, after updating > -CURRENT from r349099 to r349762. > > The subsequent boot of r349762 was free from the symptom. > > HP EliteBook 8570p, docked, with a Kensington keyboard and Logitech > track

Re: Problem with USB after r349133

On 05/07/2019 16:38, Thomas Laus wrote: Root mount waiting for USBUS7 USBUS6 USBUS0. I had the almost same (different bus numbers), just once, after updating -CURRENT from r349099 to r349762. The subsequent boot of r349762 was free from the symptom. HP EliteBook 8570p, docked, with a K

Re: Problem with USB after r349133

On 2019-07-05 18:05, Hans Petter Selasky wrote: > > There has been very few USB changes, except for ACPI USB support in: > > https://svnweb.freebsd.org/changeset/base/349161 > https://svnweb.freebsd.org/changeset/base/349251 > It looks like I will need to build a few kernels to see what changes m

Re: Problem with USB after r349133

On 2019-07-05 17:38, Thomas Laus wrote: I upgraded to CURRENT r349575 this week and my Dell Inspiron laptop stops processing the rc.conf with this message that repeats until I perform a hard power button reset, ctl-alt-del has no effect: Root mount waiting for USBUS7 USBUS6 USBUS0. I boote

Problem with USB after r349133

I upgraded to CURRENT r349575 this week and my Dell Inspiron laptop stops processing the rc.conf with this message that repeats until I perform a hard power button reset, ctl-alt-del has no effect: Root mount waiting for USBUS7 USBUS6 USBUS0. I booted my kernel.old and everything is fine at