Bug 15608

Summary: [965GM] Font corruption when switching back from VT to X
Product: xorg Reporter: Marcus Furlong <furlongm>
Component: Driver/intelAssignee: Wang Zhenyu <zhenyu.z.wang>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: high CC: dev, remi
Version: gitKeywords: regression
Hardware: x86 (IA32)   
OS: Linux (All)   
URL: https://bugs.gentoo.org/show_bug.cgi?id=218190
i915 platform: i915 features:
Description Flags
dmesg none

Description Marcus Furlong 2008-04-19 09:38:18 UTC
Created attachment 16041 [details]

Fonts are corrupted (look like little blocks) when I switch back to X from a
virtual console. Restarting X is the only solution.

Reproducible: Always with .903, not with .902 or .901

Steps to Reproduce:
1. Switch to virtual console and make some output occur (e.g. dmesg)
2. Switch back to X with Ctrl-Alt-F7

Actual Results:  
Fonts are corrupted, can't read anything.
Screenshot: https://bugs.gentoo.org/attachment.cgi?id=150117

Expected Results:  
Non-corrupt fonts.

uname -a
Linux griffith #1 SMP PREEMPT Thu Mar 13 00:41:57 GMT 2008 i686 Intel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHz GenuineIntel GNU/Linux

Package versions (Gentoo)

lspci -vv
00:02.0 VGA compatible controller: Intel Corporation Mobile Integrated Graphics Controller (rev 0c) (prog-if 00 [VGA controller])
        Subsystem: Dell Unknown device 01fe
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 16
        Region 0: Memory at fea00000 (64-bit, non-prefetchable) [size=1M]
        Region 2: Memory at e0000000 (64-bit, prefetchable) [size=256M]
        Region 4: I/O ports at efe8 [size=8]
        Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
                Address: 00000000  Data: 0000
        Capabilities: [d0] Power Management version 3
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
                Bridge: PM- B3+
Comment 1 Marcus Furlong 2008-04-19 09:39:08 UTC
Created attachment 16042 [details]
Comment 2 Marcus Furlong 2008-04-19 09:39:30 UTC
Created attachment 16043 [details]
Comment 3 Gordon Jin 2008-04-21 01:34:04 UTC
Increasing priority as this is regression.
Comment 4 Wang Zhenyu 2008-04-21 02:04:03 UTC
I can't produce on Lenovo T61 here, in gnome switch vt, X came back normally.
Could you try current 2.3-branch? or could you nail down what change might cause this? (try options like "Tiling" "EXANoComposite", etc.)
Comment 5 Aike J Sommer 2008-04-24 06:31:31 UTC
I had the same problem... EXANoComposite fixed this!!
Comment 6 Wang Zhenyu 2008-04-24 17:45:06 UTC
Aike, what's the model of your machine? Have you seen this corrupt before (like 2.2.1) or just recent 2.3.0? Possible to try to see if that's regression?
Comment 7 Marcus Furlong 2008-04-24 18:27:48 UTC
(In reply to comment #4)
> I can't produce on Lenovo T61 here, in gnome switch vt, X came back normally.
> Could you try current 2.3-branch? or could you nail down what change might
> cause this? (try options like "Tiling" "EXANoComposite", etc.)

EXANoComposite seemed to fix it. Is that a boolean? It doesn't matter whether I set it true or false, it fixes it either way.

Only occurs on 903 for me, 902 and 901 are fine.
Comment 8 Aike J Sommer 2008-04-25 00:19:08 UTC
It's a Dell XPS M1330...
I have this with all versions i tried, being 902, 903 and 2.3.0 (and whatever opensuse 11.0 beta 1 installed as default).
Comment 9 Wang Zhenyu 2008-06-18 01:23:35 UTC
Could you test with current 2.3.2 release?
Comment 10 Aike J Sommer 2008-06-18 04:03:13 UTC
Just tested it, and it seems to be fixed for me!!
Comment 11 Wang Zhenyu 2008-06-18 18:24:55 UTC
Nice! I'm closing this one, feel free to reopen if this issue still catch you in any case.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.