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: <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.
-- Terry
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
