Re: About acpi0: reservation of ... failed message in `dmesg`
Hi Nate and John, Thanks for your clarification. From now on, we and our customers will use `devinfo -ur` to verify these resource allocations. Best Regards, Fred ___ freebsd-acpi@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-acpi To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org
Re: About acpi0: reservation of ... failed message in `dmesg`
Nate Lawson wrote: avatar Lin wrote: Our customers are concerned about the following messages in `dmesg` output. === acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, bff0 (3) failed === Please help to clarify this issue. Or , in other direction, where to find official document to convince our customers that these messages are ignorable ? It is related to the sysresource acpi memory objects. It means that something was using the system resource before acpi allocated it. For #1, that looks like lowmem up to the VGA range. For #2, it looks like option ROMs. The BIOS has configured the devices beforehand so as long as everything works, the msgs can be ignored. Actually, to handle non-ACPI systems and ACPI systems that do not list system memory in the system resource objects, I added a 'ram0' device which uses the SMAP table and allocates address space for all of memory to perform a similar function to ACPI system resource objects. Often this message triggers now because the ram0 device has claimed the resources before ACPI gets a chance. You can certainly ignore these messages. If you look in 'devinfo -ur' you will probably find that these resource ranges are allocated by the ram0 device. -- John Baldwin ___ freebsd-acpi@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-acpi To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org
Re: About acpi0: reservation of ... failed message in `dmesg`
On 05/11/10 13:46, John Baldwin: Our customers are concerned about the following messages in `dmesg` output. === acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, bff0 (3) failed See http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/119356 These messages do not have anything to do with allocating the memory used for wakeup from suspend Such messages are related to problem with ACPI's memory allocation. Mentioned bug report is related to ACPI's memory allocation problem. As I fail to make complete analysis of current problem, I can't decide if both problems have common base or not. I assumed my notice may help to someone else more skilled not to overlook something already known. I'm not sure how they are related to the bug you are reporting Nor me. My see here doesn't mean here is explanation and fix but here may be informations that may (or may not) be related to your problem. Nothing more, nothing less. It seems to be language problem. English is not my native language. I will try to be more explicit in the future. Dan ___ freebsd-acpi@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-acpi To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org
