Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 18 May 2009 00:10:27 +0200
From:      Lucius Windschuh <lwindschuh@googlemail.com>
To:        Sam Leffler <sam@freebsd.org>
Cc:        Weongyo Jeong <weongyo@freebsd.org>, current@freebsd.org
Subject:   Re: HEADSUP: uath(4) has been committed.
Message-ID:  <90a5caac0905171510v17441d4na51a059f72f7ecae@mail.gmail.com>
In-Reply-To: <4A106B49.4020809@freebsd.org>
References:  <20090407022956.GA71377@weongyo.cdnetworks.kr> <90a5caac0905161502x3771072n22d58111a235de24@mail.gmail.com> <4A0F419A.2020700@freebsd.org> <90a5caac0905171218r6de3473le8edcac3dab7e2bb@mail.gmail.com> <4A106B49.4020809@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for the commits.

But... I forgot one thing: kldunload if_uath ; kldload if_uath on a
firmware-loaded device leads to this output:

uath0: timeout waiting for reply to cmd 0x1 (1)
uath0: could not initialize adapter
device_attach: uath0 attach returned 35
uath0: timeout waiting for reply to cmd 0x1 (1)
uath0: could not initialize adapter
device_attach: uath0 attach returned 35

Is this also a known problem?

Lucius



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?90a5caac0905171510v17441d4na51a059f72f7ecae>