Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 26 Sep 2014 14:34:43 +0000
From:      bugzilla-noreply@freebsd.org
To:        gnome@FreeBSD.org
Subject:   [Bug 193692] graphics/cairo: 1.12 crashes xorg server (NOT WITH_NEW_XORG)
Message-ID:  <bug-193692-6497-bmChrq4MyE@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-193692-6497@https.bugs.freebsd.org/bugzilla/>
References:  <bug-193692-6497@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193692

Johan Kuuse <kuuse@redantigua.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kuuse@redantigua.com

--- Comment #16 from Johan Kuuse <kuuse@redantigua.com> ---
Just confirming what others already have mentioned here.

Using a fresh FreeBSD 10.0 RELEASE install:
uname -a
FreeBSD latitude 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Fri Jan 17
01:46:25 UTC 2014     root@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC  i386


On a Dell Latitude E5400, with a Mobile Intel GM45 Express Chipset:
dmesg | grep 'apc\|agp'
vgapci0: <VGA-compatible display> port 0xefe8-0xefef mem
0xf6c00000-0xf6ffffff,0xe0000000-0xefffffff irq 16 at device 2.0 on pci0
agp0: <Intel GM45 SVGA controller> on vgapci0
agp0: aperture size is 256M, detected 32764k stolen memory
vgapci0: Boot video device
vgapci1: <VGA-compatible display> mem 0xf6b00000-0xf6bfffff at device 2.1 on
pci0

Xorg -retro works, so does starting startx, but running any
(cairo-dependent?)application causes an Xorg crash.
Workaround: Replace "intel" by "vesa" 
/etc/X11/xorg.conf:
    ###Driver      "intel"
    Driver      "vesa"

Not using WITH_NEW_XORG, as /etc/make.conf doesn't even exist.

With the Vesa driver, graphics quality is less than optimized, but I prefer not
to downgrading cairo and symlinking several others libs to fix what I hope is a
short time issue.

Opinion:
Not what you expect from a new RELEASE.
As mentioned by others, Intel chipsets are quite common out there, chances are
quite big this bug could have been nailed down.
I have been using FreeBSD since 3.0, and there have been few minor quirks in
releases in the past, but this is a big one.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-193692-6497-bmChrq4MyE>