linux-kernel - Re: is there a fix for ubuntu with intel GPU booting to blank screen?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1293832014.27359.7.camel@maxim-laptop>
Date:	Fri, 31 Dec 2010 23:46:54 +0200
From:	Maxim Levitsky <maximlevitsky@...il.com>
To:	"Robert P. J. Day" <rpjday@...shcourse.ca>
Cc:	Anca Emanuel <anca.emanuel@...il.com>,
	Ubuntu kernel team mailing list 
	<kernel-team@...ts.ubuntu.com>,
	LKML <linux-kernel@...r.kernel.org>,
	"intel-gfx@...ts.freedesktop.org" <intel-gfx@...ts.freedesktop.org>
Subject: Re: is there a fix for ubuntu with intel GPU booting to blank
 screen?

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
> 


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/