Date: Tue, 25 Mar 2008 15:19:10 -0400 From: John Baldwin <jhb@freebsd.org> To: "Bruce M. Simpson" <bms@freebsd.org> Cc: nsouch@freebsd.org, freebsd-stable@freebsd.org Subject: Re: lpbb broken in 6.x? Message-ID: <200803251519.10414.jhb@freebsd.org> In-Reply-To: <47E8381B.5060100@FreeBSD.org> References: <47E7D003.3070009@incunabulum.net> <47E8333E.20900@incunabulum.net> <47E8381B.5060100@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200803251519.10414.jhb>