public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Boszormenyi Zoltan <zboszor@pr.hu>
To: dri-devel@lists.freedesktop.org,
	lkml <linux-kernel@vger.kernel.org>,
	linux-acpi@vger.kernel.org
Cc: Steve Tilden <stilden@sicom.com>
Subject: New prototype computer problem with S3 suspend
Date: Thu, 06 Jun 2013 20:11:42 +0200	[thread overview]
Message-ID: <51B0D0DE.30902@pr.hu> (raw)

[-- 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 --]

             reply	other threads:[~2013-06-06 18:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-06 18:11 Boszormenyi Zoltan [this message]
2013-06-07  1:17 ` New prototype computer problem with S3 suspend Aaron Lu
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=51B0D0DE.30902@pr.hu \
    --to=zboszor@pr.hu \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stilden@sicom.com \
    /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