From owner-freebsd-acpi@FreeBSD.ORG Sat Jul 10 22:58:07 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0938916A4CF for ; Sat, 10 Jul 2004 22:58:07 +0000 (GMT) Received: from pfepa.post.tele.dk (pfepa.post.tele.dk [195.41.46.235]) by mx1.FreeBSD.org (Postfix) with ESMTP id 891D743D1F for ; Sat, 10 Jul 2004 22:58:06 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (0x50c7990f.naenxx7.adsl-dhcp.tele.dk [80.199.153.15]) by pfepa.post.tele.dk (Postfix) with ESMTP id 21F9647FE11 for ; Sun, 11 Jul 2004 00:58:04 +0200 (CEST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.11/8.12.11) with ESMTP id i6AMvhTr002747 for ; Sun, 11 Jul 2004 00:57:44 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: acpi@freebsd.org From: Poul-Henning Kamp Date: Sun, 11 Jul 2004 00:57:42 +0200 Message-ID: <2746.1089500262@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Subject: IBM Thinkpad T41p ACPI trouble. X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jul 2004 22:58:07 -0000 I bought a Thinkpad T41p some weeks back, and to my delight ACPI worked flawlessly. I could adjust the backlight, turn the little white "head light" led on and off, suspend etc. Then at some point, it started wedging solid at the mere thought of ACPI. Touching the "Fn" key and any other key is pure death, but touching the Fn key alone gives me a NUL-char. Tonight I went timetravelling with my kernel and get as far back as first of may, but all along the same instant death if ACPI was provoked. It is not quite instant if the laptop is running on batteries, but it still dies within a few seconds. The hang has all the hallmark properties of an interrupt storm, but no kernel warning about interrupt storm results. I fully understand what a wretched monster ACPI is and that I know only the tiniest amount about what it is and does, but I'd like to offer my help debugging this bug anyway. Anyone have some good and clear suggestions for how to go from here ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.