From: Jani Nikula <jani.nikula@linux.intel.com>
To: Knut Petersen <Knut_Petersen@t-online.de>,
intel-gfx <intel-gfx@lists.freedesktop.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Intel-gfx] [Bug 3.15-rc2] intel framebuffer broken
Date: Tue, 22 Apr 2014 14:54:03 +0300 [thread overview]
Message-ID: <87tx9lh95w.fsf@intel.com> (raw)
In-Reply-To: <53554B59.8080107@t-online.de>
On Mon, 21 Apr 2014, Knut Petersen <Knut_Petersen@t-online.de> wrote:
> Booting kernel 3.15-rc2 on an AOpen i915GMm-hfs, I see the framebuffer broken.
> Only about the upper left quarter of the monitor is used for displaying the boot messages,
> these (and the cursor) are replicated at the right of that area.
Is this before or after i915.ko is loaded?
> Approximately the lower half of the monitor stays black. The output of the xserver
> is not affected.
Most likely the fastest way to root cause is to bisect, please do. To
keep track of all the bugs we have, please file a bug on DRM/Intel at
[1] and while at it attach dmesg with drm.debug=0xe from the boot.
BR,
Jani.
[1] https://bugs.freedesktop.org/enter_bug.cgi?product=DRI
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-04-22 11:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-21 16:46 [Bug 3.15-rc2] intel framebuffer broken Knut Petersen
2014-04-22 11:54 ` Jani Nikula [this message]
2014-04-22 13:59 ` [Intel-gfx] [Bug 3.15-rc2] [bisected] " Knut Petersen
2014-04-22 15:10 ` Jani Nikula
2014-04-22 16:20 ` Knut Petersen
2014-04-22 21:05 ` [PATCH] drm/i915: Discard BIOS framebuffers too small to accommodate chosen mode Chris Wilson
2014-04-23 7:11 ` Daniel Vetter
2014-04-23 7:39 ` Chris Wilson
2014-04-23 7:54 ` Chris Wilson
2014-04-23 8:24 ` [Intel-gfx] " Ville Syrjälä
2014-04-23 11:03 ` Jani Nikula
2014-04-23 7:50 ` Ville Syrjälä
2014-04-22 16:22 ` [Intel-gfx] [Bug 3.15-rc2] [bisected] intel framebuffer broken Imre Deak
2014-04-22 17:33 ` Daniel Vetter
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=87tx9lh95w.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=Knut_Petersen@t-online.de \
--cc=intel-gfx@lists.freedesktop.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