Re: VMD consumes 100% cpu after unpausing guest

On 2018 Feb 26 (Mon) at 18:52:34 -0800 (-0800), Pratik Vyas wrote: :* Dave Voutila [2018-02-22 23:40:21 -0500]: : :> > Synopsis: VMD consumes 100% cpu after unpausing guest :> > Category: amd64 :> > Environment: :> System : OpenBSD 6.2 :> Details : OpenBSD

Re: (Minor, in the unbound man pages, "SEE ALSO" refs don't hyperlink)

Hi, Jason McIntyre wrote on Tue, Feb 27, 2018 at 07:07:04AM +: > On Tue, Feb 27, 2018 at 02:01:30AM -0500, Tinker wrote: >> The links in the unbound documentation >> e.g. http://man.openbsd.org/unbound#SEE_ALSO >> do not share format with the other OpenBSD docs >>

Re: uvideo0: could not open VS pipe: INVAL

-> 2018-02-26 Mon 17:02, Stefan Sperling, : > On Mon, Feb 26, 2018 at 04:09:36PM +0100, C. wrote: > > -> 2018-02-26 Mon 15:52, Martin Pieuchot, : > > > There's currently no support for isochronous transfers on xhci(4). Some > > > code is there but it has to be

Re: panic: kernel diagnostic assertion "skrev->reverse == NULL"

On 2018-02-25 22:48, Johan Huldtgren wrote: On 2018-02-25 21:54, Alexander Bluhm wrote: On Sat, Feb 24, 2018 at 04:20:50PM -0500, Johan Huldtgren wrote: trying to connect to my gateway today I found the following panic. This is 100% reproducible anytime I connect via openvpn and then generate

Re: HDMI can't be used as primary monitor

Thank you Mark for reply. I upraded to snapshot. Now the xrandr command shows properly HDMI connected and possible modes, but the command xrandr --output eDP-1 --auto --rotate normal --pos 0x0 --output HDMI-1 --auto --rotate normal --right-of eDP-1 it did not make HDMI TV to wakeup and I was

Re: HDMI can't be used as primary monitor

On Wed, Feb 28, 2018 at 07:25:03AM +0100, Jiri Navratil wrote: > Thank you Mark for reply. > > I upraded to snapshot. Now the xrandr command shows properly HDMI > connected and possible modes, but the command > > xrandr --output eDP-1 --auto --rotate normal --pos 0x0 --output HDMI-1 --auto >

Re: VMD consumes 100% cpu after unpausing guest

Peter Hessler writes: > On 2018 Feb 26 (Mon) at 18:52:34 -0800 (-0800), Pratik Vyas wrote: > :* Dave Voutila [2018-02-22 23:40:21 -0500]: > : > :> > Synopsis:VMD consumes 100% cpu after unpausing guest > :> > Category:amd64 > :> > Environment:

Re: VMD consumes 100% cpu after unpausing guest

* Dave Voutila [2018-02-27 21:29:25 -0500]: I can confirm this patch resolves the issue I reported. I _think_ I'm seeing a similar CPU load drop as well, but definitely have paused/unpaused the guest multiple times without issues. Thanks Dave and Peter for testing. I will