From owner-freebsd-current@FreeBSD.ORG Wed Apr 5 18:46:41 2006 Return-Path: X-Original-To: current@freebsd.org 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 EBB4016A430 for ; Wed, 5 Apr 2006 18:46:40 +0000 (UTC) (envelope-from harikurniawan@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7644B43D46 for ; Wed, 5 Apr 2006 18:46:38 +0000 (GMT) (envelope-from harikurniawan@gmail.com) Received: by zproxy.gmail.com with SMTP id 13so16734nzp for ; Wed, 05 Apr 2006 11:46:37 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:mime-version:content-type; b=gGbuBUnjkwlIHpHrOZEEi5tXcOwr98gnjR7Nj6Bm0PHm5DvWCRN6Z/4IW62K4xnQ0Z7JwXEAb0eROlBFqBPJCWsEmr6U0eDhUM/znqYNX8gvAqgZJtlt7K+HJySFLSud6cBvvpE2yJHieP0fskdcwHkOyALxWLFvhOBaGIuR3u8= Received: by 10.64.143.4 with SMTP id q4mr54035qbd; Wed, 05 Apr 2006 11:46:37 -0700 (PDT) Received: by 10.64.201.6 with HTTP; Wed, 5 Apr 2006 11:46:37 -0700 (PDT) Message-ID: <4c40c4e70604051146y48cc35fal1680d5121f73ab29@mail.gmail.com> Date: Wed, 5 Apr 2006 18:46:37 +0000 From: "Angka H. K." To: "Nate Lawson" MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_3413_6255684.1144262797216" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Alexander Leidinger , current@freebsd.org Subject: ACPI Error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 05 Apr 2006 18:46:41 -0000 ------=_Part_3413_6255684.1144262797216 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Great the error is gone now thanks. I have other question about ACPI. My dmesg showing like below and I know nothing about ACPI. What does it mean and can it be fix ? acpi_perf0: on cpu0 acpi_perf0: failed in PERF_STATUS attach device_attach: acpi_perf0 attach returned 6 acpi_perf0: on cpu0 acpi_perf0: failed in PERF_STATUS attach device_attach: acpi_perf0 attach returned 6 On 4/4/06, Angka H. K. wrote: > > Thanks a lot, you really dedicate your time to FreeBSD > Sorry I still don't have good connection to do cvsup, may be tomorrow. > > Ah.. hard time to finish my job sorry can't help :( > > > On 4/4/06, Nate Lawson wrote: > > > Angka H. K. wrote: > > > Thanks for the replay > > > I am updating my source now and planing to rebuild it again, but I > > don't see > > > any changes on ACPI code. > > > > > > I was mistype on the val that return by kernel, the error should be > > "acpi: > > > bad write to port 0x073(8) val 20", I am sorry. > > > Hope it'll be fixed soon. > > > > Ok, I fixed the range check on ports so 0x73 should not trigger it. If > > you have some other write to a port that IS in the blacklist, you'll > > still get the warning. > > > > Ultimately, I intend to emulate what Windows does which is block all > > writes to the PIC, and block all writes on XP or newer BIOSen. > > > > -- > > Nate > > > > ------=_Part_3413_6255684.1144262797216--