public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: ykzhao <yakui.zhao@intel.com>
To: wferi <wferi@niif.hu>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: Suspend to RAM freeze with kernel modesetting
Date: Fri, 09 Oct 2009 09:34:02 +0800	[thread overview]
Message-ID: <1255052042.3601.2.camel@localhost.localdomain> (raw)
In-Reply-To: <7ff4351d91a63843e586e595d0c5a5d5@niif.hu>

On Thu, 2009-10-08 at 09:40 +0800, wferi wrote:
> Hi ACPI folks,
> 
> I'd like to solicit your opinion on the
> https://bugs.freedesktop.org/show_bug.cgi?id=22126 issue.
> In short, if I load the Intel graphics driver with kernel
> modesetting enabled, my ThinkPad R50e won't suspend to RAM
> anymore, it freezes instead (ie. does not enter S3).
> Tracing seems to show that the freeze happens in a
> particular line of drivers/acpi/acpica/hwsleep.c:
> /* Run the _PTS method */
> status = acpi_evaluate_object(NULL, METHOD_NAME__PTS, &arg_list, NULL);
> 
> in acpi_enter_sleep_state_prep, as described in the bug
> report. Can anybody provide a clue why this happens?
> Suspend to disk works invariably, just like suspend to RAM
> until I enable the kernel modesetting by a module option.
Will you please attach the output of acpidump on your box?
Thanks.
> 
> Please Cc me or the bug report, I'm not subscribed to linux-acpi.
> 
> Thanks,
> Feri.
> --
> 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


  reply	other threads:[~2009-10-09  1:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-08  1:40 Suspend to RAM freeze with kernel modesetting wferi
2009-10-09  1:34 ` ykzhao [this message]
2009-10-09 21:20   ` Wagner Ferenc

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=1255052042.3601.2.camel@localhost.localdomain \
    --to=yakui.zhao@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=wferi@niif.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