[i945GM] After loading background crashes back to GDM. Works with 'driver "vesa"'.

[Saku Ytti]

Binary package hint: xserver-xorg-video-intel

As par Martin's recommendation in #320525 I'm opening new bug.

Prior to the 'garbled' video issue described in aforementioned bug ID everything was working ok, the new intel driver fixed the 'garbled' video, but I still can't start session.

GDM displays now correctly, but after logging in and after background has been loaded it crashes back to X, flashing quickly
blue vertical gabled bars.

If I add 'driver "vesa"' in xorg.conf session starts normally.

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
Package: xserver-xorg-video-intel 2:2.6.1-1ubuntu1
ProcEnviron:
 SHELL=/bin/zsh
 PATH=(custom, user)
 LANG=en_GB.UTF-8
ProcVersion: Linux version 2.6.28-5-generic (buildd@crested) (gcc version 4.3.3 20090119 (prerelease) (Ubuntu 4.3.2-2ubuntu14) ) #15-Ubuntu SMP Fri Jan 23 01:16:33 UTC 2009

SourcePackage: xserver-xorg-video-intel
Uname: Linux 2.6.28-5-generic x86_64

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub [8086:27a0] (rev 03)
 Subsystem: Hewlett-Packard Company Device [103c:30aa]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03)
 Subsystem: Hewlett-Packard Company Device [103c:30aa]

[Saku Ytti (ubuntu-ip)]

Requested files + xsession-errors.

--
  ++ytti

[Martin Olsson (mnemo)]

Here is the warnings and errors from that xorg.log.old above:

(WW) intel(0): libpciaccess reported 0 rom size, guessing 64kB
(WW) intel(0): Register 0x61200 (PP_STATUS) changed from 0xc0000008 to 0xd000000a
(WW) intel(0): PP_STATUS before: on, ready, sequencing idle
(WW) intel(0): PP_STATUS after: on, ready, sequencing on
(WW) intel(0): Register 0x70024 (PIPEASTAT) changed from 0x00000000 to 0x00000203
(WW) intel(0): PIPEASTAT before: status:
(WW) intel(0): PIPEASTAT after: status: VSYNC_INT_STATUS VBLANK_INT_STATUS OREG_UPDATE_STATUS
(WW) intel(0): Register 0x71024 (PIPEBSTAT) changed from 0x00000202 to 0x80000242
(WW) intel(0): PIPEBSTAT before: status: VSYNC_INT_STATUS VBLANK_INT_STATUS
(WW) intel(0): PIPEBSTAT after: status: FIFO_UNDERRUN VSYNC_INT_STATUS LBLC_EVENT_STATUS VBLANK_INT_STATUS
(WW) intel(0): DRI2 requires UXA
(EE) intel(0): Failed to set tiling on front buffer: rejected by kernel
(EE) intel(0): Failed to set tiling on back buffer: rejected by kernel
(EE) intel(0): Failed to set tiling on depth buffer: rejected by kernel
(WW) intel(0): ESR is 0x00000001, instruction error
(WW) intel(0): Existing errors found in hardware state.

[Martin Olsson (mnemo)]

Since it says DRI2 requires UXA, can you attach your xorg.conf as well? Beyond option DRI2 you I think need to enable UXA maybe?

[Martin Olsson (mnemo)]

I assumed the DRI2 messages meant you were trying to run some non-default config but actually I have the DRI2 requires UXA warning on my working G45 jaunty machine as well so that's probably not the problem.

[Martin Olsson (mnemo)]

Out of curiousity, what happens if you add this to the "Device" section in xorg.conf:

        Option "AccelMethod" "UXA"
        Option "Tiling" "No"

[Saku Ytti (ubuntu-ip)]

No difference.

[Lorenco Trichardt (trichalo)]

I have 100% the same running on Thinkpad T60 hmmm
Let me know if I can add more info and things to try to shed light on this issue.

[Rich Johnson (nixternal)]

Confirming! I have this problem and there is also a duplicate report for this problem. The duplicate was marked a duplicate of another bug, the one where Saku was told to create this new bug because it was different than the reported issue. Everything is pretty much the same for me, however I am using a G31.

[Rich Johnson (nixternal)]

Sorry for all of the changes, silly launchpad or firefox with my groovy new mouse is wreaking havoc! :)

[Rich Johnson (nixternal)]

Timo, please quite marking bugs duplicates when they are not. You have done this on 2 or 3 of the bugs I have reported on today and they weren't even close to being duplicates in the first place. This is a bug, the one you just linked against is a fixed released, and guess what, it hasn't been fixed for us.

[Timo Aaltonen (tjaalton)]

Please update to the latest packages.. that error has occured to me when the mesa version was too old (=incompatible), and the amd64 version was not available for some time because of build-daemon problems. If you still can reproduce it with the latest packages, show what 'apt-cache policy libgl1-mesa-dri' outputs.

The reason why I marked it a dupe was that I got two confirmations on irc that the update fixed issues like this (KDE not starting at all, Compiz crashing the X). The update was not available on the archive, I just build it for them so they could test (32bit version, you seem to have 64bit)...

[Saku Ytti (ubuntu-ip)]

You're right, I did got packages, including mesa now, which were not available yesterday while troubleshooting.

After installing the packages, I could again start gnome with intel driver. During the whole 'poor intel GPU performance'
issue I saw ~300fps for glxgears, now I got ~60fps. After enabling UXA I get ~500fps. I don't think 500fps is yet
where it should be, but from usability point of view, I have no complains now. mplayer videos work in full screen,
compiz cube switches without lag.

Thanks guys.

[Timo Aaltonen (tjaalton)]

thanks for testing

mind you, glxgears is not a benchmark, and the reason why it shows 60fps is that vblank is used with DRI1, UXA enables DRI2, and for some reason it doesn't use vblank yet.

[Lorenco Trichardt (trichalo)]

I have one more issue after the crash....

I can not switch ctrl+alt+Fx anymore (Get a black screen?) Then have to force quit the XServer(ctrl+alt+backspace) .... Even ctrl+alt+F7 copmes up blank ?

should I open a new Bug report ?

[Carey Underwood (cwillu)]

Saku, can you check if things are working properly with the current updates (i.e., not crashing) with UXA disabled (which means you'll be running under EAX)?

If things aren't actually crashing anymore, I'll mark this as Fix Released.

This bug report is specifically related to the crash, any lingering performances issues need to be addressed in a new bug report, and any issues related to UXA should also be in their own bug reports.

[Lorenco Trichardt (trichalo)]

The latest updates I got made everthing gone bad again. (Was happy with UXA enabled)
Then I had a couple of freezes since updates yesterday (06)

Now I had three crshes today. Have now removed UXA but get a lot of corruption ??

[Andres Mujica (andres.mujica)]

Saku, are you seeing the same issue as Lorenco? the original reported crashes i mean?

[Saku Ytti (ubuntu-ip)]

Sorry for not replying earlier, I've been on vacation and tried to kept away from computer. Anyhow no, I have not seen this crash in ages. Thank you for your work.

[Bryce Harrington (bryce)]

Hi Saku,

This one is fixed in karmic, with a tiling fix to the kernel. It'd be great if you could test karmic alpha-2 or newer and verify it is indeed solved now.

[Bryce Harrington (bryce)]

Actually, since you've already indicated you're no longer seeing it, I guess we can close it at this time. Thanks again.