[i945] Xorg crashed with SIGSEGV in CreateSolidPicture() [Classic Desktop]

Bug #705295 reported by Robert Abramovitz
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Running from the LiveCD of 1/19/2011.

I ran nothing. These errors occured while the window system was coming up.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: xserver-xorg-core 2:1.9.0.902-1ubuntu4
ProcVersionSignature: Ubuntu 2.6.37-12.26-generic 2.6.37
Uname: Linux 2.6.37-12-generic i686
Architecture: i386
DRM.card0.VGA.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1280x1024 1280x1024 1024x768 1024x768 1024x768 800x600 800x600 800x600 800x600 640x480 640x480 640x480 720x400
 edid-base64: AP///////wA6rAEAAQAAACAMAQMIIhsAygsynFpNjCYgTlevzwCBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAUg4RAAAeAAAA/gAKICAgICAgICAgICAgAAAA/gAKICAgICAgICAgICAgAAAA/AAKICAgICAgICAgICAgANY=
Date: Thu Jan 20 06:51:52 2011
DistUpgraded: Fresh install
DistroCodename: natty
DistroVariant: ubuntu
ExecutablePath: /usr/bin/Xorg
GdmLog1: Not present
GdmLog2: Not present
GraphicsCard: Subsystem: Intel Corporation Device [8086:464c]
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110119)
ProcCmdline: X -br -ac -noreset -nolisten tcp -nr vt7 :0
ProcEnviron:
 LANGUAGE=
 PATH=(custom, no user)
 LANG=en_US.UTF-8
ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
ProcKernelCmdLine_: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
SegvAnalysis:
 Segfault happened at: 0x813311e: movb $0x23,(%eax)
 PC (0x0813311e) ok
 source "$0x23" ok
 destination "(%eax)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: xorg-server
StacktraceTop:
 ?? ()
 CreateSolidPicture ()
 ?? () from /usr/lib/xorg/modules/drivers/intel_drv.so
 CompositeRects ()
 ?? ()
Title: Xorg crashed with SIGSEGV in CreateSolidPicture()
UnitySupportTest:

UserGroups:

dmi.bios.date: 04/14/2010
dmi.bios.vendor: Intel Corp.
dmi.bios.version: LF94510J.86A.0278.2010.0414.2000
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: D945GCLF
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE27042-400
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrLF94510J.86A.0278.2010.0414.2000:bd04/14/2010:svn:pn:pvr:rvnIntelCorporation:rnD945GCLF:rvrAAE27042-400:cvn:ct3:cvr:
version.libdrm2: libdrm2 2.4.22-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 7.9+repack-1ubuntu6
version.xserver-xorg: xserver-xorg 1:7.5+6ubuntu7
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.13.2-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.13.901-2ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20100805+b96170a-0ubuntu1

Revision history for this message
Robert Abramovitz (bromo) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 XISendDeviceHierarchyEvent (flags=0xbfa682cc)
 DisableDevice (dev=0x99d2e18, sendevent=1 '\001')
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in xorg-server (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Bryce Harrington (bryce) wrote : Re: Xorg crashed with SIGSEGV in CreateSolidPicture()

Hey, tell me more... the backtrace doesn't reveal what the problem is, so I need a more detailed description of your situation, your hardware, etc.

Changed in xorg-server (Ubuntu):
status: New → Incomplete
visibility: private → public
Revision history for this message
Robert Abramovitz (bromo) wrote : Re: [Bug 705295] Re: Xorg crashed with SIGSEGV in CreateSolidPicture()

Hi Bryce,

I was running a Live install from the natty-desktop-i386.iso built on
20-Jan-2011. As Ubuntu was booting a dialog box appeared stating that my HW
was not able to support Unity and gave me the option of choosing the Classic
User session. I chose this option and Ubuntu came up. Immediately I began
to get dialog boxes stating that various applications had unexpectedly quit
and could be reloaded. The following apps issued the unexpected exit
dialogs:
Show Desktop
Window List
Workspace switcher
Trash
Notification Area
Indication Applet
Indication Applet Session
Clock

Clock SEGV'd and this was where the error reporting began.

My HW is an Intel Atom based motherboard. Here are the details
dmi.bios.date: 07/29/2009
dmi.bios.vendor: Intel Corp.
dmi.bios.version: LF94510J.86A.0229.2009.0729.0209
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: D945GCLF
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE27042-400
dmi.chassis.type: 3

If you need additional information I will be happy to provide it.

"Bryce Harrington"

> Hey, tell me more... the backtrace doesn't reveal what the problem is,
> so I need a more detailed description of your situation, your hardware,
> etc.
>
> ** Changed in: xorg-server (Ubuntu)
> Status: New => Incomplete
>
> ** Visibility changed to: Public

Bryce Harrington (bryce)
summary: - Xorg crashed with SIGSEGV in CreateSolidPicture()
+ Xorg crashed with SIGSEGV in CreateSolidPicture() [Classic Desktop]
summary: - Xorg crashed with SIGSEGV in CreateSolidPicture() [Classic Desktop]
+ [i945] Xorg crashed with SIGSEGV in CreateSolidPicture() [Classic
+ Desktop]
Revision history for this message
Bryce Harrington (bryce) wrote :

Those application restart dialogs are a known issue with the Classic Desktop, and unrelated to the X crash.

Do you have any idea why unity would refuse to run on this hardware? It looks like a bog standard i945 graphics chip, and I've run unity on i945 many a time so it seems odd it would refuse you.

So that's one bug.

Second bug is that apport isn't collecting a valid backtrace. Are you comfortable using gdb to collect backtraces? If so, would you mind attaching to X and manually collecting a backtrace? Some directions are available at http://wiki.ubuntu.com/X/Backtracing (skip over the Apport stuff).

Third bug is the X crash itself. At this point there's not enough evidence on hand to make guesses about it, except that it seems to be something in the compositor.

Bryce Harrington (bryce)
Changed in xorg-server (Ubuntu):
status: Incomplete → New
status: New → Incomplete
Revision history for this message
bugbot (bugbot) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Revision history for this message
Bryce Harrington (bryce) wrote :

Possibly this is a dupe of 714829

Changed in xorg-server (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.