From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Nico Schottelius <nico-linux-20100709@schottelius.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.35-rc4 / X201 issues
Date: Fri, 9 Jul 2010 10:29:35 -0700 [thread overview]
Message-ID: <20100709102935.60648095@virtuousgeek.org> (raw)
In-Reply-To: <20100709170432.GA7691@schottelius.org>
On Fri, 9 Jul 2010 19:04:32 +0200
Nico Schottelius <nico-linux-20100709@schottelius.org> wrote:
> Good evening hackers,
>
> latest report from 2.6.35-rc4 on X201:
>
> - (almost) everytime I close and reopen the lid, the image is screwed up
> - switching to vt1 (away from xorg) and back to vt7 fixes that almost always
> - did not happen on 2.6.34 (iirc)
Can you bisect this issue?
> - if it's not screwed up, the system is frozen
> - does not react on ping, last image is displayed, no keyboard shortcut works
> - ATTENTION: it's *NOT* needed to suspend directly before to get a freeze!
> - simplying closing & opening the lid is enough
Presumably this used to work too, so a bisect might help here as well.
FWIW mine doesn't behave this way; I have an x201s and it works pretty
well with current bits (note that a bunch of 2D, Mesa and libdrm fixes
have landed recently as well).
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2010-07-09 17:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-09 17:04 Nico Schottelius
2010-07-09 17:29 ` Jesse Barnes [this message]
2010-09-06 7:17 ` 2.6.36-rc3 suspend issue (was: 2.6.35-rc4 / X201 issues) Nico Schottelius
2010-09-06 8:49 ` Nico Schottelius
2010-09-06 13:50 ` Jeff Chua
2010-09-06 18:37 ` Rafael J. Wysocki
2010-09-07 3:42 ` Jeff Chua
2010-09-07 21:48 ` Rafael J. Wysocki
2010-09-07 22:50 ` Nico Schottelius
2010-09-07 23:28 ` Rafael J. Wysocki
2010-09-08 6:21 ` Nico Schottelius
2010-09-08 22:27 ` Rafael J. Wysocki
2010-09-10 8:26 ` 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=20100709102935.60648095@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nico-linux-20100709@schottelius.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
all inboxes | Powered by JetHome®