Date: Thu, 12 May 2016 14:58:34 +0900 From: YongHyeon PYUN <pyunyh@gmail.com> To: Yuri <yuri@rawbw.com> Cc: freebsd-net@freebsd.org Subject: Re: Marvell Yukon (msk) network card causes the "sticky mouse" problem: mouse stops for extended periods of time Message-ID: <20160512055834.GA1198@michelle.fasterthan.co.kr> In-Reply-To: <57341899.2040600@rawbw.com> References: <572CC657.8040207@rawbw.com> <572E0AF1.5060307@grosbein.net> <572E18E3.30300@rawbw.com> <20160508093305.GA1558@michelle.fasterthan.co.kr> <57341899.2040600@rawbw.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, May 11, 2016 at 10:46:01PM -0700, Yuri wrote: > On 05/08/2016 02:33, YongHyeon PYUN wrote: > >msk(4) will try to use MSI unless not configured to do so the IRQ > >wouldn't be shared with other devices. If msk(4) is using MSI you > >should see a high irq number greater than or equal to 256 in vmstat > >output. Given that you're seeing issues with MSI, try disabling > >MSI for msk(4). Add the following tunable to /boot/loader.conf and > >reboot. > > > >hw.msk.msi_disable="1" > > For some reason hw.msk.msi_disable isn't found: > # sysctl hw.msk.msi_disable=1 > sysctl: unknown oid 'hw.msk.msi_disable' > even though it is defined in sys/dev/msk/if_msk.c and if_msk module is > loaded. hw.msk.msi_disable is a loader tunable so you can't check it with sysctl(8). Add the tunable to boot/loader.conf to take it effect. See loader.conf(5) for more information.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160512055834.GA1198>