Date: Mon, 11 Mar 2002 05:40:21 +0100 From: Bernd Walter <ticso@cicely8.cicely.de> To: Christian Weisgerber <naddy@mips.inka.de> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Serial break into debugger broken from 'cu' on -CURRENT? Message-ID: <20020311044020.GE4295@cicely8.cicely.de> In-Reply-To: <a6g7sp$2ect$1@kemoauc.mips.inka.de> References: <Pine.NEB.3.96L.1020310100210.61696P-100000@fledge.watson.org> <20020310161126.A18441@freebie.xs4all.nl> <p0510151db8b13ce922ff@[10.1.1.118]> <20020310175626.A18718@freebie.xs4all.nl> <a6g7sp$2ect$1@kemoauc.mips.inka.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Mar 10, 2002 at 06:15:53PM +0000, Christian Weisgerber wrote: > Wilko Bulte <wkb@freebie.xs4all.nl> wrote: > > > It could be that the DS10 was sufficiently catatonic to not react to > > a break (how likely is that in the first place? I was looking at a hard > > lockup). > > If you experience one of the lockups that currently plague > -CURRENT/alpha, the machine won't react to break, ctrl-alt-esc, or > anything else except HALT and RESET. My testbox (NoName) doesn't even react on halt. But in the normal case a serial break just does what it should do. Serial client is tip from 4.3-20010630-STABLE. My notebook is running -current from 15th feb and tip's break also worked always fine. Well sending the break sequence against an ssh or not after a linebreak are typical mistakes in usage. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de 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?20020311044020.GE4295>