From owner-freebsd-current@FreeBSD.ORG Mon Mar 2 04:08:03 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8D1AE1065670; Mon, 2 Mar 2009 04:08:03 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 4B4838FC0C; Mon, 2 Mar 2009 04:08:03 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id n22480eW066061 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 1 Mar 2009 20:08:01 -0800 (PST) (envelope-from sam@freebsd.org) Message-ID: <49AB5BA0.9070406@freebsd.org> Date: Sun, 01 Mar 2009 20:08:00 -0800 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.18 (X11/20081209) MIME-Version: 1.0 To: "M. Warner Losh" References: <69F972E4-D7C1-47D8-8C83-A44062DB47E1@gmail.com> <6D5C9BFA-CCF4-4AEE-9688-23D66D594BC6@gmail.com> <20090301.205017.1025328203.imp@bsdimp.com> In-Reply-To: <20090301.205017.1025328203.imp@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC-x.dcc-servers-Metrics: ebb.errno.com; whitelist Cc: usb@freebsd.org, yanefbsd@gmail.com, freebsd-current@freebsd.org Subject: Re: The rc.d mess strikes back X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Mar 2009 04:08:04 -0000 M. Warner Losh wrote: > In message: > Garrett Cooper writes: > : On Mar 1, 2009, at 7:36 PM, Garrett Cooper wrote: > : > : > On Mar 1, 2009, at 7:20 PM, Garrett Cooper wrote: > : > > : >> On Mar 1, 2009, at 6:36 PM, Sam Leffler wrote: > : >> > : >>> Garrett Cooper wrote: > : >>>> device ums # Mouse > : >>> > : >>> This is why you cannot kldload. Not sure about any functional > : >>> regression. > : >>> > : >>> Sam > : >> > : >> Yeah, well that message was printed out by another process > : >> altogether while loading up the kernel after the ata subsystem was > : >> brought up, so something's getting confused and trying to kldload > : >> by accident... I was just reproducing the message. > : >> I'll provide more data to prove this claim when I can. > : >> Thanks, > : >> -Garrett > : > > : > Here's the picture from my iPhone: : > >. I OBVIOUSLY didn't do the kldload... and because my /boot/ > : > loader.conf doesn't contain ums_load="YES", I'm really curious who > : > the actual culprit is in rc.d land... > : > I used to do WITHOUT_MODULES=* to not build modules, but I'm trying > : > to move away from that mentality for some things like snd_emu10kx, > : > but obviously there's a conflict somewhere for ums; hopefully it's > : > merely cosmetic... > : > Thanks, > : > -Garrett > : > : Ok, found the culprit. It turns out moused is being called from > : devd... this is all probably related to the startup mess I reported 2 > : weeks ago with my NIC. I'm seeing a lot of additional problems in > : terms of keeping track of daemons; for instance syslogd is getting > : started up twice, but the first instance isn't recording a PID and the > : second one is dying because the first one is bound to the address. > : Agh... > > I didn't think that moused loaded anything. > > And what do extra nics have to do with this? I think you are > confusing multiple problems... > > : Could we just unwind this rc.d mess? It seems to be causing issues > : and wasn't very thoroughly tested before commit. > > This is a little to vague to be actionable. Do you have specific > instances? Do you have rcorder output? Etc... > I saw a similar problem today; if I have a wireless nic setup with ifconfig_ath0="wlan0" ifconfig_wlan0="WPA DHCP" then two instances of wpa_supplicant are launched when I do /etc/rc.d/netif start ath0 (you get log msgs from wpa_supplicant about not being able to setup the /var/run/wpa_supplicant/wlan0 unix domain socket). Wasn't able to pin it down but it's likely the same issue. Sam