amd64 head -r349794 (under Hyper-V): "panic: spin lock held too long" during a buildworld buildkernel

2019-07-06 Thread Mark Millard
Looks like pmap_invalidate_range using smp_targeted_tlb_shootdown using _mtx_lock_spin_cookie. I'll note that I had no trouble with -r349444 building world or kernel repeatedly, including when I originally build -r349794 to upgrade. The below is from my 2nd buildworld buildkernel under -r349794

Re: Someone broke USB

2019-07-06 Thread Steve Kargl
On Sat, Jul 06, 2019 at 03:08:13PM -0600, Ian Lepore wrote: > On Sat, 2019-07-06 at 14:06 -0700, Steve Kargl wrote: > > On Sat, Jul 06, 2019 at 10:50:59PM +0200, Hans Petter Selasky wrote: > > > On 2019-07-06 21:41, Steve Kargl wrote: > > > > On Sat, Jul 06, 2019 at 08:33:39PM +0200, Hans Petter Se

Re: Someone broke USB

2019-07-06 Thread Thomas Laus
On 2019-07-06 16:50, Hans Petter Selasky wrote: > > Are you able to bisect the commit introducing the bad behaviour? > I built and booted r349160. My 'boot mount waiting for USBUS7 -> USBUS0 issue went away but the startup halted at the 'mounting late filesystems' step of rc.conf. I had the USB

Re: Someone broke USB

2019-07-06 Thread Hans Petter Selasky
Hi Takanori, Can you have a look at the issues reported in this thread? Are the ACPI functions you call thread safe? USB will enumerate multiple busses at the same time. --HPS On 2019-07-06 23:08, Ian Lepore wrote: On Sat, 2019-07-06 at 14:06 -0700, Steve Kargl wrote: On Sat, Jul 06, 2019

Re: Someone broke USB

2019-07-06 Thread Ian Lepore
On Sat, 2019-07-06 at 14:06 -0700, Steve Kargl wrote: > On Sat, Jul 06, 2019 at 10:50:59PM +0200, Hans Petter Selasky wrote: > > On 2019-07-06 21:41, Steve Kargl wrote: > > > On Sat, Jul 06, 2019 at 08:33:39PM +0200, Hans Petter Selasky > > > wrote: > > > > On 2019-07-06 20:23, Steve Kargl wrote: >

Re: Someone broke USB

2019-07-06 Thread Steve Kargl
On Sat, Jul 06, 2019 at 10:50:59PM +0200, Hans Petter Selasky wrote: > On 2019-07-06 21:41, Steve Kargl wrote: > > On Sat, Jul 06, 2019 at 08:33:39PM +0200, Hans Petter Selasky wrote: > >> On 2019-07-06 20:23, Steve Kargl wrote: > >>> So, how does one get usb working, again? > >>> > >>> -- Steve >

Re: Someone broke USB

2019-07-06 Thread Hans Petter Selasky
On 2019-07-06 21:41, Steve Kargl wrote: On Sat, Jul 06, 2019 at 08:33:39PM +0200, Hans Petter Selasky wrote: On 2019-07-06 20:23, Steve Kargl wrote: So, how does one get usb working, again? -- Steve Can you show dmesg? It looks like the enumeration of busses and devices has changed. grepp

Re: Someone broke USB

2019-07-06 Thread Steve Kargl
On Sat, Jul 06, 2019 at 08:33:39PM +0200, Hans Petter Selasky wrote: > On 2019-07-06 20:23, Steve Kargl wrote: > > So, how does one get usb working, again? > > > > -- Steve > > Can you show dmesg? > It looks like the enumeration of busses and devices has changed. grepping for uhub and usbus of

Re: Someone broke USB

2019-07-06 Thread Steve Kargl
On Sat, Jul 06, 2019 at 08:33:39PM +0200, Hans Petter Selasky wrote: > On 2019-07-06 20:23, Steve Kargl wrote: > > So, how does one get usb working, again? > > > > -- Steve > > Can you show dmesg? > This is dmesg.boot for the kernel with the non-functioning USB stack. I'll need to reboot wit

Re: Problem with USB after r349133

2019-07-06 Thread Thomas Laus
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: Someone broke USB

2019-07-06 Thread Hans Petter Selasky
On 2019-07-06 20:23, Steve Kargl wrote: So, how does one get usb working, again? -- Steve Can you show dmesg? --HPS ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail

Someone broke USB

2019-07-06 Thread Steve Kargl
Updated a month old FreeBSD-current to top of tree. Upon rebooting, the usb no longer functions. No usb mouse. No usb external hard drive. Unplugging and then re-plugging in external drive does not cause the drive to spin up. Logged in as root.` % usbconfig list No device match or lack of perm

Re: Problem with USB after r349133

2019-07-06 Thread Graham Perrin
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

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