From owner-freebsd-current  Thu Sep  6 15:23:30 2001
Delivered-To: freebsd-current@freebsd.org
Received: from mass.dis.org (mass.dis.org [216.240.45.41])
	by hub.freebsd.org (Postfix) with ESMTP id DC6C837B403
	for <current@freebsd.org>; Thu,  6 Sep 2001 15:23:26 -0700 (PDT)
Received: from mass.dis.org (localhost [127.0.0.1])
	by mass.dis.org (8.11.6/8.11.3) with ESMTP id f86MTmo03473;
	Thu, 6 Sep 2001 15:29:48 -0700 (PDT)
	(envelope-from msmith@mass.dis.org)
Message-Id: <200109062229.f86MTmo03473@mass.dis.org>
To: Pete Carah <pete@ns.altadena.net>
Cc: current@freebsd.org, msmith@mass.dis.org
Subject: Re: Now 2 ACPI strangeness, both AMD procs 
In-Reply-To: Message from Pete Carah <pete@ns.altadena.net> 
   of "Wed, 05 Sep 2001 22:15:04 PDT." <200109060515.f865F5i65849@ns.altadena.net> 
Date: Thu, 06 Sep 2001 15:29:48 -0700
From: Mike Smith <msmith@freebsd.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

> K6-2-450, bus running at 95mhz, Acer 1541 (A? B?)
> 
> All works fine with the new ACPI _except_ the clock; the time of day
> advances about twice as fast as it should, and I get LOTS of
> calcru negative time and time went backwards messages.

We've seen this before; the Acer Aladdin X clocks are busted.  Turn off
the ACPI timer.

A 'better' solution is going to be for us to sanity-check the ACPI
timer and not use it when it's broken.  I really need someone with one
of these busted boards to spend a little time looking at the (really,
really simple) code and experimenting to see what's going on.

> My athlon MB (ASUS A7V) still won't boot with the new ACPI, at all.
> Dies with a panic trying to attach something, saying can't allocate memory.
> The message disappears too fast to remember what it objected to; I think
> it was the fxp card.

When the system panics, it *stops*.  The message doesn't "disappear" at all.
Please capture whatever is happening and write it down; this isn't a useful
bug report.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message