From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Ben Gamari <bgamari.foss@gmail.com>
Subject: Re: [REGRESSION 2.6.34] Suspend fails in pm_test=processor on Dell laptop
Date: Wed, 21 Apr 2010 06:51:19 +0200
User-Agent: KMail/1.12.4 (Linux/2.6.34-rc4-rjw; KDE/4.3.5; x86_64; ; )
Cc: linux-kernel@vger.kernel.org,
       pm list <linux-pm@lists.linux-foundation.org>
References: <4bcb1cf2.116bdc0a.2008.6f5a@mx.google.com> <201004200533.13219.rjw@sisk.pl>
In-Reply-To: <201004200533.13219.rjw@sisk.pl>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-2"
Content-Transfer-Encoding: 7bit
Message-Id: <201004210651.20056.rjw@sisk.pl>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1143
Lines: 32

On Tuesday 20 April 2010, Rafael J. Wysocki wrote:
> On Sunday 18 April 2010, Ben Gamari wrote:
> > Hey all,
> > 
> > It seems that something in the 2.6.34 merge cycle has broken suspend to RAM on
> > my Dell Latitude D830. While suspend has been rock solid for several release
> > cycles, as of 2.6.34-rc4 it locks up on suspend. All of the pm_test options up
> > to processor work fine, precluding a driver issue.
> 
> Hmm, does the "processors" work?

Sorry, the subject says it doesn't.

> > Unfortunately, I've been unable to get any useful output from the serial
> > console during suspend. I'll try bisecting and report back when I have more
> > details. Let me know what else I can do to help.
> 
> I can't reproduce this, so it looks hardware or BIOS-related.  Or it's an
> obscure x86 bug.

Does switching CPU1 on/off by echoing 0/1 to

/sys/devices/system/cpu/cpu1/online

work?

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