Date: Fri, 23 Jan 2009 14:58:08 +0000 From: "Bruce M. Simpson" <bms@FreeBSD.org> To: John Baldwin <jhb@freebsd.org> Cc: current@freebsd.org Subject: Re: [PATCH] ppbus/ppc locking Message-ID: <4979DB00.10503@FreeBSD.org> In-Reply-To: <4979D2C3.1050103@FreeBSD.org> References: <200811191503.02192.jhb@freebsd.org> <200901211536.08297.jhb@freebsd.org> <4979BF48.7010704@FreeBSD.org> <200901230838.35340.jhb@freebsd.org> <4979D2C3.1050103@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Bruce M. Simpson wrote: > John Baldwin wrote: >> ... >> Hmm you don't see /dev/lpt0 and /dev/lpt0.ctl via ls(1)? The attach >> routine creates the devices via make_dev() right after the >> "interrupt-driven port" message. >> >> > > I see /dev/lpt0.ctl, but not /dev/lpt0. As per IRC convo: * I instrumented lpt_attach() to clean up if it can't create the cdevs. * If I then kldload lpt after boot in single-user, and ls /dev, the ls process hangs inside devfs_populate_loop(). Something really fishy is going on. I don't see this issue with devfs if I load lpt from the loader, however, lpt0 doesn't appear there either. I still see the destroy_devl() panic if I kldunload lpt. This probably shouldn't be MFCed until this can get sorted out... in the meantime, this is my home repo box / smb / print server, need it up, and need to fix the total RAID meltdown I experienced yesterday after first trying this patch (I don't think this patch is to blame here), so, back to work :/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4979DB00.10503>