From owner-freebsd-current Tue Sep 4 0:26:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.121.85]) by hub.freebsd.org (Postfix) with ESMTP id 0166E37B403 for ; Tue, 4 Sep 2001 00:26:42 -0700 (PDT) Received: from mindspring.com (dialup-209.247.140.38.Dial1.SanJose1.Level3.net [209.247.140.38]) by gull.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id AAA08978; Tue, 4 Sep 2001 00:26:29 -0700 (PDT) Message-ID: <3B948251.D48A74DF@mindspring.com> Date: Tue, 04 Sep 2001 00:27:14 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Pete Carah Cc: current@freebsd.org Subject: Re: ACPI problems References: <200109022001.f82K1vo07551@ns.altadena.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 Pete Carah wrote: > > I have a panic that I haven't seen in the notes so far; if I allow load > of the acpi module, it gets a "can't allocate memory" very early in the > boot process. > > Hopefully the following is complete - KDE2 cut-and-paste didn't work > as I expected for a big region. [ ... ] > unknown: can't assign resources > unknown: at port 0x378-0x37f on isa0 > unknown: can't assign resources > unknown: at port 0x3f8-0x3ff on isa0 > unknown: can't assign resources > unknown: at port 0x2f8-0x2ff on isa0 > unknown: can't assign resources > unknown: at irq 12 on isa0 > unknown: can't assign resources > unknown: at port 0x60 on isa0 > unknown: failed to probe at port 0x61 on isa0 Known problem... see the -current archives. You are attaching twice: once because of ACPI, and again because of the "hints". You need to comment the entries out of your hints file to make them not get attached twice. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message