From owner-freebsd-stable@FreeBSD.ORG Tue Jan 31 09:50:51 2006 Return-Path: X-Original-To: stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4177816A420 for ; Tue, 31 Jan 2006 09:50:51 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F79A43D48 for ; Tue, 31 Jan 2006 09:50:50 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.3/8.13.3) with ESMTP id k0V9olwg003264 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 31 Jan 2006 12:50:48 +0300 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.3/8.13.1/Submit) id k0V9ol0F003263; Tue, 31 Jan 2006 12:50:47 +0300 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Tue, 31 Jan 2006 12:50:47 +0300 From: Gleb Smirnoff To: Andrew Pantyukhin Message-ID: <20060131095047.GE93773@cell.sick.ru> References: <20060131082845.GB93773@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i Cc: FreeBSD Stable Subject: Re: Recent MFC's causing trouble with network and mouse X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2006 09:50:51 -0000 On Tue, Jan 31, 2006 at 12:38:44PM +0300, Andrew Pantyukhin wrote: A> On 1/31/06, Gleb Smirnoff wrote: A> > On Tue, Jan 31, 2006 at 02:27:58AM +0300, Andrew Pantyukhin wrote: A> > A> I upgraded my world and kernel from about a week's A> > A> old state to today's source and network (vge) and A> > A> mouse (ums) stopped working. vge0 has a formerly A> > A> usual trouble of link state going up and down, while A> > A> ums0 doesn't move or feel its buttons (tried moused A> > A> and xorg). A> > A> A> > A> Had a look at cvs, didn't see anything suspicious A> > A> about vge and ums in particular :-( This is about time A> > A> I learnt how to live with several kernels at hand... A> > A> > Yes, vge(4) and ums(4) wasn't agressively edited recently, A> > so the breakage is somewhere else. Probably you need to A> > make a binary search to find the commit that caused the problem. A> A> Ok, could you please tell me where to learn how to do A> that? 1) Divide the breakage timeframe by two, to determine the middle. (For example 26 Jan - working, 31 Jan - not working. Then the middle would be 28 Jan.) 2) Update your sources to the middle. 3) Check whether problem is present? Goto 1). You loop in this cycle until you come to a small timeframe with a few commits. Then you either determine which one is problematic logically, or try to apply them one by one. Once you habe found the problematic commit, you contact its author. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE