public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nico Schottelius <nico-linux-20101018@schottelius.org>
To: linux-kernel@vger.kernel.org
Cc: Nico Schottelius <nico-linux-20101018@schottelius.org>
Subject: Display freezes: 2.6.36-rc6-00137-g7c6d45e and 2.6.36-rc7-00124-g85a3318
Date: Mon, 18 Oct 2010 10:33:07 +0200	[thread overview]
Message-ID: <20101018083307.GA4744@schottelius.org> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 711 bytes --]

Good morning kernel hackers,

as reported before, the system does not freeze completly anymore
and even reports errors after the nth time resumed (about 10 cycles
needed). Currently the display gets redrawn VERY slow, if at all.
Restarting xorg does not help, rebooting the system does.

The problem though continues to exist on latest kernels,
tested here are 2.6.36-rc6-00137-g7c6d45e and 2.6.36-rc7-00124-g85a3318.

This happens on the X200 and X201 (both tested).

Attached are both dmesg and xorg log from last two cases.

If there are any known workarounds, please let me know (besides not suspending).

Cheers,

Nico

-- 
PGP key: 7ED9 F7D3 6B10 81D7 0EC5  5C09 D7DC C8E4 3187 7DF0

[-- Attachment #1.2: 2.6.36-rc6-00137-g7c6d45e.dmesg.gz --]
[-- Type: application/octet-stream, Size: 35851 bytes --]

[-- Attachment #1.3: 2.6.36-rc6-00137-g7c6d45e.xorg.gz --]
[-- Type: application/octet-stream, Size: 13026 bytes --]

[-- Attachment #1.4: 2.6.36-rc7-00124-g85a3318.dmesg.gz --]
[-- Type: application/octet-stream, Size: 29610 bytes --]

[-- Attachment #1.5: 2.6.36-rc7-00124-g85a3318.xorg.gz --]
[-- Type: application/octet-stream, Size: 8372 bytes --]

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

             reply	other threads:[~2010-10-18 12:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-18  8:33 Nico Schottelius [this message]
2010-10-19  7:37 ` Display freezes: 2.6.36-rc6-00137-g7c6d45e and 2.6.36-rc7-00124-g85a3318 Nico Schottelius

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=20101018083307.GA4744@schottelius.org \
    --to=nico-linux-20101018@schottelius.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