public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Nico -telmich- Schottelius <nico-linux-20090106@schottelius•org>
To: LKML <linux-kernel@vger•kernel.org>, linux-next@vger•kernel.org
Cc: Nico -telmich- Schottelius <nico-linux-20090106@schottelius•org>
Subject: Suspend issues on all latest kernels!
Date: Wed, 7 Jan 2009 20:35:59 +0100	[thread overview]
Message-ID: <20090107193559.GA4306@denkbrett.schottelius.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1069 bytes --]

Hello!

Suspend fails on Lenovo X200 with

  - 2.6.28-next-20090107-ikn
  - 2.6.28-ikn-06859-gede6f5a

When doing echo mem > /sys/power/state, the
"Suspending consoles..." message appears, the "moon" is blinking,
but the system stays in this state (waited 10 minutes) forever.

At least -next is broken for a longer time (see previous posts on
linux-next).

Now the -wl tree also gained a suspend problem:

With

  - 2.6.28-rc9-wl-ikn-24949-ge98df74

I can suspend (!) and even wake up, but the display is black
(xorg and console) with some strange drawn columns.

Tha last known working version is

  - 2.6.28-rc9-wl-denkbrett-24896-gf4f5c96

Can somebody fix that so upgrading and testing
to a newer kernel is possible again?

Sincerly,

Nico

P.S.: -ikn or -denkbrett is just the hostname; kernels are not patched,
      directly fetched via git.


-- 
Think about Free and Open Source Software (FOSS).
http://nico.schottelius.org/documentations/foss/the-term-foss/

PGP: BFE4 C736 ABE5 406F 8F42  F7CF B8BE F92A 9885 188C

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

             reply	other threads:[~2009-01-07 19:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-07 19:35 Nico -telmich- Schottelius [this message]
2009-01-07 20:37 ` Suspend issues on all latest kernels! Jiri Slaby

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=20090107193559.GA4306@denkbrett.schottelius.org \
    --to=nico-linux-20090106@schottelius$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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