Date: Sun, 1 Mar 2009 20:41:35 -0800 From: Garrett Cooper <yanefbsd@gmail.com> To: Andrew Thompson <thompsa@freebsd.org> Cc: usb@freebsd.org, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: ums no longer loads on CURRENT Message-ID: <7d6fde3d0903012041l76436344o6db7660a3fa8cf37@mail.gmail.com> In-Reply-To: <20090302043013.GA66136@citylink.fud.org.nz> References: <CB26D07A-6D29-4B53-B3F1-CD1CAB8AF899@gmail.com> <49AB4649.40906@freebsd.org> <69F972E4-D7C1-47D8-8C83-A44062DB47E1@gmail.com> <20090302043013.GA66136@citylink.fud.org.nz>
index | next in thread | previous in thread | raw e-mail
On Sun, Mar 1, 2009 at 8:30 PM, Andrew Thompson <thompsa@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,
-Garrett
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7d6fde3d0903012041l76436344o6db7660a3fa8cf37>