From owner-freebsd-hackers@freebsd.org Fri May 6 16:33:43 2016 Return-Path: Delivered-To: freebsd-hackers@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 69B32B2F11E for ; Fri, 6 May 2016 16:33:43 +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 462A0144D for ; Fri, 6 May 2016 16:33:42 +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 u46GXg5g028044 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Fri, 6 May 2016 09:33:42 -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: Brief and intermittent system freezes To: freebsd-hackers@freebsd.org References: <57212CEC.6050105@rawbw.com> From: Yuri Message-ID: <572CC765.5090003@rawbw.com> Date: Fri, 6 May 2016 09:33:41 -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: <57212CEC.6050105@rawbw.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 May 2016 16:33:43 -0000 On 04/27/2016 14:19, Yuri wrote: > I changed the motherboard on the 10.3 desktop system and now I am > getting the "sticky mouse" effect: mouse briefly freezes every few > seconds. I think USB mouse events aren't propagated to the Xorg > process in a timely fashion. This also possibly makes the system > impaired in some other ways too. One thing I can think of is that the > network driver changed from re(4) to msk(4). For the record, I identified the problem: Marvell Yukon network card driver is faulty. I reported it on net@ Yuri