linux-kernel - Re: [Regression: 2.6.25-rc5: Blank Screen: Intel 945]

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, 1 Apr 2008 13:22:58 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Justin Madru <jdm64@...ab.com>
Cc:	lkml <linux-kernel@...r.kernel.org>,
	linux-fbdev-devel@...ts.sourceforge.net
Subject: Re: [Regression: 2.6.25-rc5: Blank Screen: Intel 945]

On Monday, March 31, 2008 12:24 pm Justin Madru wrote:
> Well, I disabled gdm and tryed to trigger the blank screen. I did about ~16
> reboots and it blanked out on me only 2 times. I was using a script to
> reboot and/or startx. One time I'm not exactly sure if X was started, so it
> might have blanked out on a "startx". The other time I'm fairly sure X
> wasn't started, so it blanked out on a terminal login.

Ok, so that might indicate something in the fb layer is killing it...

> Both of the blank outs were different than the ones with gdm started.
> Pressing ctrl+alt+f# changed nothing on the screen; the screen seemed
> almost completely off (no or little backlight). A few seconds after
> pressing the power button the shutdown splash screen would show, but this
> time it was _very_ faint.
>
> Usually, when gdm is enabled, pressing ctrl+alt+f# would "refresh" (or
> mode/resolution change) the screen, but it would still be blank. Also the
> backlight still seamed to be on and at full brightness (although, still
> displaying black).
>
> Well, I don't know what to say, it's the strangest of problems.

Yeah, seems pretty weird.  Given that you see it w/o the fb stuff loaded as 
well and we still have a few open bugs against the intel X driver regarding 
VT switch & mode programming, I don't think this is a real kernel regression.  
It's more likely that some timing or memory layout changed subtly and is 
causing to to hit one of our existing bugs more frequently that you did 
before.  Can you file a bug against the intel X driver at 
bugs.freedesktop.org so we can track it there?  Unless we can find a way to 
reproduce it reliably it'll probably take a long time to fix, but we don't 
want to lose it either...

Thanks,
Jesse
--
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/