From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: Anca Emanuel <anca.emanuel@gmail.com>,
Ubuntu kernel team mailing list <kernel-team@lists.ubuntu.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: is there a fix for ubuntu with intel GPU booting to blank screen?
Date: Sat, 1 Jan 2011 06:18:02 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.00.1101010613320.5796@localhost6.localdomain6> (raw)
In-Reply-To: <1293832014.27359.7.camel@maxim-laptop>
On Fri, 31 Dec 2010, Maxim Levitsky wrote:
> 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.
one of the difficulties (if i'm reading this correctly) is that the
issue isn't even reliably reproducible. a number of people who have
reported this claim that *sometimes* the system boots properly but
it's hit and miss, so it's not even clear you can bisect
deterministically.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2011-01-01 11:18 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 ` 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
2011-01-01 11:18 ` Robert P. J. Day [this message]
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=alpine.DEB.2.00.1101010613320.5796@localhost6.localdomain6 \
--to=rpjday@crashcourse.ca \
--cc=anca.emanuel@gmail.com \
--cc=kernel-team@lists.ubuntu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maximlevitsky@gmail.com \
/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®