From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 29 22:13:35 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF92B16A4CE for ; Sun, 29 Aug 2004 22:13:35 +0000 (GMT) Received: from newmail.slackdot.org (mail2.slackdot.org [66.92.146.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E21843D1F for ; Sun, 29 Aug 2004 22:13:35 +0000 (GMT) (envelope-from deker@slackdot.org) Received: from localhost (localhost [127.0.0.1]) by newmail.slackdot.org (Postfix) with ESMTP id 276E418032 for ; Sun, 29 Aug 2004 18:13:02 -0400 (EDT) Received: from newmail.slackdot.org ([127.0.0.1]) by localhost (newmail.slackdot.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19890-06 for ; Sun, 29 Aug 2004 18:12:59 -0400 (EDT) Received: from [192.168.0.2] (unknown [192.168.0.2]) by newmail.slackdot.org (Postfix) with ESMTP id 476731801D for ; Sun, 29 Aug 2004 18:12:59 -0400 (EDT) From: Rob Deker To: freebsd-hackers@freebsd.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-Dt76DS0nVsjP63p3lXhX" Message-Id: <1093817592.8552.90.camel@nyx.slackdot.org> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sun, 29 Aug 2004 18:13:12 -0400 X-Virus-Scanned: by amavisd-new at slackdot.org Subject: Serial consoles and remote GDB X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Aug 2004 22:13:35 -0000 --=-Dt76DS0nVsjP63p3lXhX Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi folks, New to the list, so please bear with me if this is a question that's been answered someplace before. I've been searching and can't seem to find an answer. I'm doing some driver hacking w/ FreeBSD 5.2.1 and I've hit a spot where my life would be much easier if I had remote GDB for kernel debugging. I am however using a serial console on this box, and can't seem to get things working so that I have console access to the box on one serial port and remote gdb running on the other one. Is this possible? I've tried various combinations of port flags for sio[01] in the device.hints file, but I'm not having much luck. I've tried toe following combinations (with the following results): - hint.sio.0.flags=3D"0x10" hint.sio.1.flags=3D"0x80" =20 This yeilded a console initially at boot, but one I told the loader to go ahead and boot the kernel, all I got for output were repeated 0x8e chars (looks like an accented capital 'A'). so, i figured that it might possibly be that the lowest numbered port should be the one with 0x80 set in flags, so I tried: - hint.sio.0.flags=3D"0x80" hint.sio.1.flags=3D"0x10" This got me (again) a console up until kernel load, but after that I had NO output at all. I'm open to any suggestions. My problem is that the machines that are the debug target and debug host are in my basement headless while my office is upstairs and I really would like to avoid running up and down stairs every time I need to switch in and out of gdb mode in ddb (no matter how much I might need the exercise ;) Thanks, -d --=-Dt76DS0nVsjP63p3lXhX Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQBBMlT4iIu2X5vnl3ERAomZAKCafh6gFTqa2yzMhp+yaTTIvioUEgCeMjuU cArpqeXprN+qN8juaV7seFQ= =m64J -----END PGP SIGNATURE----- --=-Dt76DS0nVsjP63p3lXhX--