From owner-freebsd-current Fri Jan 3 11:17: 1 2003 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 6671537B401 for ; Fri, 3 Jan 2003 11:17:00 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 6056343EB2 for ; Fri, 3 Jan 2003 11:16:58 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 99302 invoked by uid 1000); 3 Jan 2003 19:16:57 -0000 Date: Fri, 3 Jan 2003 11:16:57 -0800 (PST) From: Nate Lawson To: Trent Nelson Cc: freebsd-current@freebsd.org Subject: Re: System freeze running -current In-Reply-To: <20030103151234.GA21140@arpa.com> 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 On Fri, 3 Jan 2003, Trent Nelson wrote: > I've experienced -current lock up in exactly the same way twice now; > once with 5.0-RC2, and just now, with sources from 30th December. > > The system in question is a Sharp PC-AR50 laptop. In both instances > the system was idle and I was editing a file in vim on ttyv0. Both > systems exhibited the following symptoms: > > 1. Able to switch terminals using alt-F1..F8, but that's it, I'm un- > able to type anything else (keyboard doesn't respond to letters, > numbers, but capslock and numlock still turn on lights). > 2. Responds to pings from other systems on the network. Sounds like an atkbd or syscons problem. Did you suspend the laptop and resume before this happens? How does "unset acpi_load" at the boot prompt change things? -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message