Re: Problem with USB after r349133

2019-07-22 Thread Thomas Laus
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

2019-07-22 Thread Thomas Laus
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

2019-07-22 Thread Nick Wolff
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

2019-07-22 Thread Hans Petter Selasky
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

2019-07-22 Thread Nick Wolff
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

2019-07-22 Thread Nick Wolff
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

2019-07-22 Thread Nick Wolff
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: filesystem mount problem

2019-07-22 Thread Cy Schubert
On July 21, 2019 1:44:13 PM PDT, Ian Lepore wrote: >On Sun, 2019-07-21 at 15:07 -0400, AN wrote: >> Hi: >> >> FreeBSD FreeBSD_13 13.0-CURRENT FreeBSD 13.0-CURRENT #102 r350187: >> Sat Jul >> 20 19:04:30 EDT 2019 >> root@FreeBSD_13:/usr/obj/usr/src/amd64.amd64/sys/MYKERNEL amd64 >> 1300036 >>

Re: mmap port from 9 not working

2019-07-22 Thread Ronald Klop
Van: Laurie Jennings Datum: maandag, 22 juli 2019 14:56 Aan: Ronald Klop Onderwerp: Re: mmap port from 9 not working Van: Laurie Jennings Datum: zondag, 21 juli 2019 16:58 Aan: Konstantin Belousov CC: FreeBSD Current Onderwerp: Re: mmap port from 9 not working On Sunday,

Re: mmap port from 9 not working

2019-07-22 Thread Konstantin Belousov
On Mon, Jul 22, 2019 at 02:03:26PM +0200, Ronald Klop wrote: > > Van: Laurie Jennings > Datum: zondag, 21 juli 2019 16:58 > Aan: Konstantin Belousov > CC: FreeBSD Current > Onderwerp: Re: mmap port from 9 not working > > > > On Sunday, July 21, 2019, 10:44:14 AM EDT, Konstantin Belousov > >

Re: mmap port from 9 not working

2019-07-22 Thread Ronald Klop
Van: Laurie Jennings Datum: zondag, 21 juli 2019 16:58 Aan: Konstantin Belousov CC: FreeBSD Current Onderwerp: Re: mmap port from 9 not working On Sunday, July 21, 2019, 10:44:14 AM EDT, Konstantin Belousov wrote: On Sun, Jul 21, 2019 at 03:48:03AM +, Laurie Jennings wrote: > I have