Bug 13227

Summary:

VT switch broken

Product:

xorg

Reporter:

Bill Nottingham <notting>

Component:

Driver/intel

Assignee:

Jesse Barnes <jbarnes>

Status:

RESOLVED FIXED

QA Contact:

Xorg Project Team <xorg-team>

Severity:

normal

Priority:

medium

Version:

git

Hardware:

Other

OS:

All

Whiteboard:

i915 platform:

i915 features:

Bug Depends on:

Bug Blocks:

13027

Attachments:

Description	Flags
X log	none

Description Bill Nottingham 2007-11-13 12:45:35 UTC

I just get a white screen.

(II) AIGLX: Suspending AIGLX clients for VT switch
(II) intel(0): fbc disabled on pipe a
(II) intel(0): xf86UnbindGARTMemory: unbind key 1
(II) intel(0): xf86UnbindGARTMemory: unbind key 2
(II) intel(0): xf86UnbindGARTMemory: unbind key 0
(II) intel(0): xf86UnbindGARTMemory: unbind key 3
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) AIGLX: Resuming AIGLX clients after VT switch
(II) intel(0): xf86BindGARTMemory: bind key 1 at 0x01000000 (pgoffset 4096)
(II) intel(0): xf86BindGARTMemory: bind key 2 at 0x02000000 (pgoffset 8192)
(II) intel(0): xf86BindGARTMemory: bind key 0 at 0x04000000 (pgoffset 16384)
(II) intel(0): xf86BindGARTMemory: bind key 3 at 0x08000000 (pgoffset 32768)
(II) intel(0): Fixed memory allocation layout:
(II) intel(0): 0x00000000-0x0001ffff: ring buffer (128 kB)
(II) intel(0): 0x00020000-0x0061ffff: compressed frame buffer (6144 kB, 0x00000000bf820000 physical
)
(II) intel(0): 0x00620000-0x00620fff: compressed ll buffer (4 kB, 0x00000000bfe20000 physical
)
(II) intel(0): 0x00621000-0x0062afff: HW cursors (40 kB, 0x00000000bfe21000 physical
)
(II) intel(0): 0x0062b000-0x00632fff: logical 3D context (32 kB)
(II) intel(0): 0x00633000-0x00633fff: overlay registers (4 kB, 0x00000000bfe33000 physical
)
(II) intel(0): 0x00634000-0x00643fff: xaa scratch (64 kB)
(II) intel(0): 0x007bf000:            end of stolen memory
(II) intel(0): 0x01000000-0x01ffffff: back buffer (11264 kB) X tiled
(II) intel(0): 0x02000000-0x02ffffff: depth buffer (11264 kB) X tiled
(II) intel(0): 0x04000000-0x07ffffff: front buffer (44800 kB) X tiled
(II) intel(0): 0x08000000-0x09ffffff: classic textures (32768 kB)
(II) intel(0): 0x10000000:            end of aperture
(II) intel(0): fbc disabled on pipe a
(II) intel(0): fbc disabled on pipe a
(II) intel(0): Output configuration:
(II) intel(0):   Pipe A is off
(II) intel(0):   Display plane A is now disabled and connected to pipe A.
(II) intel(0):   Pipe B is on
(II) intel(0):   Display plane B is now enabled and connected to pipe B.
(II) intel(0):   Output VGA is connected to pipe none
(II) intel(0):   Output LVDS is connected to pipe B
(II) intel(0):   Output TMDS-1 is connected to pipe none
(II) intel(0): [drm] dma control initialized, using IRQ 16
(II) <default pointer>: ps2EnableDataReporting: succeeded
(II) 3rd Button detected: disabling emulate3Button

are the relevant messages.

xorg-x11-server-Xorg-1.4.99.1-0.8.fc9
xorg-x11-drv-i810-2.1.99-0.fc9

Comment 1 Gordon Jin 2007-11-13 17:53:02 UTC

What platfrom are you using? Please attach the full log.

Comment 2 Bill Nottingham 2007-11-13 19:39:50 UTC

Created attachment 12533 [details]
X log

Platform is Fedora 8/development, x86_64.

Comment 3 Jesse Barnes 2007-11-13 20:45:45 UTC

Was this after a fresh startup or after a suspend/resume cycle?

I think this may be a DUP of 12994.  It also shows tiled front buffer allocation with XAA, which won't work.  I'll try to reproduce on my T61.

Comment 4 Bill Nottingham 2007-11-13 22:06:48 UTC

Either or - the failure mode changes (sometimes blank white, other times random garbage).

Comment 5 Jesse Barnes 2007-11-14 09:13:49 UTC

Bill, can you try the latest driver bits from git?  Zhenyu checked in some fixes that might help this case.

Comment 6 Bill Nottingham 2007-11-14 10:40:02 UTC

git master seems to work.

Comment 7 Jesse Barnes 2007-11-14 11:25:52 UTC

Excellent, thanks for testing.

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.