From owner-freebsd-net@freebsd.org  Thu May 12 05:46:09 2016
Return-Path: <owner-freebsd-net@freebsd.org>
Delivered-To: freebsd-net@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id E8892B38841
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Thu, 12 May 2016 05:46:09 +0000 (UTC) (envelope-from yuri@rawbw.com)
Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42])
 by mx1.freebsd.org (Postfix) with ESMTP id D94FB129C
 for <freebsd-net@freebsd.org>; Thu, 12 May 2016 05:46:09 +0000 (UTC)
 (envelope-from yuri@rawbw.com)
Received: from yuri.doctorlan.com (c-24-5-143-190.hsd1.ca.comcast.net
 [24.5.143.190]) (authenticated bits=0)
 by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id u4C5k2Ft009237
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO);
 Wed, 11 May 2016 22:46:03 -0700 (PDT) (envelope-from yuri@rawbw.com)
X-Authentication-Warning: shell1.rawbw.com: Host
 c-24-5-143-190.hsd1.ca.comcast.net [24.5.143.190] claimed to be
 yuri.doctorlan.com
Subject: Re: Marvell Yukon (msk) network card causes the "sticky mouse"
 problem: mouse stops for extended periods of time
To: pyunyh@gmail.com
References: <572CC657.8040207@rawbw.com> <572E0AF1.5060307@grosbein.net>
 <572E18E3.30300@rawbw.com> <20160508093305.GA1558@michelle.fasterthan.co.kr>
Cc: freebsd-net@freebsd.org
From: Yuri <yuri@rawbw.com>
Message-ID: <57341899.2040600@rawbw.com>
Date: Wed, 11 May 2016 22:46:01 -0700
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101
 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <20160508093305.GA1558@michelle.fasterthan.co.kr>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 12 May 2016 05:46:10 -0000

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.

Yuri