From owner-freebsd-current@FreeBSD.ORG Thu Jun 19 00:33:50 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 CF8C537B404 for ; Thu, 19 Jun 2003 00:33:50 -0700 (PDT) Received: from anduin.net (anduin.net [212.12.46.226]) by mx1.FreeBSD.org (Postfix) with SMTP id B449A43FAF for ; Thu, 19 Jun 2003 00:33:49 -0700 (PDT) (envelope-from ltning@anduin.net) Received: (qmail 14711 invoked from network); 19 Jun 2003 07:33:47 -0000 Received: from celduin.net (HELO anduin.net) (81.0.162.106) by anduin.net with SMTP; 19 Jun 2003 07:33:47 -0000 Message-ID: <3EF16755.4090903@anduin.net> Date: Thu, 19 Jun 2003 09:33:41 +0200 From: Eirik Oeverby User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: ACPI issues on ThinkPad T21 + Dock 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: Thu, 19 Jun 2003 07:33:51 -0000 Hello all! I've been tinkering with 5.1 (-current) for a while now, ever since it was released. I checked out code and recompiled my kernel as late as yesterday evening. Since the install, I have encountered a few problems that I'd like to discuss: - When my machine is docked, I *have to* enable ACPI, otherwise it will not boot past 'Mounting root from ufs:/dev/ad0s1a' (and the following WARNING about / not being unmounted cleanly, if the next point happened to be true) - When booted with ACPI enabled (docked), the machine will at some point simply power itself off. I have seen people complaining about similiar machines powering themselves *on* after a power-off, but in my case it's the opposite. Out of nothing, with no warning (that I can see), it simply powers off. It's not suspend either, or hibernation or anything. - I have not been able to reproduce any of these problems while the machine is undocked. In fact, it seems to work pretty well both on battery power and while plugged in - it's only while it's docked I'm having these problems. They are consistent and effectively keep me from using the computer while docked. If anyone wants to look more into this, I'll be happy to provide whatever information is necessary. Please let me know. The system is running at the latest firmware level. There are no 'firmwares' for the docking station, so there is nothing I can do there. /Eirik Oeverby