All of lore.kernel.org
 help / color / mirror / Atom feed
From: Calvin Walton <calvin.walton@gmail.com>
To: "Carlos R. Mafra" <crmafra@gmail.com>
Cc: linux-kernel@vger.kernel.org, venkatesh.pallipadi@intel.com
Subject: Re: [2.6.25-rc1 regression] Suspend to RAM (bisected)
Date: Mon, 11 Feb 2008 00:47:44 -0500	[thread overview]
Message-ID: <1202708864.5206.0.camel@zem> (raw)
In-Reply-To: <47AFDC4D.4070400@gmail.com>

On Mon, 2008-02-11 at 03:25 -0200, Carlos R. Mafra wrote: 
> Hi,
> 
> I want to report that suspend to RAM stopped working on my Sony Vaio 
> VGN-FZ240E in 2.6.25-rc1 and that I could bisect the problem down
> to:
> 
> commit bc71bec91f9875ef825d12104acf3bf4ca215fa4
> Author: venkatesh.pallipadi@intel.com <venkatesh.pallipadi@intel.com>
> Date:   Thu Jan 31 17:35:04 2008 -0800
> 
>     ACPI: enable MWAIT for C1 idle

I normally hate to throw in a 'me-too', but I'm also seeing a
suspend-to-ram regression on my Thinkpad R61i that I've managed to
bisect down to the same patch series.

You beat me emailing the issue to the list by a few minutes :)

> The problem with suspend to RAM is that right after typing (from inside X)
> 'echo mem > /sys/power/state' the screen becomes black and the laptop 
> freezes. I have to use SysRq+b to reboot.

My symptoms in this case are slightly different - the suspend appears to
work correctly, and is fast. However, when I resume, the screen lights
up quickly, but the system hangs for nearly a minute with the suspend
light still on solid before it actually resumes. No delay is visible in
dmesg; this apparently happens before the "return to C".

> I tried to revert the above commit (bc71bec) on top of 2.6.25-rc1, but
> the compilation fails. It turns out that I have to revert also 9a0b8415 and
> 9b12e18c to be able to compile without errors. 
> 
> After reverting the 3 commits mentioned above, the resulting 2.6.25-rc1 kernel
> can suspend to RAM again (and I must say that it is better that 2.6.24, because
> now it resumes directly into X and I don't need to use Crtl-Alt-F1 and Alt-F7 to
> go back to X as I used to do before).

I just tried reverting the above-mentioned 3 commits, doing so fixes the
delay. 

> The laptop is a Core 2 Duo T7250 2.0 GHz, running Mandriva 2008.0 in 64-bit mode, with the
> following graphics card:
> VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c) (prog-if 00 [VGA])

Rather similar system - I have a core 2 duo 1.5 running x86_64 gentoo,
and a GM965 chip (using uvesafb)

> 
> If there is anything else I can do to help please let me know.
> 
> Carlos R. Mafra

-- 
Calvin Walton <calvin.walton@gmail.com>



  parent reply	other threads:[~2008-02-11  5:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-11  5:25 [2.6.25-rc1 regression] Suspend to RAM (bisected) Carlos R. Mafra
2008-02-11  5:35 ` Arjan van de Ven
2008-02-11  6:08   ` Carlos R. Mafra
2008-02-11  5:47 ` Calvin Walton [this message]
2008-02-11 18:22   ` Pallipadi, Venkatesh
2008-02-11 19:37     ` Carlos R. Mafra
2008-02-11 20:06       ` Venki Pallipadi
2008-02-11 23:20         ` Venki Pallipadi
2008-02-12  0:08           ` Carlos R. Mafra
2008-02-14  5:00           ` Len Brown

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=1202708864.5206.0.camel@zem \
    --to=calvin.walton@gmail.com \
    --cc=crmafra@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=venkatesh.pallipadi@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.