Date: Wed, 27 Nov 2002 10:23:05 -0800 From: "Grover, Andrew" <andrew.grover@intel.com> To: "Moore, Robert" <robert.moore@intel.com>, "'Mitsuru IWASAKI'" <iwasaki@jp.FreeBSD.org> Cc: "'acpi-jp@jp.FreeBSD.org'" <acpi-jp@jp.FreeBSD.org>, "'nate@root.org'" <nate@root.org>, "'current@freebsd.org'" <current@freebsd.org> Subject: RE: [acpi-jp 1988] Re: ACPI errors and then panic - fixed! Message-ID: <EDC461A30AC4D511ADE10002A5072CAD04C7A558@orsmsx119.jf.intel.com>
next in thread | raw e-mail | index | archive | help
Our web person is out today, so things will be posted Monday at the earliest. I'll email Iwasaki-san the latest release, so y'all can get going if you want. Regards -- Andy > -----Original Message----- > From: Moore, Robert > Sent: Wednesday, November 27, 2002 8:28 AM > To: 'Mitsuru IWASAKI'; Grover, Andrew; Moore, Robert > Cc: acpi-jp@jp.FreeBSD.org; nate@root.org; current@freebsd.org > Subject: RE: [acpi-jp 1988] Re: ACPI errors and then panic - fixed! > > > > The deleted object problem has been fixed in the 20021122 > release which should be available soon, if not already. (I > was able to reproduce the problem with your dsdt on previous > releases, and I verified it fixed with the 11/22 release.) > > I did not see any mutex issues -- as we found out on Linux, > the OSL implementation of wait_semaphore is often the culprit. > > Bob > > > -----Original Message----- > From: Mitsuru IWASAKI [mailto:iwasaki@jp.FreeBSD.org] > Sent: Wednesday, November 27, 2002 12:37 AM > To: andrew.grover@intel.com; robert.moore@intel.com > Cc: acpi-jp@jp.FreeBSD.org; nate@root.org; current@freebsd.org > Subject: Re: [acpi-jp 1988] Re: ACPI errors and then panic - fixed! > > Hi, Intel folks. > It seems that there is a bug in cached object utilization. > This causes strange behavior; > first evaluation of \_SB_.PCI0.LPC_.EC__.BAT0._BST is OK, but > second (or later) evaluation returns AE_TYPE. > > > acpi_cmbat0: error fetching current battery status -- AE_TYPE > > The raw DSDT is at: > http://www.root.org/~nate/acpi/ibm.dsdt > > I guess that InternalObject was returned to cache in > AcpiUtReleaseToCache() but the same object is still in use > somewhere (for ResultObj ?). > > I could reproduce this problem with acpica debugger. Trace > output attached. I'll track this down later. > > Thanks > > ---- > % acpicadb ibm.dsdt > Loading Acpi table from file ibm.dsdt > utmisc-0802 [11] UtAcquireMutex : Mutex > [ACPI_MTX_Namespace] already acquired by this thread [C25] > utmisc-0802 [11] UtAcquireMutex : Mutex > [ACPI_MTX_Namespace] already acquired by this thread [C25] > Parsing > Methods:...................................................... > .............................................................. > .............................................................. > .............................................................. > .............................................................. > .................................................... > Table [DSDT] - 1208 Objects with 61 Devices 354 Methods 18 > Regions Acpi table [DSDT] successfully installed and loaded > - f _BST > \_SB_.PCI0.LPC_.EC__.BAT0._BST (0x80ba0a8) - Method > \_SB_.PCI0.LPC_.EC__.BAT1._BST (0x80ba6a8) - Method > - debug _SB_.PCI0.LPC_.EC__.BAT0._BST > Executing \_SB_.PCI0.LPC_.EC__.BAT0._BST > 00000 #007F XOr (DerefOf (Index (BT0I, 0x00))) > > % > ArgObj: 0x80b9ea8 <Node> Name BT0I Package 0x80e1ba8 > ArgObj: 0x80f9fa8 <Obj> Integer 0000000000000000 > ArgObj: 0x80fe028 <Obj> Integer 0000000000000000 > 00000 #0037 [EvalSubTree] (Package (0x0D) > { > 0x00, > 0xFFFFFFFF, > 0xFFFFFFFF, > 0x01, > 0x2A30, > 0x00, > 0x00, > 0x01, > 0x01, > "", > "", > "", > "" > }) > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EDC461A30AC4D511ADE10002A5072CAD04C7A558>