Date: Thu, 6 Sep 2001 21:48:45 -0700 (PDT) From: Pete Carah <pete@ns.altadena.net> To: tlambert2@mindspring.com Cc: current@freebsd.org Subject: Re: ACPI problems Message-ID: <200109070448.f874mkX21174@ns.altadena.net>
next in thread | raw e-mail | index | archive | help
Terry Lambert wrote: >.... > > unknown: <PNP0400> can't assign resources > > unknown: <PNP0400> at port 0x378-0x37f on isa0 > > unknown: <PNP0501> can't assign resources > > unknown: <PNP0501> at port 0x3f8-0x3ff on isa0 > > unknown: <PNP0501> can't assign resources > > unknown: <PNP0501> at port 0x2f8-0x2ff on isa0 > > unknown: <PNP0f13> can't assign resources > > unknown: <PNP0f13> at irq 12 on isa0 > > unknown: <PNP0303> can't assign resources > > unknown: <PNP0303> at port 0x60 on isa0 > > unknown: <PNP0800> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200109070448.f874mkX21174>