Date: Mon, 13 Dec 2004 21:57:46 +0900 From: Hidetoshi Shimokawa <simokawa@FreeBSD.org> To: Ulrich Spoerlein <q@uni.de> Cc: freebsd-bugs@FreeBSD.org Subject: Re: kern/74977: dcons.ko requires KDB support Message-ID: <86d5xetkxh.wl@maru5.nunu.org> In-Reply-To: <20041213084319.GA864@galgenberg.net> References: <200412121050.iBCAoc6w052924@coyote.q.local> <87llc3t9n9.wl@tora.nunu.org> <20041213084319.GA864@galgenberg.net>
index | next in thread | previous in thread | raw e-mail
At Mon, 13 Dec 2004 09:43:20 +0100, Ulrich Spoerlein wrote: > > [1 <text/plain; us-ascii (quoted-printable)>] > On Mon, 13.12.2004 at 07:49:14 +0900, Hidetoshi Shimokawa wrote: > > > >Fix: > > > Remove those two 'echo defines' from the Makefile, rebuild the module, > > > dconschat(8) starts working! :) > > > I don't know if this is the right fix however. Is KDB needed on the > > > _client_ to debug the _servers_ Kernel via dconschat? > > > > You don't need dcons(4) on the host system. > > dcons(4) is necessary only on the target system. > > Then I'm doing something wrong. dconschat only worked, when dcons is > loaded on host system. (Target System has loaded dcons and dcons_crom) > > % fwcontrol > 2 devices (info_len=2) > node EUI64 status > 1 20-00-00-00-04-00-52-cf 0 > 0 35-4f-c0-00-35-67-98-30 1 > % dconschat -t 35-4f-c0-00-35-67-98-30 > [dcons disconnected (get crom failed)] > > And nothing ever happens. You may need a manual bus reset after loading dcons(4) on the target system. Try 'fwcontrol -r'. /\ Hidetoshi Shimokawa \/ simokawa@FreeBSD.orghelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86d5xetkxh.wl>