From owner-freebsd-current Thu Sep 6 15:31: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id 712EA37B406; Thu, 6 Sep 2001 15:30:44 -0700 (PDT) Received: from laptop.baldwin.cx (john@[147.11.46.201]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id PAA18198; Thu, 6 Sep 2001 15:30:42 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200109062229.f86MTmo03473@mass.dis.org> Date: Thu, 06 Sep 2001 15:30:39 -0700 (PDT) From: John Baldwin To: Mike Smith Subject: Re: Now 2 ACPI strangeness, both AMD procs Cc: msmith@mass.dis.org, current@FreeBSD.org, Pete Carah 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 On 06-Sep-01 Mike Smith wrote: >> 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. Unless you are on a 80x25 console with a fatal kernel trap and the new console testing code, in which case you may very well lose relevant portions of the panic messages. :-P Also, if his box is resetting after panic'ing it might be too fast. Serial consoles are an excellenet remedy for both of these problems. [ Not directly to you Mike, you know all of this already. ] -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message