Ubuntu
xserver-xorg-video-intel package

[i945] (UXA) 945GM [8086:27a2] (rev 03): Xserver crashes when Virtual > 2048

Bug #382327 reported by cgrushko on 2009-06-01

This bug report is a duplicate of: Bug #351756: [i945gm] Xorg crashed after external monitor in drm_intel_bo_reference() from i830_set_pixmap_bo - no dri for virtual > 2048 (UXA bug). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	xserver-xorg-video-intel (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Binary package hint: xserver-xorg-video-intel

Running on a laptop and attaching an external monitor,
if the combined resolution is more than 2048, X-server will not
start.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: xserver-xorg-video-intel 2:2.7.1-0ubuntu1~xup~1
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersion: Linux version 2.6.28-11-generic (buildd@palmer) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009
SourcePackage: xserver-xorg-video-intel
Uname: Linux 2.6.28-11-generic i686
UnreportableReason: This is not a genuine Ubuntu package
xkbcomp:

[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: Dell Device [1028:01d4]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03)
Subsystem: Dell Device [1028:01d4]

See original description

Tags:

Revision history for this message

cgrushko (carmi-grushko) wrote on 2009-06-01:

Dependencies.txt Edit (4.2 KiB, text/plain; charset="utf-8")
LsHal.txt Edit (142.6 KiB, text/plain; charset="utf-8")
LsMod.txt Edit (2.4 KiB, text/plain; charset="utf-8")
LsPci.txt Edit (10.9 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (1.1 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (17.1 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (17.1 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (6.0 KiB, text/plain; charset="utf-8")
glxinfo.txt Edit (11.7 KiB, text/plain; charset="utf-8")
monitors.xml.txt Edit (949 bytes, text/plain; charset="utf-8")
setxkbmap.txt Edit (320 bytes, text/plain; charset="utf-8")
system.txt Edit (297 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (10.6 KiB, text/plain; charset="utf-8")

Bryce Harrington (bryce) on 2009-06-02

summary:

- (UXA) 945GM [8086:27a2] (rev 03): Resolution width is limited to 2048
+ [i945] (UXA) 945GM [8086:27a2] (rev 03): Resolution width is limited to
+ 2048

Bryce Harrington (bryce) on 2009-06-02

Changed in xserver-xorg-video-intel (Ubuntu):
status:	New → Confirmed

Bryce Harrington (bryce) on 2009-06-02

description:

updated

Geir Ove Myhr (gomyhr) on 2009-06-02

tags:	added: 945gm crash intel xorg
tags:	added: jaunty

Revision history for this message

Geir Ove Myhr (gomyhr) wrote on 2009-06-02: Re: [i945] (UXA) 945GM [8086:27a2] (rev 03): Resolution width is limited to 2048

The end of your Xorg.0.log files indicates that X is crashing. Could you get a full backtrace with any of the methods described at https://wiki.ubuntu.com/X/Backtracing ?

Also, is the crash triggered when the Virtual part is not commented out even if an external monitor is not connected, or do you need the external monitor connected as well?

Revision history for this message

cgrushko (carmi-grushko) wrote on 2009-06-03:

1. Backtrace - wasn't really sure how to do this, so ended up letting Apport open another bug report: bug #383029.

2. Crashes are triggered without an external monitor attached, as soon as the Virtual part is uncommented.

Revision history for this message

Geir Ove Myhr (gomyhr) wrote on 2009-06-03: Re: [Bug 382327] Re: [i945] (UXA) 945GM [8086:27a2] (rev 03): Resolution width is limited to 2048

> 1. Backtrace - wasn't really sure how to do this, so ended up letting
> Apport open another bug report: bug #383029.

That's okay. I'm also not sure how to add crash reports to an existing
bug using apport (there is apport-collect, but it mainly collects logs
etc., not sure if it can upload crash reports as well). For some
reason I cannot access bug 383029 (it is marked private, but I
normally have access to those). Would you mind looking through the
stracktrace and see if you recognize something important like one of
your passwords? If not, you may mark the bug as public.

> 2. Crashes are triggered without an external monitor attached, as soon
> as the Virtual part is uncommented.

Good to know. Having a virtual setting is necessary to use dual-head,
but it's not actually the extra monitor triggering the bug.

This bug is similar to bug 379804, except that for that one it just
hangs and does not crash (so it's not a duplicate).

summary:

- [i945] (UXA) 945GM [8086:27a2] (rev 03): Resolution width is limited to
+ [i945] (UXA) 945GM [8086:27a2] (rev 03): Xserver crashes when Virtual >
2048

Revision history for this message

cgrushko (carmi-grushko) wrote on 2009-06-03:

Changed privacy settings for bug #383029.
(hopefully no passwords in it...)

Revision history for this message

Geir Ove Myhr (gomyhr) wrote on 2009-06-03:

The information looks just fine privacy wise. Unfortunately the stacktrace itself is not very good (the lines with ??). If you could install the package xserver-xorg-video-intel-dbg and repeat the procedure, that package should have the necessary information to fill the ?? with useful information. (There are a few other -dbg packages mentioned on https://wiki.ubuntu.com/X/Backtracing , you may install those as well just to be sure).

Revision history for this message

Geir Ove Myhr (gomyhr) wrote on 2009-06-03:

Btw, it is possible that Launchpad has some magic to fill in those question marks (retracing). Retracing is usually done shortly after a bug is reported, but in your case it is not done yet. Maybe the Launchpad servers are very busy at the moment. Anyway, I'm not sure if it will fill in the blanks, but you may want to wait and see if it is a lot of work to repeat with the -dbg packages.

Revision history for this message

cgrushko (carmi-grushko) wrote on 2009-06-03:

Being a developer myself (but not in Linux, yet) I should have guessed the stack trace is not enough.
A new bug report got created, bug #383347.
I subscribed you to it, so you should have access to it.

Anyway, I'm curious about what's going on, on the technical level.

Revision history for this message

Geir Ove Myhr (gomyhr) wrote on 2009-06-03:

Thank you! The new stack traces look much better. I will leave it for a while to see if the Apport retracing service does its magic.

On the technical level I don't have much of an explanation to offer, as I'm not a developer.

Looking a bit at it, this looks very similar this upstream bug:
http://bugs.freedesktop.org/show_bug.cgi?id=21571
which is marked as a duplicate of
http://bugs.freedesktop.org/show_bug.cgi?id=21190

The corresponding bug here is bug 351756. Since it has 7 duplicates already, it's likely that this one is also a duplicate. The apport retrace service should detect that automatically. You may follow the upstream bug report and see if the fix that should come also fixes the problem for you.

Revision history for this message

Geir Ove Myhr (gomyhr) wrote on 2009-06-07:

#10

The apport retracing service has done its job at bug report 383347, but nothing more came out of it. Actually, it seems that the retracing service doesn't include the necessary debug packages either, so your manual backtrace was better. I compared it manually to the one in bug 351756, though, and it seems to be exactly the same (the line numbers are a bit off, but that stack trace is for 2.7.0, while yours is for 2.7.1).

I'm going to mark this bug as a duplicate of 351756 (and I think I will simply invalidate the apport-bug 383347 so that nobody spends extra time on it). Thank you for all the information. It would be nice if you can verify any solution that might come to bug 383347.