From owner-freebsd-x11@freebsd.org  Thu Sep  3 19:51:09 2015
Return-Path: <owner-freebsd-x11@freebsd.org>
Delivered-To: freebsd-x11@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6C54C9CACD5
 for <freebsd-x11@mailman.ysv.freebsd.org>;
 Thu,  3 Sep 2015 19:51:09 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 5898E1152
 for <freebsd-x11@FreeBSD.org>; Thu,  3 Sep 2015 19:51:09 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t83Jp9wV069374
 for <freebsd-x11@FreeBSD.org>; Thu, 3 Sep 2015 19:51:09 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-x11@FreeBSD.org
Subject: [Bug 202643] x11/xorg: illegal instruction starting xorg in FreeBSD
 10.2 in kvm/qemu virtulization
Date: Thu, 03 Sep 2015 19:51:09 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Ports & Packages
X-Bugzilla-Component: Individual Port(s)
X-Bugzilla-Version: Latest
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: dim@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-x11@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-202643-8047-xchRGfm4pt@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-202643-8047@https.bugs.freebsd.org/bugzilla/>
References: <bug-202643-8047@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-x11@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: X11 on FreeBSD -- maintaining and support <freebsd-x11.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-x11>,
 <mailto:freebsd-x11-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-x11/>
List-Post: <mailto:freebsd-x11@freebsd.org>
List-Help: <mailto:freebsd-x11-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-x11>,
 <mailto:freebsd-x11-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Sep 2015 19:51:09 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202643

--- Comment #18 from Dimitry Andric <dim@FreeBSD.org> ---
(In reply to nogcjx from comment #16)
> I can run FreeBSD 10.1 in the same KVM/qemu setup that fails when I try to
> run 10.2.  I install the VM with scripts, so the setup options are the same.
> Something changed, but what changed I don't know.  I am running virtualized
> 10.1 right now.

Maybe you were just lucky, as it *does* crash for me on FreeBSD 10.1-RELEASE. 
I started both 10.1-RELEASE and 10.2-RELEASE instances on KVM, installed all of
xorg with pkg (from the 'latest' pkg repo), and started /usr/local/bin/Xorg on
them.  Both crash with:

Program received signal SIGILL, Illegal instruction.
[Switching to Thread 803406400 (LWP 100054/Xorg)]
0x00000000004a40d0 in xf86SlowBcopy ()
(gdb) bt
#0  0x00000000004a40d0 in xf86SlowBcopy ()
#1  0x0000000802dd2b99 in VESASaveRestore () from
/usr/local/lib/xorg/modules/drivers/vesa_drv.so
#2  0x0000000802dd1e27 in VESAScreenInit () from
/usr/local/lib/xorg/modules/drivers/vesa_drv.so
#3  0x0000000000439ec0 in AddScreen ()
#4  0x000000000047e104 in InitOutput ()
#5  0x0000000000429056 in _start ()
#6  0x0000000000428d4f in _start ()
#7  0x0000000800814000 in ?? ()
#8  0x0000000000000000 in ?? ()

I'll see if it gives a little more information to rebuild these with debug
info.

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