public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jslaby@suse.cz>
To: Jiri Slaby <jslaby@suse.cz>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	Linux PM mailing list <linux-pm@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: -next: no resume from suspend
Date: Wed, 16 Jan 2013 12:02:04 +0100	[thread overview]
Message-ID: <50F688AC.3030609@suse.cz> (raw)
In-Reply-To: <50F68443.3040900@suse.cz>

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

  reply	other threads:[~2013-01-16 11:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <50F3D9E8.6040802@suse.cz>
     [not found] ` <16191961.j5ydKsJ3d3@vostro.rjw.lan>
2013-01-16 10:43   ` -next: no resume from suspend Jiri Slaby
2013-01-16 11:02     ` Jiri Slaby [this message]
2013-01-16 14:00     ` Rafael J. Wysocki
2013-01-16 22:48       ` Jiri Slaby
2013-01-16 23:01         ` Bjorn Helgaas
2013-01-16 23:13           ` Rafael J. Wysocki
2013-01-14 12:53 Sedat Dilek
2013-01-14 13:36 ` Sedat Dilek
2013-01-14 14:06   ` Sedat Dilek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50F688AC.3030609@suse.cz \
    --to=jslaby@suse.cz \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox