From owner-acpi-jp@jp.freebsd.org  Fri Oct 13 06:13:03 2000
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id GAA62526;
	Fri, 13 Oct 2000 06:13:03 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from thalia.fm.intel.com (thalia.fm.intel.com [132.233.247.11])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id GAA62521
	for <acpi-jp@jp.freebsd.org>; Fri, 13 Oct 2000 06:13:02 +0900 (JST)
	(envelope-from andrew.grover@intel.com)
Received: from SMTP (fmsmsxvs01-1.fm.intel.com [132.233.42.201])
	by thalia.fm.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.31 2000/08/22 00:15:13 dmccart Exp $) with SMTP id VAA29826
	for <acpi-jp@jp.freebsd.org>; Thu, 12 Oct 2000 21:14:09 GMT
Received: from fmsmsx27.FM.INTEL.COM ([132.233.48.27]) by 132.233.48.201
  (Norton AntiVirus for Internet Email Gateways 1.0) ;
  Thu, 12 Oct 2000 21:12:53 0000 (GMT)
Received: by fmsmsx27.fm.intel.com with Internet Mail Service (5.5.2650.21)
	id <4M7PJBDH>; Thu, 12 Oct 2000 14:12:52 -0700
Message-ID: <4148FEAAD879D311AC5700A0C969E8905DE3DB@orsmsx35.jf.intel.com>
From: "Grover, Andrew" <andrew.grover@intel.com>
To: "'acpi-jp@jp.freebsd.org'" <acpi-jp@jp.freebsd.org>
Date: Thu, 12 Oct 2000 14:12:47 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Reply-To: acpi-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+000315
X-Sequence: acpi-jp 860
Subject: [acpi-jp 860] RE: Latest ACPI megapatch update 
Errors-To: owner-acpi-jp@jp.freebsd.org
Sender: owner-acpi-jp@jp.freebsd.org
X-Originator: andrew.grover@intel.com

Oops, I may have implied that we've already fixed it, but that's not the
case.

I'll keep you updated.

Regards -- Andy

> -----Original Message-----
> From: Mike Smith [mailto:msmith@freebsd.org]
> Sent: Thursday, October 12, 2000 1:37 PM
> To: acpi-jp@jp.freebsd.org
> Subject: [acpi-jp 859] Re: Latest ACPI megapatch update 
> 
> 
> > Our interpreter guy (Bob) has verified this is an 
> interpreter bug, but the
> > fix is not trivial. Hopefully this fix will be in our next 
> release, but
> > can't say for sure.
> 
> Any chance of an early peek at the fix?  I'd be *very* happy 
> to test it, 
> given that I'm crippled by the bug at the moment...

