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] [day] [month] [year] [list]
Date:	Mon, 03 Mar 2014 11:31:25 +0200
From:	Jani Nikula <jani.nikula@...ux.intel.com>
To:	prometheanfire@...too.org, daniel.vetter@...ll.ch,
	airlied@...ux.ie, intel-gfx@...ts.freedesktop.org,
	"kernel\@gentoo.org" <kernel@...too.org>,
	dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Subject: Re: i915 - Corruption on boot for 3.13.x

On Fri, 28 Feb 2014, Matthew Thode <prometheanfire@...too.org> wrote:
> Hardware is a T520 with a i5-2520M (intel only).
>
> Booting via uefi stub, kernel config is attached.
>
> This is broken on 3.13.x the video shows hardened kernel being booted,
> but I've tested kernel.org sources as well with the same effect.
>
> I can boot, login and shutdown, etc; just graphics is broken.
>
> https://www.youtube.com/watch?v=yxDyvyJTrXs
>
> Think that's it, let me know if there's more info I can get you.

Hi Matthew, thanks for the report.

Please file a bug on DRM/Intel component at [1]. Just because my gut
feeling says this will be better tracked there than by cluttering the
list...

On the bug, please indicate:

Did this use to work? Which kernel version?

Please disable i915.ko and see if there's still corruption in the
fb. It's hard to see from the video whether the corruption starts before
i915 gets loaded.

Please attach dmesg from early boot with drm.debug=0xe module parameter
set.


BR,
Jani.


[1] https://bugs.freedesktop.org/enter_bug.cgi?product=DRI

-- 
Jani Nikula, Intel Open Source Technology Center
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ