From: Andrew Morton <akpm@linux-foundation.org>
To: Nico Schottelius <nico-linux-2010-07-01@schottelius.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
netdev@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org,
Maciej Rutecki <maciej.rutecki@gmail.com>
Subject: Re: Report for 2.6.35-rc3-00262-g984bc96
Date: Tue, 6 Jul 2010 19:42:22 -0700 [thread overview]
Message-ID: <20100706194222.fcf16e13.akpm@linux-foundation.org> (raw)
In-Reply-To: <20100701074052.GA3501@schottelius.org>
On Thu, 1 Jul 2010 09:40:52 +0200 Nico Schottelius <nico-linux-2010-07-01@schottelius.org> wrote:
> Good morning!
>
> A short report on what's broken in 2.6.35-rc3-00262-g984bc96 with
> the Lenovo X201:
So you see two post-2.6.34 regressions?
> == xrandr ==
>
> After using xrandr several times in xorg, the screen gets
> "fancy": blue/white/black changing patterns.
> Getting even more weired when changing to a conosle.
>
> The only thing that keeps on working is the mouse cursor
> in xorg. This did not happen with 2.6.34-rcsomething, neither
> with 2.6.33 iirc.
>
> This is a Intel Corporation Core Processor Integrated Graphics Controller (rev 02),
> attached xorg.log.
(cc dri-devel)
> == netlink/carrier messag ==
>
> dhcpcd does not get updated when the link is established,
> need to restart it.
(cc netdev)
> == suspend/resume (to ram) ==
>
> So far no real crash! Only xorg is sometimes not coming up
> again, but this may be related to the first issue.
>
> == wifi / intel 6000 ==
>
> Works! Works! (Besides the netlink issue, which is annoying,
> but for all devices).
next parent reply other threads:[~2010-07-07 2:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100701074052.GA3501@schottelius.org>
2010-07-07 2:42 ` Andrew Morton [this message]
2010-07-07 6:25 ` Report for 2.6.35-rc3-00262-g984bc96 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=20100706194222.fcf16e13.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.rutecki@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nico-linux-2010-07-01@schottelius.org \
--cc=rjw@sisk.pl \
/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;
as well as URLs for NNTP newsgroup(s).