Re: -next: no resume from suspend

From: Jiri Slaby
Date: Wed Jan 16 2013 - 06:01:56 EST


On 01/16/2013 11:43 AM, Jiri Slaby wrote:
> On 01/14/2013 01:56 PM, Rafael J. Wysocki wrote:
>> On Monday, January 14, 2013 11:11:52 AM Jiri Slaby wrote:
>>> Hi,
>>>
>>> since friday's -next (the last known to be working is the last monday's)
>>> I cannot resume from suspend. The last thing I see with
>>> no_console_suspend is:
>>> i915: No ACPI video bus found
>>>
>>> But I used to see the message always, so this is no difference. Any idea
>>> before I start bisecting?
>>
>> Well, what's the next message you normally see with no_console_suspend?
>
> As I wrote in the other message, the kernel is spinning in
> acpi_rs_get_aml_length. There are weird resources in the list. For
> serial 00:05 there is resource with type and length equal to 0 and for
> parport_pc 00:06 there is resource type 58196295 with length of
> 134284152. See:
> acpi_rs_get_aml_length: ffff8801b9f7b380 type=3 len=16
> acpi_rs_get_aml_length: ffff8801b9f7b390 type=0 len=0
> acpi_rs_get_aml_length: BAD ffff8801b9f7b390 type=0 len=0
> serial 00:05: activation failed
> dpm_run_callback(): pnp_bus_resume+0x0/0x80 returns -5
> PM: Device 00:05 failed to resume: error -5
> acpi_rs_get_aml_length: ffff8801b9f7b680 type=3 len=24
> acpi_rs_get_aml_length: ffff8801b9f7b698 type=58196295 len=134284152
> parport_pc 00:06: activation failed
> dpm_run_callback(): pnp_bus_resume+0x0/0x80 returns -5
> PM: Device 00:06 failed to resume: error -5
>
> if (!length)
> return error;
>
> makes it resume again with the errors above...
>
> This was 3.8.0-rc3-next-20130114. Going to test 20130116 as there are
> these patches:

It did not help...

> thanks,
--
js
suse labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/