From owner-freebsd-acpi@FreeBSD.ORG Tue Feb 7 20:33:48 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B705416A420; Tue, 7 Feb 2006 20:33:48 +0000 (GMT) (envelope-from oberman@es.net) Received: from postal4.es.net (postal4.es.net [198.124.252.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0176C43D5F; Tue, 7 Feb 2006 20:33:44 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal4.es.net (Postal Node 4) with ESMTP (SSL) id IBA74465; Tue, 07 Feb 2006 12:33:41 -0800 Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 7C5F945041; Tue, 7 Feb 2006 12:33:40 -0800 (PST) To: "Donald J. O'Neill" In-reply-to: Your message of "Tue, 07 Feb 2006 14:13:06 CST." <200602071413.07109.duncan.fbsd@gmail.com> Date: Tue, 07 Feb 2006 12:33:40 -0800 From: "Kevin Oberman" Message-Id: <20060207203340.7C5F945041@ptavv.es.net> Cc: freebsd-acpi@freebsd.org Subject: Re: Kernel panic with ACPI enabled X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Feb 2006 20:33:48 -0000 > From: "Donald J. O'Neill" > Date: Tue, 7 Feb 2006 14:13:06 -0600 > Sender: owner-freebsd-acpi@freebsd.org > > On Tuesday 07 February 2006 13:04, John Baldwin wrote: > > On Tuesday 07 February 2006 13:37, Donald J. O'Neill wrote: > > > On Tuesday 07 February 2006 09:48, John Baldwin wrote: > > > > > > > I have a few things. Is there a reason you have 'device apm'? Are > > > you trying to use APM and ACPI at the same time? Why do you have > > > 'device isa' rather than 'device eisa'? Where you, by any chance, > > > just re-using your conf file from 5.x? It kind of looks that way. > > > Have you looked at i386/conf/NOTES? There is some more information > > > in there. > > > > device isa is normal, and he probably just commented out eisa since > > modern systems don't have EISA slots. The apm thing won't hurt, > > though it probably adds a small bit of bloat to the kernel. If you > > have both apm and acpi then acpi will be used if it is present, > > otherwise if acpi is not present (or is disabled) then apm will be > > used. > > Hi John, > > It seems to me that eisa was an extension to isa and that most modern > computers don't have an isa bus but have eisa bus instead, In fact I > have a Gateway Computer (500Mhz PIII) that has an eisa slot on the MB. > Actually most modern computers don't physically have a slot for either > isa or eisa. Quite possibly either one would work. I have 'device eisa' > in my conf, it's also 'device eisa' in the GENERIC conf which is why I > mentioned it. While it is an extension of the ISA system, it is not something that can be used with the same drivers as ISA. They are completely separate devices. And almost all systems have ISA devices, even though they have not ISA slots. For example, the mouse and keyboard are ISA devices. In V&, ISA gets built into the kernel whether you have it in your config file or not because too many people assumed that they didn't need it and built broken kernels. Yes, it is possible (and easy) to build a kernel without the ISA device, but it requires modifying another file that is used by config.) Also, some systems will fail to boot if the EISA driver is in the kernel. Rare, but becoming more common as EISA gets rarer. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634