From owner-freebsd-current Fri Mar 8 15: 1: 4 2002 Delivered-To: freebsd-current@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id ECF0437B42F for ; Fri, 8 Mar 2002 15:00:30 -0800 (PST) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020308230030.QNET1147.rwcrmhc52.attbi.com@InterJet.elischer.org>; Fri, 8 Mar 2002 23:00:30 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id OAA50496; Fri, 8 Mar 2002 14:42:07 -0800 (PST) Date: Fri, 8 Mar 2002 14:42:06 -0800 (PST) From: Julian Elischer To: David Wolfskill Cc: current@freebsd.org Subject: Re: Keyboard (quasi-)lockup running script In-Reply-To: <200203082202.g28M2cS30276@bunrab.catwhisker.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 cvs checkout -D "8PM last Monday" :-) (or similar....) On Fri, 8 Mar 2002, David Wolfskill wrote: > Is anyone else seeing this? > > Running -CURRENT (been tracking it daily for a while, now), I find that > if I run script(1), things basically run as expected... until I try to > close script's stdin (normally, by entering EOT (^D)). > > At that point, I can use the mouse (if I'm in an environment where that > makes sense); I can switch among the ttyvNs (up to a point), but nothing > indicates that any (other) characters are being read -- I can't use > Ctl+Alt+Esc to break into the debugger; can't Ctl+Alt+Del to reboot -- > it's power-cycle time (unless I remembered[*] that this was going to > happen, and set up an "at" task to reboot at some auspicious time in the > (near) future. > > I first noticed this a few days ago, in conjunction with my normal build > sequence: I would fire up screen(1), within that "screen" session, fire > up script(1), do the "make buildworld" & friends; after the mergemaster, > I'd exit script(1), then reboot. > > Except that (starting a few days ago -- between Sunday - Tuesday, I > think) I would hit ^D on the script session, and fail to get a shell > prompt back. I could still type on xterms displayed on my laptop (the > machine I was upgrading at the time) that were actually running on other > machines (and get expected/useful responses back, too). And as > alluded to above, setting up an "at" task ahead of time appears to > work OK. > > I had thought that there might be some correlation bewteen this and some > whines (warning messages) I was seeing from sudo(8), since I needed to > have a different sudo executable for -CURRENT than I do for -STABLE. > So, this afternoon, I removed sudo & re-built it (under today's > -CURRENT). > > But then I discovered that the behavior (quasi-lockup) occurs even if I > use script(1) as a "normal" user -- no use of sudo at all. > > This would seem to be A Bad Thing. > > Here's my recent CVSup history: > freebeast(4.5-S)[4] tail /var/log/cvsup-history.log > CVSup begin from cvsup14.freebsd.org at Mon Mar 4 03:47:03 PST 2002 > CVSup ended from cvsup14.freebsd.org at Mon Mar 4 03:53:29 PST 2002 > CVSup begin from cvsup14.freebsd.org at Tue Mar 5 03:47:07 PST 2002 > CVSup ended from cvsup14.freebsd.org at Tue Mar 5 03:54:20 PST 2002 > CVSup begin from cvsup14.freebsd.org at Wed Mar 6 03:47:02 PST 2002 > CVSup ended from cvsup14.freebsd.org at Wed Mar 6 03:53:38 PST 2002 > CVSup begin from cvsup14.freebsd.org at Thu Mar 7 03:47:02 PST 2002 > CVSup ended from cvsup14.freebsd.org at Thu Mar 7 03:53:22 PST 2002 > CVSup begin from cvsup14.freebsd.org at Fri Mar 8 03:47:03 PST 2002 > CVSup ended from cvsup14.freebsd.org at Fri Mar 8 03:53:39 PST 2002 > > And the laptop is presently running: > g1-6(5.0-C)[1] uname -a > FreeBSD g1-6.catwhisker.org 5.0-CURRENT FreeBSD 5.0-CURRENT #93: Fri Mar 8 08:17:09 PST 2002 root@g1-7.catwhisker.org:/common/S3/obj/usr/src/sys/LAPTOP_30W i386 > g1-6(5.0-C)[2] > > > If some kind soul would care to loan me a clue, I'll be happy to > hunt for causes and such. I can provide kernel configs, dmesg > output, and the like on a Web page, if that would be useful -- but > what I'm asking for at this point is hints for narrowing the scope > down somewhat from "the entire known universe". (OK; that was > melodramatic. Sorry.) > > * "It's a poor sort of memory that only works backaards," the Queen > remarked. -- Lewis Carroll; _Through the Looking-Glass_ ("Wool and > Water") > > Thanks, > david > -- > David H. Wolfskill david@catwhisker.org > I believe it would be irresponsible (and thus, unethical) for me to advise, > recommend, or support the use of any product that is or depends on any > Microsoft product for any purpose other than personal amusement. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message