Date: Sun, 10 Mar 2002 08:49:16 -0800 From: Mark Peek <mp@FreeBSD.org> To: Wilko Bulte <wkb@freebie.xs4all.nl>, Robert Watson <rwatson@FreeBSD.ORG> Cc: current@FreeBSD.ORG Subject: Re: Serial break into debugger broken from 'cu' on -CURRENT? Message-ID: <p0510151db8b13ce922ff@[10.1.1.118]> In-Reply-To: <20020310161126.A18441@freebie.xs4all.nl> References: <Pine.NEB.3.96L.1020310100210.61696P-100000@fledge.watson.org> <20020310161126.A18441@freebie.xs4all.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
At 4:11 PM +0100 3/10/02, Wilko Bulte wrote: >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 ;-) Hitting ~# in tip worked fine for me with a -current CVSup'd from yesterday. However, it did stump me for a second until I realized I was initially escaping into SSH and not tip. Mark 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?p0510151db8b13ce922ff>