From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1SV8ix-0001UH-N9 for garchives@archives.gentoo.org; Thu, 17 May 2012 21:59:08 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id BDD17E0B50; Thu, 17 May 2012 21:58:46 +0000 (UTC) Received: from mail-lb0-f181.google.com (mail-lb0-f181.google.com [209.85.217.181]) by pigeon.gentoo.org (Postfix) with ESMTP id 94C0DE0AE6 for ; Thu, 17 May 2012 21:57:01 +0000 (UTC) Received: by lbbgk8 with SMTP id gk8so1874276lbb.40 for ; Thu, 17 May 2012 14:57:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:x-google-sender-auth:message-id :subject:to:content-type; bh=aPdfxZEQSUdEjI9kHjMrtdz4nAYF5yKLaV9RYsG36A8=; b=Y+tgEEKA8t1rRV8+mu/6leGcf5R8TbOn/SuYwUlppFhb6SrZYAjhAA3p3WyBSpoVUT JKUwb8MFRR1ro8MOg8fHG26EnLiY63Bj8UNqKUzIZ70PN6Wk0lLgm8oasd0C7QXkegtp FbtN+tZRonULVYD7Ag54KuS9liv3LUfZvf4spf1q3Ak9gChgS22J2/VBZA/gZeQLATb9 Y0AdqEt4bSQTsKRawarTh9rakOeEGbV3zheR7Q+h1N4IwkR9tkUiSqDNupe8Jih+NpJP mtjHPrkkvjzjjEGi/gyB0fiGz3AUa9KSi8Jpo/WlxwsWBR9utE0FywVDiWweKAS1Tfae ik3w== Received: by 10.112.28.131 with SMTP id b3mr3746907lbh.63.1337291820524; Thu, 17 May 2012 14:57:00 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Sender: paul.hartman@gmail.com Received: by 10.112.77.4 with HTTP; Thu, 17 May 2012 14:56:40 -0700 (PDT) From: Paul Hartman Date: Thu, 17 May 2012 16:56:40 -0500 X-Google-Sender-Auth: kRqjjh97XYterNhrZIxSeueogWU Message-ID: Subject: [gentoo-user] Any DSDT/AML gurus out there? To: Gentoo User Content-Type: text/plain; charset=ISO-8859-1 X-Archives-Salt: 72ec1c7d-215b-4b1b-8f25-7d274c9d3792 X-Archives-Hash: 6d340ff5863af42aa2e32734d1580401 Hi, I have a laptop which apparently has a buggy DSDT. It is possible to decompile and recompile it, including it in an in-kernel initramfs to override the one in BIOS, as described by the somewhat outdated example at: http://www.lesswatts.org/projects/acpi/overridingDSDT.php My main problem is that the AML code that it generates is completely foreign to me and I'm unable to tell what exactly the problem is. Most examples on the web explain fixing compilation errors, which are fairly obvious. Mine has no errors - only warnings. I think there is a logical error leading to an infinite loop condition. My previous attempts to fix it have only resulting in even worse results (no battery readings at all, ever, lack of power management in general, that kind of fun stuff). Normally, my laptop battery readings will work perfectly well until suddenly, randomly it shows this in dmesg: [ 6286.707038] ACPI Error: Method parse/execution failed [\_SB_.PCI0.PIB_.EC0_.SMWR] (Node ffff88007d028348), AE_AML_INFINITE_LOOP (20120111/psparse-536) [ 6286.707074] ACPI Error: Method parse/execution failed [\_SB_.PCI0.PIB_.EC0_.SMSL] (Node ffff88007d028398), AE_AML_INFINITE_LOOP (20120111/psparse-536) [ 6286.707096] ACPI Error: Method parse/execution failed [\_SB_.PCI0.PIB_.EC0_._Q09] (Node ffff88007d028438), AE_AML_INFINITE_LOOP (20120111/psparse-536) After that, the battery state can no longer be read and eventually spontaneously powering off without proper shutdown when the battery dies. The problem does not occur in Microsoft Windows (or windows handles it better), but I don't normally use Microsoft Windows, so that doesn't help me any. :) Has anyone on this list dealt with this before, or have any ideas to help guide me along? I'd be happy to send the code to anyone interested in trying their hand at fixing it. Thanks, Paul