Date: Fri, 25 Apr 2008 09:49:21 +1000 From: Peter Jeremy <peterjeremy@optushome.com.au> To: Zbigniew Baniewski <zb@ispid.com.pl> Cc: freebsd-acpi@freebsd.org Subject: Re: Problem with ACPI using Abit BE6-II V2.0 Message-ID: <20080424234921.GR92261@server.vk2pj.dyndns.org> In-Reply-To: <20080424171712.GA5180@sarge.my.own.domain.no-net> References: <20080420134236.GA6019@sarge.my.own.domain.no-net> <480C0DEF.2030707@root.org> <20080421095156.GA5263@sarge.my.own.domain.no-net> <58AFE814-343F-4F83-94DA-A2979180C512@FreeBSD.org> <20080424171712.GA5180@sarge.my.own.domain.no-net>
next in thread | previous in thread | raw e-mail | index | archive | help
--Z1OTrj3C7qypP14j Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Apr 20, 2008 at 03:42:36PM +0200, Zbigniew Baniewski wrote: >3. When booted with "verbose", there are steadily error messages printed on >first console: > > acpi: bad write to port 0x070 (8), val 0x4c > acpi: bad read from port 0x071 (8) To quote sys/dev/acpica/Osd/OsdHardware.c: * Some BIOS vendors use AML to read/write directly to IO space. This * can cause a problem if such accesses interfere with the OS's access to * the same ports. Windows XP and newer systems block accesses to certain * IO ports. We print a message or block accesses based on a tunable. ports 0x070 and 0x071 refer to the RTC & CMOS RAM and are blocked but it seems your AML wants to access location 0x4c. FreeBSD prints out a warning when in verbose mode. On Thu, Apr 24, 2008 at 07:17:12PM +0200, Zbigniew Baniewski wrote: >On Thu, Apr 24, 2008 at 03:26:34PM +0100, Rui Paulo wrote: > >> The problem is that old boards have buggy ACPI implementations. It =20 >> might work on FreeBSD, or it might not. > >I suppose, if it can work on Linux, it can (and should) work on FreeBSD to= o. >Why not, actually? On the same motherboard I tried NetBSD in versions 2.0 >and 3.0 - there weren't ACPI-related problems. Different OSs will have different work-arounds for ACPI bugs and/or will rely on different ACPI features. It seems most likely that FreeBSD is relying on ACPI features that are not working in your ACPI. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --Z1OTrj3C7qypP14j Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.8 (FreeBSD) iEYEARECAAYFAkgRHIEACgkQ/opHv/APuIed+QCfQv/qkDN623lkoE9TXDhKHWhp u7sAoJx2wJSb8ClyB6KTJRvUP+P/6xgi =heNn -----END PGP SIGNATURE----- --Z1OTrj3C7qypP14j--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080424234921.GR92261>