public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lior Dotan <liodot@gmail.com>
To: Andy Isaacson <adi@hexapodia.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.32-rc8 - T500 fails to suspend to RAM
Date: Sat, 05 Dec 2009 12:55:15 +0200	[thread overview]
Message-ID: <4B1A3C13.4060204@gmail.com> (raw)
In-Reply-To: <20091204234459.GC25713@hexapodia.org>

Andy Isaacson wrote:
> Re-adding LKML.
>
> On Fri, Dec 04, 2009 at 11:39:25PM +0200, Lior Dotan wrote:
>   
>> On Fri, Dec 4, 2009 at 10:24 PM, Andy Isaacson <adi@hexapodia.org> wrote:
>>     
>>> For what it's worth, I'm testing suspend-to-ram on Ubuntu 9.10 x86_64
>>> with 2.6.32 final on a T500 and it's been pretty reliable -- I've
>>> suspended by closing the lid at least a dozen times and it hasn't locked
>>> up yet.
>>>       
>> I'm using either KDE menu to suspend or hibernate-ram from hibernate-script.
>> I will try to use the lid and see if it makes any difference.
>> The strange thing is that I tried using rc6 & rc7 and they don't work now
>> even though they used to, so I now I need to see what broke it.
>>     
>
> I mentioned the lid because of BZ #14484 which is only on Intel GMA plus
> using the lid switch to trigger suspend.  Since neither is relevant to
> you it's just a red herring. :)
>
>   
>>> 1. are you using DMAR (VT-d)?  I'm not, and I had problems on another
>>>   machine (also Core 2 Duo with GM45 graphics) when I tried suspending
>>>   with CONFIG_DMAR=y.
>>>       
>>  I disabled DMAR but still no luck.
>>     
>
> It's getting better but DMAR has still been a little problematic for me
> the last few months.  Updating to the very latest BIOS does help
> sometimes.
>
>   
>>> 2. are you running into http://bugzilla.kernel.org/show_bug.cgi?id=14484
>>>   or a similar problem?
>>> 3. (if you have GMA graphics) Are you up to date on the xorg-video-intel
>>>   driver?  I'm using KMS and xorg-video-intel 2.9.0.  2.8.x is missing
>>>   some relevant bugfixes.  (Of course if you have ATI graphics then
>>>   this isn't relevant.)
>>>
>>>       
>> I'm using the Radeon GPU so no KMS for me yet.
>>     
>
> Sounds like your Radeon or fglrx driver got updated and broke
> suspend/resume.
>   
I got some progess, when using the Intel GMA, the suspend works fine. 
The problem are only when using the radeon driver.
I am trying to use KMS for radeon but it fails to load the firmware and 
the system boots without KMS. I will disable KMS and revert the 
xf86-video-ati driver to the latest released version (I am now using the 
git version).

> -andy
>   
Thanks for your help,
Lior.

      reply	other threads:[~2009-12-05 10:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-01 13:53 Linux 2.6.32-rc8 - T500 fails to suspend to RAM Lior Dotan
2009-12-01 21:46 ` Rafael J. Wysocki
2009-12-01 21:58   ` Lior Dotan
2009-12-02 12:40   ` Lior Dotan
2009-12-02 21:39     ` Rafael J. Wysocki
2009-12-03 18:23 ` Andy Isaacson
2009-12-04 20:24   ` Andy Isaacson
     [not found]     ` <a5bf86a80912041339g3d35cbfcrd56669f746d095ff@mail.gmail.com>
2009-12-04 23:44       ` Andy Isaacson
2009-12-05 10:55         ` Lior Dotan [this message]

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=4B1A3C13.4060204@gmail.com \
    --to=liodot@gmail.com \
    --cc=adi@hexapodia.org \
    --cc=linux-kernel@vger.kernel.org \
    /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