From: Maxim Levitsky <maximlevitsky@gmail.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Anca Emanuel <anca.emanuel@gmail.com>,
Ubuntu kernel team mailing list <kernel-team@lists.ubuntu.com>,
LKML <linux-kernel@vger.kernel.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: is there a fix for ubuntu with intel GPU booting to blank screen?
Date: Fri, 31 Dec 2010 23:46:54 +0200 [thread overview]
Message-ID: <1293832014.27359.7.camel@maxim-laptop> (raw)
In-Reply-To: <alpine.DEB.2.00.1012311153190.3495@localhost6.localdomain6>
On Fri, 2010-12-31 at 12:01 -0500, Robert P. J. Day wrote:
> On Fri, 31 Dec 2010, Maxim Levitsky wrote:
>
> ... snip related to i915 blank screen issues ...
>
> > Since you know how to compile kernel, and even have a close working
> > version, you really should just bisect the bug.
> >
> > Bisection is a built-in in the git binary search that allows you to
> > find the first commit that introduced the bug.
> >
> > For example, quick google gives,
> > http://www.kernel.org/pub/software/scm/git-core/docs/v1.0.13/howto/isolate-bugs-with-bisect.txt
>
> oh, i know how to do bisection but, to be frank, i just don't have
> the time. i'm under a brutal deadline for some billable work and,
> even if i had the time, i suspect that when i eventually tracked down
> the commit, i probably wouldn't really appreciate what i was looking
> at, anyway.
You truly underestimate this.
Having commit that broke things points perfectly at the issue.
Then, developers can even just revert the offending commit until it is
understood why it breaks stuff.
I have done many bisections in the past, and lot of bugs were fixed that
way.
I personally can't help you with the issue, because I am nether familiar
with the hardware nor with the driver, but I just say what I do when I
get a regression (and this not uncommon).
Best regards,
Maxim Levitsky
>
> i've done some searching on the issue and, among other pages, i've
> come up with this one:
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/683775
>
> so i downloaded the kernel mentioned there and tested that, but no
> luck. mostly, i understand that there top men -- *top* *men* --
> working on this :-) who know far more about the graphics subsystem
> than i do so i'm just going to stay out of their way, but i'm willing
> to test any proposed solutions if they come up. my biggest worry is
> that, given that we're already at -rc8, will this issue be fixed
> before the next official release?
>
> rday
>
next prev parent reply other threads:[~2010-12-31 21:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.00.1012270640240.3071@localhost6.localdomain6>
2010-12-31 6:32 ` is there a fix for ubuntu with intel GPU booting to blank screen? Anca Emanuel
2010-12-31 14:23 ` Robert P. J. Day
2010-12-31 16:48 ` Maxim Levitsky
2010-12-31 17:01 ` Robert P. J. Day
2010-12-31 21:46 ` Maxim Levitsky [this message]
2011-01-01 11:18 ` Robert P. J. Day
2011-01-02 12:13 ` Robert P. J. Day
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=1293832014.27359.7.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=anca.emanuel@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kernel-team@lists.ubuntu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
/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