linux-kernel - Re: [Intel-gfx] [PATCH] drm/i915: Disable all outputs early, before KMS takeover

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]

Date:	Tue, 5 Apr 2011 13:37:17 +0300
From:	Pekka Enberg <penberg@...nel.org>
To:	Chris Wilson <chris@...is-wilson.co.uk>
Cc:	Tomas Winkler <tomasw@...il.com>, intel-gfx@...ts.freedesktop.org,
	linux-kernel@...r.kernel.org, Daniel Vetter <daniel@...ll.ch>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Disable all outputs early, before
 KMS takeover

Hi Chris!

On Tue, Apr 5, 2011 at 1:30 PM, Chris Wilson <chris@...is-wilson.co.uk> wrote:
> On Tue, 5 Apr 2011 13:21:08 +0300, Tomas Winkler <tomasw@...il.com> wrote:
>> On Fri, Apr 1, 2011 at 2:51 PM, Pekka Enberg <penberg@...nel.org> wrote:
>> > Unfortunately I get a blank screen with after boot:
>> > Nacked-by: Pekka Enberg <penberg@...nel.org>
>
> But until you can tell me where it explodes on your system, we fix
> issues on several other machines...

Oh, that's nice, you first made the damn thing flicker in 2.6.39-rc1
and now you're fixing it for others by giving me a blank screen after
boot?

I guess I don't need to tell you that I am not at all happy especially
since you keep breaking i915 in almost every damn release!

>> Not sure this is related, but when I enable DRM_I915_KMS=y I'm got
>> stuck after boot too. When KMS is disabled I can at least get to the
>> console (no graphics)
>> This is with kernel 2.6.39-rc1.  It worked fine with 2.6.38. I don't
>> have much time bisect and reboot.  Shell I  try to pull drm-fixes for
>> rc2 or use try this patch?
>
> Add drm.debug=0xe to your grub kernel parameters and attach the dmesg for
> the failing boot. From that I should be able to recommend a course of
> action.

OK, I'll try that tonight.

                       Pekka
--
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/