From owner-freebsd-stable@FreeBSD.ORG Tue Jan 31 08:28:48 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 E16AA16A420 for ; Tue, 31 Jan 2006 08:28:48 +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 4328E43D45 for ; Tue, 31 Jan 2006 08:28:47 +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 k0V8SjPX001517 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 31 Jan 2006 11:28:46 +0300 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.3/8.13.1/Submit) id k0V8SjIV001516; Tue, 31 Jan 2006 11:28:45 +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 11:28:45 +0300 From: Gleb Smirnoff To: Andrew Pantyukhin Message-ID: <20060131082845.GB93773@FreeBSD.org> References: 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 08:28:49 -0000 On Tue, Jan 31, 2006 at 02:27:58AM +0300, Andrew Pantyukhin wrote: A> I upgraded my world and kernel from about a week's A> old state to today's source and network (vge) and A> mouse (ums) stopped working. vge0 has a formerly A> usual trouble of link state going up and down, while A> ums0 doesn't move or feel its buttons (tried moused A> and xorg). A> A> Had a look at cvs, didn't see anything suspicious A> about vge and ums in particular :-( This is about time A> I learnt how to live with several kernels at hand... Yes, vge(4) and ums(4) wasn't agressively edited recently, so the breakage is somewhere else. Probably you need to make a binary search to find the commit that caused the problem. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE