From owner-freebsd-current Sun Mar 10 8:49:25 2002 Delivered-To: freebsd-current@freebsd.org Received: from relay.pair.com (relay1.pair.com [209.68.1.20]) by hub.freebsd.org (Postfix) with SMTP id 7FEE337B405 for ; Sun, 10 Mar 2002 08:49:22 -0800 (PST) Received: (qmail 39954 invoked from network); 10 Mar 2002 16:49:21 -0000 Received: from 12-236-89-83.client.attbi.com (HELO ?10.1.1.118?) (12.236.89.83) by relay1.pair.com with SMTP; 10 Mar 2002 16:49:21 -0000 X-pair-Authenticated: 12.236.89.83 Mime-Version: 1.0 X-Sender: (Unverified) Message-Id: In-Reply-To: <20020310161126.A18441@freebie.xs4all.nl> References: <20020310161126.A18441@freebie.xs4all.nl> Date: Sun, 10 Mar 2002 08:49:16 -0800 To: Wilko Bulte , Robert Watson From: Mark Peek Subject: Re: Serial break into debugger broken from 'cu' on -CURRENT? Cc: current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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