From: Melchior FRANZ <melchior.franz@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Chris Wilson <chris@chris-wilson.co.uk>,
dri-devel@lists.freedesktop.org,
Keith Packard <keithp@keithp.com>
Subject: [3.0-rc1 regression] (was: Re: [2.6.39 regression] i915/kms: garbled screen because of 49183b281)
Date: Mon, 30 May 2011 14:10:10 +0200 [thread overview]
Message-ID: <201105301410.11270@rk-nord.at> (raw)
In-Reply-To: <201105121849.09225@rk-nord.at>
* Melchior FRANZ -- Thursday 12 May 2011:
> > Chris Wilson (4):
> > drm/i915: Only enable the plane after setting the fb base (pre-ILK)
>
> This patch introduces a bug on my infamous "Acer Travelmate
> 5735Z-452G32Mnss": when KMS takes over, the frame buffer contents
> get completely garbled up on screen, with colored stripes and
> unreadable text (photo on request). Only when X11 is started, the
> screen gets restored again. Closing and re-opening the lid partly
> cures the mess, too: it makes the font readable, though horizontally
> stretched.
>
> Reverting 49183b2818de6899383bb82bc032f9344d6791ff fixes the
> bug.
This got fixed after my bug report, but now it's back with exactly
the same description. Bisection result to come ...
m.
next prev parent reply other threads:[~2011-05-30 12:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 2:49 Linux 2.6.39-rc7 Linus Torvalds
2011-05-10 3:53 ` Konrad Rzeszutek Wilk
2011-05-10 23:36 ` Konrad Rzeszutek Wilk
2011-05-10 23:42 ` H. Peter Anvin
2011-05-12 16:49 ` [2.6.39 regression] i915/kms: garbled screen because of 49183b281 (was: Re: Linux 2.6.39-rc7) Melchior FRANZ
2011-05-12 18:52 ` [PATCH] Revert "drm/i915: Only enable the plane after setting the fb base (pre-ILK)" Keith Packard
2011-05-12 21:41 ` [2.6.39 regression] i915/kms: garbled screen because of 49183b281 (was: Re: Linux 2.6.39-rc7) Chris Wilson
2011-05-13 11:59 ` Melchior FRANZ
2011-05-30 12:10 ` Melchior FRANZ [this message]
2011-05-15 13:50 ` Linux 2.6.39-rc7 Borislav Petkov
2011-05-15 13:53 ` Tejun Heo
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=201105301410.11270@rk-nord.at \
--to=melchior.franz@gmail.com \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=keithp@keithp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@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
all inboxes | Powered by JetHome®