From owner-freebsd-current Thu Sep 6 21:49:20 2001 Delivered-To: freebsd-current@freebsd.org Received: from ns.altadena.net (ns.altadena.net [206.126.144.2]) by hub.freebsd.org (Postfix) with ESMTP id B291437B406 for ; Thu, 6 Sep 2001 21:49:17 -0700 (PDT) Received: (from pete@localhost) by ns.altadena.net (8.11.3/8.8.8) id f874mkX21174; Thu, 6 Sep 2001 21:48:46 -0700 (PDT) (envelope-from pete) From: Pete Carah Message-Id: <200109070448.f874mkX21174@ns.altadena.net> Subject: Re: ACPI problems To: tlambert2@mindspring.com Date: Thu, 6 Sep 2001 21:48:45 -0700 (PDT) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=iso8859-1 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 Terry Lambert wrote: >.... > > 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. Actually not; You missed my comment that the DMESG was WITHOUT the ACPI module loaded; my real problem was a panic long before the serial probes. These pnp messages may be entries in hints twice? Apparently the AMD chipset is not served correctly by this ACPI code; I have this panic on one system and clock problems on another (Aladdin chipset; not that I love Acer) the clock runs almost exactly twice speed with the new ACPI; correctly without.) I saw a major acpi update come through this evening so I'm trying again... (that is, if strfmon and amd compile :-) -- Pete To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message