On Wednesday, January 16, 2013 12:55:20 AM Rafael J. Wysocki wrote:
> On Tuesday, January 15, 2013 03:43:17 PM Yinghai Lu wrote:
> > On Tue, Jan 15, 2013 at 3:26 AM, Rafael J. Wysocki <rjw@xxxxxxx> wrote:
> > > On Monday, January 14, 2013 10:55:49 PM Yinghai Lu wrote:
[...]
> >
> >
> > looks like:
> >
> > acpi_device_release+0x30
> > 0xffffffff81536e2f is in acpi_device_release (drivers/acpi/scan.c:524).
> > 519 static void acpi_free_power_resources_lists(struct acpi_device *device)
> > 520 {
> > 521 int i;
> > 522
> > 523 acpi_power_resources_list_free(&device->wakeup.resources);
> > 524 if (!device->flags.power_manageable)
> > 525 return;
> > 526
> > 527 for (i = ACPI_STATE_D0; i <= ACPI_STATE_D3_HOT; i++) {
> > 528 struct acpi_device_power_state *ps = &device->power.states[i];
> >
> > wakeup.resources has problem?
>
> Yes, it seems to.
>
> Thanks for the report, looking into it.
Found a bug, fixed it and updated the tree (device->flags.wakeup.valid should
be checked before the acpi_power_resources_list_free(&device->wakeup.resources),
otherwise the list may not be initialized).
Thanks,
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
