lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Fri, 4 Dec 2009 12:24:33 -0800
From:	Andy Isaacson <adi@...apodia.org>
To:	Lior Dotan <liodot@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Linux 2.6.32-rc8 - T500 fails to suspend to RAM

On Thu, Dec 03, 2009 at 10:23:36AM -0800, Andy Isaacson wrote:
> On Tue, Dec 01, 2009 at 03:53:38PM +0200, Lior Dotan wrote:
> > Ever since I've upgraded to rc8, my T500 fails to suspend to RAM for the
> > second time. Suspending for the first time works ok but when I resume and
> > later try to suspend again the screen gets blank and the moon LED blinks
> > forever. rc6 & rc7 as well as 2.6.31 worked great with out a problem.
> 
> How are you suspending -- pm-suspend, gnome power manager, closing the
> lid, ... ?

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.

Things to check:

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.
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.)

-andy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ