public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Arkadiusz Miskiewicz <arekm@maven.pl>
Cc: linux-kernel@vger.kernel.org,
	pm list <linux-pm@lists.linux-foundation.org>
Subject: Re: resume from ram hangs on 2.6.26+ kernels on thinkpad z60m
Date: Thu, 21 Aug 2008 14:43:43 +0200	[thread overview]
Message-ID: <200808211443.43690.rjw@sisk.pl> (raw)
In-Reply-To: <200808201602.26848.arekm@maven.pl>

On Wednesday, 20 of August 2008, Arkadiusz Miskiewicz wrote:
> 
> I'm seeing problems with resume (using s2ram) on thinkpad z60m notebook with 
> very fresh git kernel (built yesterday). It looks like this - I get screen 
> resumed with X window running on it, I see mouse pointer but pointer doesn't 
> react to movement and sysrq keys also don't respond (tried to 
> umount+sync+reboot via sysrq).
> 
> The hangs doesn't always happen but it happens quite often (often enough to 
> get kmail trashed several times).
> 
> The problem is also happening on 2.6.26 kernels (I wasn't testing .26 too 
> much).
> 
> Now I'm back on 2.6.25 where the problem doesn't occur.
> 
> I didn't see any reports related  to that on lkml which is bad thing 8)
> 
> Any ideas?

Not really.  We must have broken something in 2.6.26, but there were not too
many suspend-specific patches in there vs .25.

What s2ram options are used?

What hardware is there in the box (chipset, graphics)?

Thanks,
Rafael

  reply	other threads:[~2008-08-21 12:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-20 14:02 resume from ram hangs on 2.6.26+ kernels on thinkpad z60m Arkadiusz Miskiewicz
2008-08-21 12:43 ` Rafael J. Wysocki [this message]
2008-08-24 14:31   ` Arkadiusz Miskiewicz
2008-08-28 18:45     ` Arkadiusz Miskiewicz
2008-08-28 19:22       ` Rafael J. Wysocki

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=200808211443.43690.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=arekm@maven.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.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