Date: Tue, 25 Apr 2000 14:36:41 +0930 From: Greg Lehey <grog@lemis.com> To: Doug Rabson <dfr@nlsystems.com> Cc: FreeBSD Committers <cvs-committers@freebsd.org>, FreeBSD current users <FreeBSD-current@freebsd.org> Subject: Re: Remote serial gdb is broken in -CURRENT. Message-ID: <20000425143641.J26934@freebie.lemis.com> In-Reply-To: <Pine.BSF.4.21.0004231007130.62105-100000@salmon.nlsystems.com> References: <20000423154307.L4675@freebie.lemis.com> <Pine.BSF.4.21.0004231007130.62105-100000@salmon.nlsystems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday, 23 April 2000 at 10:07:38 +0100, Doug Rabson wrote: > On Sun, 23 Apr 2000, Greg Lehey wrote: > >> In the last few days, my remote serial gdb has almost completely >> stopped working. Previously I had (almost) no trouble at 38400 bps; >> now I can barely get a response at all at 9600 bps. Does anybody have >> an idea where this could be coming from? > > I noticed this too but I have no idea why. I also had to move back to > 9600. I've found the problem and fixed it. It's been broken all along, but for some reason it got worse lately. Basically, what happened was that the getpacket function, which does polled I/O, wasn't locking out interrupts, and something was interrupting long enough for characters to get lost. Since sometimes several consecutive characters got lost, it seems likely that either something locks out interrupts for an inappropriately long time, or the sio interrupt routines steal them. Anyway, it works nicely at 115200 bps now. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000425143641.J26934>