From owner-freebsd-stable@FreeBSD.ORG Tue Mar 25 19:40:34 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4AB3B1065670; Tue, 25 Mar 2008 19:40:34 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail.speedfactory.net [66.23.216.219]) by mx1.freebsd.org (Postfix) with ESMTP id AA8E38FC14; Tue, 25 Mar 2008 19:40:33 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.8s) with ESMTP id 236713782-1834499 for multiple; Tue, 25 Mar 2008 15:40:16 -0400 Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.14.2/8.14.2) with ESMTP id m2PJePpJ078956; Tue, 25 Mar 2008 15:40:27 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: "Bruce M. Simpson" Date: Tue, 25 Mar 2008 15:19:10 -0400 User-Agent: KMail/1.9.7 References: <47E7D003.3070009@incunabulum.net> <47E8333E.20900@incunabulum.net> <47E8381B.5060100@FreeBSD.org> In-Reply-To: <47E8381B.5060100@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200803251519.10414.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Tue, 25 Mar 2008 15:40:27 -0400 (EDT) X-Virus-Scanned: ClamAV 0.91.2/6392/Tue Mar 25 08:44:02 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: nsouch@freebsd.org, freebsd-stable@freebsd.org Subject: Re: lpbb broken in 6.x? 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, 25 Mar 2008 19:40:34 -0000 On Monday 24 March 2008 07:24:11 pm Bruce M. Simpson wrote: > Bruce M Simpson wrote: > > > > I used devinfo to check if other devices were attached to the ppbus=20 > > parent. ppc0 always has a single child ppbus0. In the first case ppi0=20 > > was attached. In the second case only lpbb appeared to be attached, no= =20 > > other direct children of ppbus0, printing the same message when=20 > > attempting to use the bus ("device not configured"). >=20 > Whoops, I meant "can't allocate ppbus" here, trying to avoid confusion=B7 >=20 > I can't seem to kldunload lpbb or other ppbus modules (if they are=20 > loaded) after they are loaded, this generates a "device not configured"=20 > message. It's not attaching that allocates the bus, it is having one of the devices= =20 open (though /dev/lpt0 tries to only hold the bus while doing actual I/O=20 rather than at open/close). You will probably need to use kgdb to see whic= h=20 device ppbus thinks owns the bus. =2D-=20 John Baldwin