New prototype computer problem with S3 suspend

New prototype computer problem with S3 suspend

[Boszormenyi Zoltan]

[-- Attachment #1: Type: text/plain, Size: 1816 bytes --]

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.

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.

The reason for cross-posting to dri-devel is the warnings that complain
about the video chip, like:

[drm:intel_enable_lvds] *ERROR* timed out waiting for panel to power on

on boot and 4 further warnings appearing after the machine was resumed:

WARNING: at drivers/gpu/drm/i915/intel_display.c:3927 intel_modeset_check_state+0xbd/0x539()
active connector not linked to encoder

WARNING: at drivers/gpu/drm/i915/intel_display.c:3933 intel_modeset_check_state+0x119/0x539()

WARNING: at drivers/gpu/drm/i915/intel_display.c:7873 intel_modeset_check_state+0x4d3/0x539()
encoder's active_connectors set, but no crtc

WARNING: at drivers/gpu/drm/i915/intel_display.c:7892 intel_modeset_check_state+0x2c8/0x539()
encoder's computed active state doesn't match tracked active state (expected 0, found 1)

FYI. the machine does have LVDS and a touchscreen as well.

I have tried disabling wakeup devices via /proc/acpi/wakeup and via sysfs files.
(/sys/devices/.../wakeup)

We have cross-checked suspend-resume using Windows XP and Windows 7
and these OSs are able to properly suspend the machine 50 times out of
50 attempts with Intel's official driver for the GMA3150.

How can I make S3 suspend work reliably? Is there a missing piece from our kernel .config?

Best regards,
Zoltán Böszörményi


[-- Attachment #2: config-3.10-003.gz --]
[-- Type: application/x-tar, Size: 18727 bytes --]

[-- Attachment #3: dmesg-sl20.txt.gz --]
[-- Type: application/x-tar, Size: 11570 bytes --]

[-- Attachment #4: lspci-names.txt.gz --]
[-- Type: application/x-tar, Size: 6484 bytes --]

[-- Attachment #5: lspci-numeric.txt.gz --]
[-- Type: application/x-tar, Size: 6106 bytes --]

Re: New prototype computer problem with S3 suspend

[Aaron Lu]

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

Re: New prototype computer problem with S3 suspend

[Boszormenyi Zoltan]

2013-06-07 03:17 keltezéssel, Aaron Lu írta:
> 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.

For the suspend bug:
https://bugzilla.kernel.org/show_bug.cgi?id=59401

For the warnings in i915:
https://bugs.freedesktop.org/show_bug.cgi?id=65497

Best regards,
Zoltán Böszörményi

--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html