From owner-freebsd-current Fri Oct 19 1:25:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by hub.freebsd.org (Postfix) with ESMTP id 5C12A37B409; Fri, 19 Oct 2001 01:25:30 -0700 (PDT) Received: from vega.vega.com (h195.227.dialup.iptcom.net [212.9.227.195]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id LAA78185; Fri, 19 Oct 2001 11:24:33 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.11.6/8.11.3) with ESMTP id f9J8O1U68002; Fri, 19 Oct 2001 11:24:01 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <3BCFE398.51EA76F@FreeBSD.org> Date: Fri, 19 Oct 2001 11:26:00 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U) X-Accept-Language: en,uk,ru MIME-Version: 1.0 To: Mike Smith , Mitsuru IWASAKI , ache@nagual.pp.ru, current@FreeBSD.org, acpi-jp@jp.FreeBSD.org Subject: Re: ACPI: problem with fdc resource allocation References: <200110022356.f92Nuit03147@mass.dis.org> <3BBADCB7.456D51AD@FreeBSD.org> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Maxim Sobolev wrote: > > Mike Smith wrote: > > > This just isn't going to work. The _CRS data stream stops at byte 0x17, > > and these extra items are simply mis-aimed. > > > > The 0x19 should really be 0x11, and the 0x1c should really be 0x14, ie. > > this is a BIOS bug, and should be reported to the vendor. (It should > > also have failed the Microsoft ACPI validation suite...) > > > > The correct action should probably be to silently discard the write > > operations outside of a defined buffer, and return Zeroes or Ones for a > > read outside a buffer. > > Do you have a patch to test this approach? While I understand that the best way to > resolve the problem is to convince vendors to fix their ACPI implementations, but > obviously this isn't going to happen any time soon, so appropriate workarround is > really a must. The problem is still here as of today's kernel. Please do something about it. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message