From: Aaron Lu <aaron.lwe@gmail.com>
To: Boszormenyi Zoltan <zboszor@pr.hu>
Cc: dri-devel@lists.freedesktop.org,
lkml <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org, Steve Tilden <stilden@sicom.com>
Subject: Re: New prototype computer problem with S3 suspend
Date: Fri, 07 Jun 2013 09:17:26 +0800 [thread overview]
Message-ID: <51B134A6.1020808@gmail.com> (raw)
In-Reply-To: <51B0D0DE.30902@pr.hu>
On 06/07/2013 02:11 AM, Boszormenyi Zoltan wrote:
> Hi,
>
> we are working on an Intel Atom-based embedded PC and I have to
> make suspend-to-RAM work but I can't seem to succeed.
>
> The symptom is that quite often, the machine resumes immediately
> after pm-suspend. Sometimes more than 20 times out of 50 attempts.
Can you please file a bug about this?
https://bugzilla.kernel.org
>
> I have tried 3.7.10, 3.9.4, 3.10-rc[234] and the linux-next branch from the
> git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git repository.
> The attached dmesg is from today's linux-pm/linux-next plus the
> latest drm-fixes patchset posted by Dave Airlie.
>
> I have tried disabling wakeup devices via /proc/acpi/wakeup and via sysfs files.
> (/sys/devices/.../wakeup)
>From the dmesg, the following three devices are still armed with wakeup
capability and might be the cause:
i8042 kbd 00:03: System wakeup enabled by ACPI
PM: suspend of devices complete after 578.883 msecs
PM: late suspend of devices complete after 0.279 msecs
pcieport 0000:00:1c.1: System wakeup enabled by ACPI
ehci-pci 0000:00:1d.7: System wakeup enabled by ACPI
PM: noirq suspend of devices complete after 31.946 msecs
Anyway, please file a bug there, thanks.
-Aaron
next prev parent reply other threads:[~2013-06-07 1:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 18:11 New prototype computer problem with S3 suspend Boszormenyi Zoltan
2013-06-07 1:17 ` Aaron Lu [this message]
2013-06-07 8:14 ` Boszormenyi Zoltan
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=51B134A6.1020808@gmail.com \
--to=aaron.lwe@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stilden@sicom.com \
--cc=zboszor@pr.hu \
/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