Date: Mon, 07 Aug 2006 15:19:03 +0100 From: Gavin Atkinson <gavin.atkinson@ury.york.ac.uk> To: Bruno Ducrot <ducrot@poupinou.org> Cc: freebsd-stable@freebsd.org Subject: Re: acpi: bad write to port Message-ID: <1154960343.40530.28.camel@buffy.york.ac.uk> In-Reply-To: <20060807140109.GR17014@poupinou.org> References: <200608071324.k77DObNm028590@lurza.secnetix.de> <44D741AD.4040404@andric.com> <20060807140109.GR17014@poupinou.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 2006-08-07 at 16:01 +0200, Bruno Ducrot wrote: > On Mon, Aug 07, 2006 at 03:35:41PM +0200, Dimitry Andric wrote: > > Oliver Fromme wrote: > > > acpi: bad write to port 0x080 (32), val ... > > ... > > > Do I have to worry? So far it doesn't seem to cause any > > > harm. > > > > It's probably just a buggy BIOS, see: > > http://lists.freebsd.org/pipermail/freebsd-acpi/2006-June/002890.html > > IMO this io (0x80) should not be blacklisted. It's used as a debug port > in that context. However the 0x80 port is a single byte wide - and his AML is trying to write 32 bits to it, so it's falling foul of the (correct) blocking of writes to port in the range 0x81 - 0x83. Gavin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1154960343.40530.28.camel>