FS#22713 - [kernel26] Laptop Sometimes Boots to Scrambled Color Screen

Attached to Project: Arch Linux
Opened by Jeremy LaCroix (jlacroix) - Wednesday, 02 February 2011, 03:01 GMT
Last edited by Andrea Scarpino (BaSh) - Saturday, 18 June 2011, 08:35 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
This is really hard to explain, so I attached a picture. Basically, sometimes my laptop (a Dell Latitude E6410 with integrated Intel graphics, WXGA+ panel) gets a corrupted screen X is about to start. This doesn't happen every time. Maybe one out of every five boots or so. When I reboot it, it may or may not launch X correctly.

When it does happen, the entire panel gets pixelated and gets brighter and brighter until it's almost all white.

I can reboot the laptop when this happens by switching to a tty and rebooting from there. I can't see the tty, just the garbled colors. But I can still execute the commands in the tty by just entering my username/password and "sudo reboot" without seeing the screen, from memory.

I'm not sure what the trigger is, but I know it happens a bit more often with 2.6.37.

Steps to reproduce:
Unfortunately, I've not determined any pattern.
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Saturday, 18 June 2011, 08:35 GMT
Reason for closing:  Fixed
Additional comments about closing:  kernel26 2.6.39-1
Comment by Thomas Dziedzic (tomd123) - Saturday, 05 February 2011, 01:37 GMT
Can you attach the output of lspci?
Comment by Jeremy LaCroix (jlacroix) - Saturday, 05 February 2011, 02:39 GMT
Attached.

I also had a chance to test 2.6.38 by installing kernel26-mainline from AUR. On that kernel, I do not have this problem. But, with that kernel the backlight won't turn on after resuming from sleep so I'm trading one problem for another.
Comment by Jelle van der Waa (jelly) - Thursday, 14 April 2011, 20:27 GMT
is this still an issue with our .38 kernel?
Comment by Jelle van der Waa (jelly) - Thursday, 16 June 2011, 10:24 GMT
and with .39?
Comment by Jeremy LaCroix (jlacroix) - Friday, 17 June 2011, 02:48 GMT
This problem doesn't exist with .39.

Loading...