From owner-freebsd-stable@FreeBSD.ORG  Wed Jun 19 17:50:48 2013
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id 8B302697;
 Wed, 19 Jun 2013 17:50:48 +0000 (UTC)
 (envelope-from wblock@wonkity.com)
Received: from wonkity.com (wonkity.com [67.158.26.137])
 by mx1.freebsd.org (Postfix) with ESMTP id 316A11383;
 Wed, 19 Jun 2013 17:50:48 +0000 (UTC)
Received: from wonkity.com (localhost [127.0.0.1])
 by wonkity.com (8.14.7/8.14.7) with ESMTP id r5JHoloc002157;
 Wed, 19 Jun 2013 11:50:47 -0600 (MDT)
 (envelope-from wblock@wonkity.com)
Received: from localhost (wblock@localhost)
 by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id r5JHolOZ002154;
 Wed, 19 Jun 2013 11:50:47 -0600 (MDT)
 (envelope-from wblock@wonkity.com)
Date: Wed, 19 Jun 2013 11:50:47 -0600 (MDT)
From: Warren Block <wblock@wonkity.com>
To: Ian Lepore <ian@FreeBSD.org>
Subject: Re: system sporadically hangs on shutdown after switching to
 WITH_NEW_XORG
In-Reply-To: <1371403440.4485.22.camel@revolution.hippie.lan>
Message-ID: <alpine.BSF.2.00.1306191147370.99258@wonkity.com>
References: <51BDD593.5000102@xs4all.nl> <20130616153710.GT91021@kib.kiev.ua>
 <51BDDE64.2040801@xs4all.nl> <20130616155502.GA26171@icarus.home.lan>
 <51BDE16D.3080903@xs4all.nl> <20130616160752.GA26518@icarus.home.lan>
 <1371403440.4485.22.camel@revolution.hippie.lan>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
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, 19 Jun 2013 11:50:47 -0600 (MDT)
Cc: Jeremy Chadwick <jdc@koitsu.org>, Michiel Boland <boland37@xs4all.nl>,
 Konstantin Belousov <kostikbel@gmail.com>,
 FreeBSD Stable <freebsd-stable@FreeBSD.org>
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jun 2013 17:50:48 -0000

On Sun, 16 Jun 2013, Ian Lepore wrote:

> On Sun, 2013-06-16 at 09:07 -0700, Jeremy Chadwick wrote:
>> On Sun, Jun 16, 2013 at 06:01:49PM +0200, Michiel Boland wrote:
>>> On 06/16/2013 17:55, Jeremy Chadwick wrote:
>>> [...]
>>>
>>>> Are you running moused(8)?  Actually, I can see quite clearly that you
>>>> are in your core.txt:
>>>>
>>>> Starting ums0 moused.
>>>>
>>>> Try turning that off.  Don't ask me how, because devd(8) / devd.conf(5)
>>>> might be involved.
>>>>
>>>
>>> The moused is started by devd - I don't see a quick way of turning that off.
>>
>> Comment out the relevant crap in devd.conf(5).  Search for "ums"
>> and comment out the two "notify" sections.
>
> I don't understand why people treat devd as if it's some sort of evil
> virus that they're forced to live with (using phrases like "crap in
> devd.conf").  In general, the standard devd rules tend to fall into 3
> categories:
>      * use logger(1) to record some anomaly
>      * kldload a module
>      * invoke a standard /etc/rc.d script
>
> For moused, the devd rules invoke /etc/rc.d/moused, which implies that
> setting moused_enable=NO in rc.conf would be all that's needed to
> disable it.

Seems that way, but it's misleading.  Plug in a USB mouse, and devd will 
start moused anyway (with different options, but still...).  ISTR that 
can be disabled with

   moused_enable="NO"
   moused_nondefault_enable="NO"

I have not tested that lately.