From owner-freebsd-current Sun Dec 1 13:16:12 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 718CD37B401 for ; Sun, 1 Dec 2002 13:16:10 -0800 (PST) Received: from pozo.com (pozo.com [216.101.162.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id D3DC243EBE for ; Sun, 1 Dec 2002 13:16:08 -0800 (PST) (envelope-from null@pozo.com) Received: from quad.pozo.com (quad.pozo.com [216.101.162.53]) by pozo.com (8.12.6/8.12.6) with ESMTP id gB1LG10l000716 (version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NOT); Sun, 1 Dec 2002 13:16:02 -0800 (PST) (envelope-from null@pozo.com) Message-Id: <5.2.0.9.2.20021201131426.00a7a308@pozo.com> X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Sun, 01 Dec 2002 13:16:01 -0800 To: Chuck Robey , FreeBSD-current From: Manfred Antar Subject: Re: console problem In-Reply-To: <20021201155958.Y360-100000@april.chuckr.org> 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 At 04:07 PM 12/1/2002 -0500, Chuck Robey wrote: >I've been on vacation for the last week, so I haven't been watching >-current like a good boy should, but I've suddenly been seeing a serious >problem, and it *might* not have been reported, and seeing as code freeze >is almost here, it's worth risking a bit of embarrassment, I guess. > >Anyhow, it's the console, it's been locking up. I just retried it with a >kernel cvsupped not 2 hours ago, and it's still here. All the vty's lock >up, and once even froze the PC speaker (beeping annoyingly at me). > >There don't seem to be any hung processes. I can use X, and I can also >ssh into the box, so it's the console only. Can't switch to different >vty's, and the one i'm on is frozen, no response to any keys. > >It seems to come on more quickly if I do something serious, like a >buildkernel. Happened once on startup, but even though rc hadn't >finished, I WAS able to ssh into the box and shut it down (indicating to >me that rc had finished, just no response from the console). > >Machine is a 2 processor Tyan Thunder, 1G memory, two Athlons, scsi disks >and eide both. > >---------------------------------------------------------------------------- >Chuck Robey | Interests include C & Java programming, FreeBSD, >chuckr@chuckr.org | electronics, communications, and SF/Fantasy. > >New Year's Resolution: I will not sphroxify gullible people into looking up >fictitious words in the dictionary. >---------------------------------------------------------------------------- > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message I'm seeing the same here and the same on a serial console. Kernel from Friday 29 Nov. 8pm PST sources works So it happened sometime after that Manfred ================================== || null@pozo.com || || Ph. (415) 681-6235 || ================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message