From owner-freebsd-current@FreeBSD.ORG Wed May 14 14:34:52 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A85BE37B401 for ; Wed, 14 May 2003 14:34:52 -0700 (PDT) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E48C43F3F for ; Wed, 14 May 2003 14:34:49 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: from khavrinen.lcs.mit.edu (localhost [IPv6:::1]) by khavrinen.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id h4ELYlVo035973 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 14 May 2003 17:34:48 -0400 (EDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.12.9/8.12.9/Submit) id h4ELYkb8035970; Wed, 14 May 2003 17:34:46 -0400 (EDT) (envelope-from wollman) Date: Wed, 14 May 2003 17:34:46 -0400 (EDT) From: Garrett Wollman Message-Id: <200305142134.h4ELYkb8035970@khavrinen.lcs.mit.edu> To: Andrew Kolchoogin In-Reply-To: <20030514200517.GA55732@mowgli.rinet.ru> References: <20030514200517.GA55732@mowgli.rinet.ru> X-Spam-Score: -19.8 () IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,REPLY_WITH_QUOTES X-Scanned-By: MIMEDefang 2.33 (www . roaringpenguin . com / mimedefang) cc: FreeBSD-CURRENT Users cc: acpi-jp@jp.freebsd.org Subject: ACPI hangs the Kernel during boot. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 May 2003 21:34:52 -0000 < said: > BTW, what did I do? ACPI timer, right? But why it doesn't work > on my motherboard? Or all SW-manufactured motherboards are "incompatible" > with Intel ACPI? I don't know. I have an Intel-manufactured motherboard (actually a dozen of them) with ServerWorks chipset and the ACPI timer has always been broken. I've been unable to get anyone interested in investigating this or fixing it, despite the fact that it's an Intel product (SR2100) and Intel's ACPI implementation. -GAWollman