Bug 17485 - [965GM] display glitch + freeze when exiting X or switching to framebuffer
Summary: [965GM] display glitch + freeze when exiting X or switching to framebuffer
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium major
Assignee: Jesse Barnes
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2008-09-08 10:50 UTC by Tyler Lawson
Modified: 2008-11-18 00:36 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Xorg.0.log from a crashing session (31.55 KB, application/octet-stream)
2008-09-08 10:50 UTC, Tyler Lawson
no flags Details
xorg.conf (3.16 KB, text/plain)
2008-09-08 10:51 UTC, Tyler Lawson
no flags Details

Description Tyler Lawson 2008-09-08 10:50:43 UTC
Created attachment 18744 [details]
Xorg.0.log from a crashing session

Overview:
Upon quit, the X server will cause the display to glitch and freezes it.  Switching to a console window does not repair the damage - however, commands can still be typed and the X server can be resumed (with startx) normally.  I assume that, if you are using a login manager, this would appear as merely a graphical glitch.
This problem can also be reproduced while X is running by attempting to switch to a console running framebuffer graphics.  switching back with ctrl-alt-F7 restores the desktop.  the bug doesn't occur if framebuffer isn't running.

Steps to reproduce:
1)startx (.xinitrc contains only "exec startfluxbox")
2)exit X
or
1)startx
2)ctrl-alt-F1

Platform:
Thinkpad X61 tablet (model 7767B7U), Intel 965GM integrated graphics controller.
Running Gentoo, kernel 2.6.25-gentoo-r7.
xserver 1.5
xf86-video-intel 2.4.2
mesa 7.1
libdrm 2.3.1
fluxbox window manager
Comment 1 Tyler Lawson 2008-09-08 10:51:21 UTC
Created attachment 18745 [details]
xorg.conf
Comment 2 Jesse Barnes 2008-09-22 17:56:22 UTC
Are you using the vesafb driver?  We've had problems with most of the fb drivers on & off for a long time.  The main issue is that both the fb driver and the X driver think they own the hardware, and they don't always touch the same bits of GPU state, so one or the other get confused at VT switch (which also means suspend/resume) time.

To figure out what's going on we'll need the output of intel_reg_dumper while X is running and then when you VT switch away from it to an fb console.  Hopefully some difference will pop out to explain the problem...
Comment 3 Gordon Jin 2008-10-28 01:56:28 UTC
ping Tyler
Comment 4 Michael Fu 2008-11-18 00:36:47 UTC
reject due to no response from bug reporter.


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.