On Sun, Mar 01, 2009 at 08:41:35PM -0800, Garrett Cooper wrote: > On Sun, Mar 1, 2009 at 8:30 PM, Andrew Thompson <thompsa_at_freebsd.org> wrote: > > On Sun, Mar 01, 2009 at 07:20:03PM -0800, 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. > > > > I have traced this already but not looked into why, the process trying > > to (re)load ums is moused. > > > > > > Andrew > > It's being done from devd's end, but I'd really like it if the > terse messaging would go away because it confused the heck out of > me... the issue was ABI/libmap.conf related like Warner put down in > UPDATING, but I instead opened up another can of worms ;(... > Thanks, A quick look found it, static int usbmodule(void) { return (kld_isloaded("uhub/ums") || kld_load("ums") != -1); } its now called ushub/ums. It can probably be renamed back to uhub now. AndrewReceived on Mon Mar 02 2009 - 03:44:56 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:43 UTC