Date: Sun, 10 Mar 2002 16:11:26 +0100 From: Wilko Bulte <wkb@freebie.xs4all.nl> To: Robert Watson <rwatson@FreeBSD.ORG> Cc: current@FreeBSD.ORG Subject: Re: Serial break into debugger broken from 'cu' on -CURRENT? Message-ID: <20020310161126.A18441@freebie.xs4all.nl> In-Reply-To: <Pine.NEB.3.96L.1020310100210.61696P-100000@fledge.watson.org>; from rwatson@FreeBSD.ORG on Sun, Mar 10, 2002 at 10:07:07AM -0500 References: <Pine.NEB.3.96L.1020310100210.61696P-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Mar 10, 2002 at 10:07:07AM -0500, Robert Watson wrote: > > For the past couple of months, I've been working with a set of identical > test boxes from SGI which, for some reason, stopped responding to serial > break on the serial console. I switched to the 'alternative break' option > in LINT, and things work fine. I assumed it was actually some issue with > that particular batch of machines, since no one else had had a problem, > and I didn't really have time to follow up. Yesterday, I brought online > two more crash boxes via serial console, both older TeleNet servers, and > noticed that neither of them respond to serial break over the serial > console using cu. This leads me to wonder two things: > > (1) Is serial break currently broken in -CURRENT > (2) Is serial break currently broken in 'cu'? I had similar experiences with tip trying to break into ddb on the AlphaStation DS10 with -current. I thought it was just me ;-) -- | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, the Netherlands 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?20020310161126.A18441>