From owner-freebsd-current@FreeBSD.ORG Mon Apr 21 16:10:38 2003 Return-Path: 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 25FD237B401 for ; Mon, 21 Apr 2003 16:10:38 -0700 (PDT) Received: from mail.gmx.net (mail.gmx.de [213.165.65.60]) by mx1.FreeBSD.org (Postfix) with SMTP id 4021C43FDF for ; Mon, 21 Apr 2003 16:10:36 -0700 (PDT) (envelope-from mdcki@gmx.net) Received: (qmail 13439 invoked by uid 65534); 21 Apr 2003 23:10:35 -0000 Received: from cvpn015.gwdg.de (EHLO gmx.net) (134.76.22.15) by mail.gmx.net (mp011-rz3) with SMTP; 22 Apr 2003 01:10:34 +0200 Message-ID: <3EA47AAA.7010802@gmx.net> Date: Tue, 22 Apr 2003 01:11:38 +0200 From: Marcin Dalecki User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4a) Gecko/20030419 X-Accept-Language: en-us, en, pl, ru MIME-Version: 1.0 To: Andre Guibert de Bruet References: <200304201807.29531.cbiffle@safety.net> <3EA4122A.8090603@isi.edu> <20030421185255.V56266@alpha.siliconlandmark.com> In-Reply-To: <20030421185255.V56266@alpha.siliconlandmark.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Ben Laurie cc: Lars Eggert cc: Robert Watson cc: FreeBSD Current Subject: Re: Laptop update... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Apr 2003 23:10:38 -0000 > I'm having the same problem with a Dell Latitude C800. I have observed similar problems on my ASUS Silicon Motion LynxEM+ notebook. Well Actually what happens is the usual "black screen and no return". No console switching no whatever. More importantly it's still possible to login remotely in to the machine. There I always find an XFree86 process taking 98% of CPU time. Tracing it showed that it hangs trying to ececute an VESA opscreen operation. Apparently it's XFree which is broken I think. Well it smell further after BIOS calls hanging, since I did have to switch the Option "NoBIOS" on for getting thich chipset working under FreeBSD at all. Otherwise it hangs right at the first try to execute BIOS code. Anyway SIGPOWER is definitively something missing from the UNIX signal list... No clumpsy "help daemon" just SIGPOWER I think...