lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51B134A6.1020808@gmail.com>
Date:	Fri, 07 Jun 2013 09:17:26 +0800
From:	Aaron Lu <aaron.lwe@...il.com>
To:	Boszormenyi Zoltan <zboszor@...hu>
CC:	dri-devel@...ts.freedesktop.org,
	lkml <linux-kernel@...r.kernel.org>, linux-acpi@...r.kernel.org,
	Steve Tilden <stilden@...om.com>
Subject: Re: New prototype computer problem with S3 suspend

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ