Port-xen archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]


On Tue, Apr 20, 2010 at 01:05:02PM +0300, Jukka Marin wrote:
> A question: Can a RAM failure (parity error) cause an ACPI exception?  If not,
> what are the common reasons for such exceptions?

As I noted already, this is malloc(9) returning ENOMEM and ACPI complaining
about it (ENOMEM -> AE_NO_MEMORY). The path where this occurs in ACPI is
related to interrupts, so it is pretty serious as far as ACPI is concerned.

I think your earlier assessment about some extraordinary situation is more
probable than a straightforward leak. You could try observing the interrupt
counts (particularly the "SCI interrupt", typically on pin 9) or adding a
simple debug-printf to AcpiOsExecute() (in sys/dev/acpi/acpica/OsdSchedule.c)
to see if there is a constant flood of ACPI events.

A dmesg would also help to verify that this is purely a runtime issue and
not something that can be tracked to the initialization of ACPI early in the

But bear in mind that it could be that only ACPI is the one complaining
loudly enough for you to notice...

- Jukka.

Home | Main Index | Thread Index | Old Index