From owner-freebsd-acpi@FreeBSD.ORG Fri Jul 21 03:27:41 2006 Return-Path: X-Original-To: acpi@freebsd.org 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 B165916A4DA for ; Fri, 21 Jul 2006 03:27:41 +0000 (UTC) (envelope-from dana.myers@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.228]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB08D43D45 for ; Fri, 21 Jul 2006 03:27:38 +0000 (GMT) (envelope-from dana.myers@gmail.com) Received: by wr-out-0506.google.com with SMTP id 36so314725wra for ; Thu, 20 Jul 2006 20:27:38 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=Isv7gTbmwVUPD4SDCP+cUDGuMyqdgGyud4NJTlJgCnJfCGEQrDcCOS6p9QUgymLKRHxgM5LIDjPxU5K+cE3lySTFBArSLk3OCqzTWfU56giu3uKYlRahM/cOMq0N5CVn8Lpr/CYzNWTjq/gmZ3P5un/e/HbBGuDmUjVJD6mpq6g= Received: by 10.65.138.14 with SMTP id q14mr184645qbn; Thu, 20 Jul 2006 20:27:37 -0700 (PDT) Received: from ?192.168.0.2? ( [67.180.22.170]) by mx.gmail.com with ESMTP id e18sm436382qba.2006.07.20.20.27.36; Thu, 20 Jul 2006 20:27:37 -0700 (PDT) Message-ID: <44C049AD.8040101@gmail.com> Date: Thu, 20 Jul 2006 20:27:41 -0700 From: "Dana H. Myers" User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Nate Lawson References: <20060630160642.D8DC245043@ptavv.es.net> <44BFEADA.8070802@root.org> In-Reply-To: <44BFEADA.8070802@root.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: acpi@freebsd.org Subject: Re: New errors when booting current X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jul 2006 03:27:41 -0000 Nate Lawson wrote: > Kevin Oberman wrote: >> I am seeing large numbers of "bad write" and "bad read" errors from acpi >> since my last update of the OS. I'm getting these from both desktops with >> minimal ACPI capability and my laptop. >> >> I don't see any problems, so I suspect they are cosmetic, but I am >> curious as to what changed to trigger them and whether they might be >> eliminated. >> >> Let me know if you want to see my ASL, but it seems to be happening on >> all of my current systems. >> >> Here is an excerpt from my dmesg on the desktop: >> acpi: bad write to port 0x070 (8), val 0x26 >> acpi: bad read from port 0x071 (8) >> acpi: bad write to port 0x070 (8), val 0x26 >> acpi: bad read from port 0x071 (8) >> acpi: bad write to port 0x070 (8), val 0x26 > > Your ASL is writing to the RTC hardware directly. This is not allowed > by Windows XP and newer systems for obvious reasons. We added the check > recently but do not block the accesses yet. I don't think we use the > RTC much so we're just lucky there's no collision. I'll try to add a > patch soon that only prints the first 5 errors or so but can do more if > we want to use it for debugging. > > http://www.microsoft.com/whdc/system/pnppwr/powermgmt/BIOSAML.mspx Windows apparently does more than block the accesses; it does to some effort to make them work safely. I eventually gave up on most I/O port access control in the Solaris ACPI CA OSL; we'd been running for several years (first with our homegrown interpreter, and then with the ACPI CA port) without port checks and we didn't have a single report of trouble as a result; when I added the checks, I immediately started getting reports of trouble. Dana