linux-kernel - Re: Linux 2.6.23-rc2

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:	Sun, 05 Aug 2007 05:02:13 +0800
From:	"Antonino A. Daplas" <adaplas@...il.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Jeff Chua <jeff.chua.linux@...il.com>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: Linux 2.6.23-rc2

On Sat, 2007-08-04 at 11:06 -0700, H. Peter Anvin wrote:
> Linus Torvalds wrote:
> > 
> > On Sat, 4 Aug 2007, Jeff Chua wrote:
> >> On 8/4/07, Jeff Chua <jeff.chua.linux@...il.com> wrote:
> >>>> After resume from s2ram or switching to console from X, my console is
> >>>> messed up on rc1 and rc2. Is there a fix for this?
> >>> This is on IBM X60. i915 chipset. No problem on 2.6.22. If this is a
> >>> known problem, than I don't need to bisect all over again.
> >> I managed to bisect down to this commit. Without this, console screen
> >> can resume without video mess.
> > 
> > [ The commit being 4fd06960f120e02e9abc802a09f9511c400042a5: "Use the new 
> >   x86 setup code for i386" ]
> > 
> > Very interesting. 
> > 
> > Jeff - do I understand correctly that the "or" means that even *without* a 
> > suspend-to-ram sequence, and just by going into X and then going back to 
> > text-mode, the screen is corrupt?
> 
> Also, can you please describe "messed up" in more detail?  We had one
> report of "screen messed up" already that did get fixed
> (CONFIG_FIRMWARE_EDID not working.)

I believe this is the case where VBE DDC reading is non-contributory.

> 
> Are you using the VGA console or a framebuffer console?
> 
> Also, please submit your .config and kernel command line.

The dmesg output, the X logs and the s2ram options will also be useful.

Tony


-
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/