Re: [regression?] Sometime (often) X come out blank (black screen) on cold boot - Intel chipset

Previous thread: [PATCH -rt 2/5] cpu-hotplug: vs page_alloc by Peter Zijlstra on Tuesday, June 10, 2008 - 4:13 am. (1 message)

Next thread: [PATCH] shm: Remove silly double assignment by Neil Horman on Tuesday, June 10, 2008 - 5:53 am. (4 messages)
From: Romano Giannetti
Date: Tuesday, June 10, 2008 - 5:38 am

I just opened this: http://bugzilla.kernel.org/show_bug.cgi?id=10892 . I
think itś a regression, but (read the description) I am not so sure, so
I checked regression but I have not blocked Rafael's metabug. 

Latest working kernel version: 2.6.25
Earliest failing kernel version: After 2.6.25, exatcly don't know, probably
2.6.26-rc3
Distribution:Ubuntu 8.04 Hardy
Hardware Environment: toshiba U305 intel-based laptop, see
http://bugzilla.kernel.org/attachment.cgi?id=16067&action=view
Software Environment:xserver-xorg-video-intel  2:2.2.1-1ubuntu12, see also
http://bugzilla.kernel.org/attachment.cgi?id=16066&action=view
Problem Description:

Sometime, on cold boot (after the laptop has been shut off), when the screen
switch from the Ubuntu startup to gdm, the screen goes blank. Forever.
Rebooting (warm) with the same kernel cures it, sometime. If I reboot 2.6.25 it
cures it everytime. 

Otherwise, the system seems to be working.

It was difficult to see because I almost never do a cold boot, the laptop is
either sleeping (s2ram) or on, or (warm) rebooted when I test a new kernel. 

Helps / tricks to gather more data when it happens are welcome.

-- 
Sorry for the disclaimer --- ¡I cannot stop it!



--
La presente comunicación tiene carácter confidencial y es para el exclusivo uso del destinatario indicado en la misma. Si Ud. no es el destinatario indicado, le informamos que cualquier forma de distribución, reproducción o uso de esta comunicación y/o de la información contenida en la misma están estrictamente prohibidos por la ley. Si Ud. ha recibido esta comunicación por error, por favor, notifíquelo inmediatamente al remitente contestando a este mensaje y proceda a continuación a destruirlo. Gracias por su colaboración.

This communication contains confidential information. It is for the exclusive use of the intended addressee. If you are not the intended addressee, please note that any form of distribution, copying or use of this communication or the information in it is ...
From: Jesse Barnes
Date: Tuesday, June 10, 2008 - 11:06 am

This sounds like a DUP; I remember Justin Madru had a similar issue (with 
Ubuntu & gdm even iirc).

Is there any way you could run the latest git bits of the Intel X driver?  
I've added some debugging that could catch at least one of the common reasons 
why the display would blank like that...

Thanks,
Jesse
--

From: Romano Giannetti
Date: Tuesday, June 10, 2008 - 10:03 pm

Yes, I think I can. Please give me instructions... I have a git
repository tracking Linus' one. 

BTW, maybe I'm on dope, but thinking hard, it seems to me that the blank
screen happens nly when I cold reboot after a crash forced me to
poweroff abruptly the laptop. Last time happened after a battery runoff.
It's that possible?

Moreover, I see a lot of flashing on shutdown (I'm sure I've seen a
report like that, but I am unable to dig it out now)...

Thanks,
	Romano 

-- 
Sorry for the disclaimer --- ¡I cannot stop it!



--
La presente comunicación tiene carácter confidencial y es para el exclusivo uso del destinatario indicado en la misma. Si Ud. no es el destinatario indicado, le informamos que cualquier forma de distribución, reproducción o uso de esta comunicación y/o de la información contenida en la misma están estrictamente prohibidos por la ley. Si Ud. ha recibido esta comunicación por error, por favor, notifíquelo inmediatamente al remitente contestando a este mensaje y proceda a continuación a destruirlo. Gracias por su colaboración.

This communication contains confidential information. It is for the exclusive use of the intended addressee. If you are not the intended addressee, please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited by law. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this message. Thank you for your cooperation. 
--

From: Jesse Barnes
Date: Wednesday, June 11, 2008 - 9:12 am

Check out http://www.intellinuxgraphics.org/ for instructions on building the 
driver.  You may also want to check out Freedesktop bug 15602 which Justin 
filed upstream (https://bugs.freedesktop.org/show_bug.cgi?id=15602).

Thanks,
Jesse
--

From: Romano Giannetti
Date: Friday, June 13, 2008 - 3:36 am

I will try to look at it --- RL entered in the game this week and
overwhelmed me a bit. 

Maybe it's related, maybe not, but as an hint I can say that the X
screen also used to go black everytime I switch from AC supply to
battery. This morning I did a ubuntu x-intel-driver update, and it seems
that now I can't reproduce that glitch anymore. 

Romano  
-- 
Sorry for the disclaimer --- ¡I cannot stop it!



--
La presente comunicación tiene carácter confidencial y es para el exclusivo uso del destinatario indicado en la misma. Si Ud. no es el destinatario indicado, le informamos que cualquier forma de distribución, reproducción o uso de esta comunicación y/o de la información contenida en la misma están estrictamente prohibidos por la ley. Si Ud. ha recibido esta comunicación por error, por favor, notifíquelo inmediatamente al remitente contestando a este mensaje y proceda a continuación a destruirlo. Gracias por su colaboración.

This communication contains confidential information. It is for the exclusive use of the intended addressee. If you are not the intended addressee, please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited by law. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this message. Thank you for your cooperation. 
--

From: Justin Madru
Date: Tuesday, June 10, 2008 - 9:33 pm

Seems like the same bug I reported:
https://bugs.freedesktop.org/show_bug.cgi?id=15602

Can you confirm, so Rafael Wysocki can mark your report 
http://bugzilla.kernel.org/show_bug.cgi?id=10892 as a dup of 
http://bugzilla.kernel.org/show_bug.cgi?id=10235.

Does disabling the boot splash fix the problem? You could also try 
disabling gdm and starting X manually. When I disable usplash it fixes 
the problem.

Are you sure kernel 2.6.25 doesn't also have the problem? Because I 
first saw the issue in 2.6.25-rc1. I tried doing a git bisect and came 
You could try git bisecting the bug, but you might run into problems. 
When I got down to the last ~80 commits the compiled kernel corrupted my 
real time clock! So, I'm not 100% sure the the commit that git reported 
was the _exact_ first bad, but fairly close (that, and the blank screen 
doesn't happen all the time). But if your git bisect returns the same or 
similar commit we might be able to narrow down the possibilities.

Jesse,
    It seems the problem might be related to usplash. In each reported 
case Ubuntu and usplash were used, and disabling usplash (at least for 
me) seems to fix the problem. Could there be some timing feature that 
usplash uses that isn't guaranteed/changed with some optimizations of 
CFS (or HR-timers) that went into 2.6.25? I've cc'ed Saïvann Carignan, 
who seems to be the most active contributer to usplash.

Justin Madru

--

From: Romano Giannetti
Date: Wednesday, June 11, 2008 - 12:38 am

Dunno. It happens to me ONLY on cold boot, and never otherwise. I had a

Will try. But it's quite rare for me, so triggering it is not so easy.
For the same reason, a bisect is difficult...

Romano

-- 
Sorry for the disclaimer --- ¡I cannot stop it!



--
La presente comunicación tiene carácter confidencial y es para el exclusivo uso del destinatario indicado en la misma. Si Ud. no es el destinatario indicado, le informamos que cualquier forma de distribución, reproducción o uso de esta comunicación y/o de la información contenida en la misma están estrictamente prohibidos por la ley. Si Ud. ha recibido esta comunicación por error, por favor, notifíquelo inmediatamente al remitente contestando a este mensaje y proceda a continuación a destruirlo. Gracias por su colaboración.

This communication contains confidential information. It is for the exclusive use of the intended addressee. If you are not the intended addressee, please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited by law. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this message. Thank you for your cooperation. 
--

From: Jesse Barnes
Date: Thursday, June 12, 2008 - 1:58 pm

Yeah, usplash really seems to affect things to make the bug more visible, but 
I still suspect a timing bug in xf86-video-intel...  Unfortunately those are 
hard to find & debug, but we're working on some related stuff, so hopefully 
we'll find & fix it soon.

Thanks,
Jesse
--

Previous thread: [PATCH -rt 2/5] cpu-hotplug: vs page_alloc by Peter Zijlstra on Tuesday, June 10, 2008 - 4:13 am. (1 message)

Next thread: [PATCH] shm: Remove silly double assignment by Neil Horman on Tuesday, June 10, 2008 - 5:53 am. (4 messages)