Bug 501272

Summary:	kernel.org-3.13.3: intel corrupted screen on boot
Product:	Gentoo Linux	Reporter:	Matthew Thode ( prometheanfire ) <prometheanfire>
Component:	[OLD] Core system	Assignee:	Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel>
Status:	RESOLVED OBSOLETE
Severity:	normal	CC:	nikoli, pageexec, spender
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	corrupted-intel.dmesg kernel.org-sources-3.13.3.config

Description Matthew Thode ( prometheanfire ) archtester

2014-02-14 06:56:24 UTC

I'm able to log in and reboot just fine.

Also, when starting X it's just black and nothing comes back if I try and switch to tty1.

Here's a pic of the corruption.   http://i.imgur.com/e4VFiuC.jpg

Comment 1 PaX Team 2014-02-14 13:31:32 UTC

what's the video driver you use? is it perhaps http://forums.grsecurity.net/viewtopic.php?f=3&t=3922?

Comment 2 Matthew Thode ( prometheanfire ) archtester

2014-02-14 15:54:39 UTC

This is intel :P

Comment 3 PaX Team 2014-02-14 16:49:39 UTC

is there anything suspicious in dmesg?

Comment 4 Matthew Thode ( prometheanfire ) archtester

2014-02-14 17:26:28 UTC

Created attachment 370410 [details]
corrupted-intel.dmesg

Comment 5 Matthew Thode ( prometheanfire ) archtester

2014-02-15 06:23:33 UTC

Created attachment 370456 [details]
kernel.org-sources-3.13.3.config

I have this error with vanilla kernel.

Hardware is a Lenovo T520 intel gfx only, kconfig attached

Comment 6 DaggyStyle 2014-02-15 13:53:12 UTC

(In reply to Matthew Thode ( prometheanfire ) from comment #2)
> This is intel :P

actually, imho 3.13.x is bad for gpus overall, I have a multiseat system with three gpus: HD5450, HD3650 and a intel igp (i7-2600).

in 3.13.0 the hd5450 got bricked, in 3.13.1 the intel gpu got bricked and finally in 3.13.3 the hd3650 got bricked.

beats me how they managed to do that...

Comment 7 Mike Pagano gentoo-dev

2014-08-15 12:17:33 UTC

3.13 is no longer in the tree or upstream supported. If this still is an issue with later kernels, please comment here.