From owner-freebsd-current@FreeBSD.ORG Mon Mar 2 03:51:46 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 DE901106564A; Mon, 2 Mar 2009 03:51:46 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 7CCC68FC13; Mon, 2 Mar 2009 03:51:46 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.2/8.14.1) with ESMTP id n223nuFa009756; Sun, 1 Mar 2009 20:49:56 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 01 Mar 2009 20:50:17 -0700 (MST) Message-Id: <20090301.205017.1025328203.imp@bsdimp.com> To: yanefbsd@gmail.com From: "M. Warner Losh" In-Reply-To: References: <69F972E4-D7C1-47D8-8C83-A44062DB47E1@gmail.com> <6D5C9BFA-CCF4-4AEE-9688-23D66D594BC6@gmail.com> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: usb@freebsd.org, 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 03:51:47 -0000 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... Warner