From owner-freebsd-stable@FreeBSD.ORG Wed Sep 3 22:23:15 2014 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BC08E77E for ; Wed, 3 Sep 2014 22:23:15 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6A7481EE1 for ; Wed, 3 Sep 2014 22:23:15 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.9/8.14.9) with ESMTP id s83MNDBT016836 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 3 Sep 2014 16:23:14 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.9/8.14.9/Submit) with ESMTP id s83MNDKJ016833; Wed, 3 Sep 2014 16:23:13 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Wed, 3 Sep 2014 16:23:13 -0600 (MDT) From: Warren Block To: Mateusz Guzik Subject: Re: Anyone else seeing lockup on boot with r271042? In-Reply-To: Message-ID: References: <20140903204605.GA16445@dft-labs.eu> User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Wed, 03 Sep 2014 16:23:14 -0600 (MDT) Cc: stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Sep 2014 22:23:15 -0000 On Wed, 3 Sep 2014, Warren Block wrote: > On Wed, 3 Sep 2014, Mateusz Guzik wrote: > >> On Wed, Sep 03, 2014 at 02:31:47PM -0600, Warren Block wrote: >>> With 10-STABLE r271042, my amd64 desktop system locks hard when devd >>> starts, or just after. >>> >>> Booting with devd disabled is possible, and it can be started after >>> the system is up. >> >> Can try to narrow down exact revision which introduces the problem? > > Checking now. r270986 is okay. Based on the changes, I'm guessing it is > some interaction with vt and moused triggered by devd. And that seems to be just what it is. During one restart, I saw the devd message, but also a part of a moused message before it locked up. I have a USB mouse, without moused explicitly enabled in /etc/rc.conf. The lockup with devd starts with r271022. It can't always be started after startup, feels like a race.