From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111271] Black stripe on screen with MGAG200 (PowerEdge R320) and modesetting
Date: Tue, 26 Jan 2016 13:34:47 +0000 [thread overview]
Message-ID: <bug-111271-2300-edZG0qFplX@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-111271-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=111271
Jean-Yves Faye <jean-yves.faye@c-s.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #201421|0 |1
is obsolete| |
--- Comment #6 from Jean-Yves Faye <jean-yves.faye@c-s.fr> ---
Created attachment 202001
--> https://bugzilla.kernel.org/attachment.cgi?id=202001&action=edit
bisect log
After trying to printk around this commit, I noticed some strange behavior,
just adding debug statements making the stripe disappear. I suspected some side
effects in the compilation process.
I've redone the bisect using mrproper instead of make clean between builds,
copying my .config each time. I use make -j20 too.
Bisect results makes much more send now
Author: Christopher Harvey <charvey@matrox.com>
Date: Wed Jun 5 15:24:26 2013 -0400
drm/mgag200: Hardware cursor support
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-01-26 13:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 16:59 [Bug 111271] New: Black stripe on screen with MGAG200 (PowerEdge R320) and modesetting bugzilla-daemon
2016-01-25 17:01 ` [Bug 111271] " bugzilla-daemon
2016-01-25 17:01 ` bugzilla-daemon
2016-01-25 17:02 ` bugzilla-daemon
2016-01-25 17:51 ` bugzilla-daemon
2016-01-25 18:06 ` bugzilla-daemon
2016-01-26 13:34 ` bugzilla-daemon [this message]
2016-01-26 14:42 ` bugzilla-daemon
2024-01-08 10:19 ` bugzilla-daemon
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=bug-111271-2300-edZG0qFplX@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.