From owner-freebsd-stable@FreeBSD.ORG Thu Apr 9 18:51:14 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 02B1BAA9 for ; Thu, 9 Apr 2015 18:51:14 +0000 (UTC) Received: from athena.awarent.com (unknown [IPv6:2600:3c03::f03c:91ff:feae:fc92]) by mx1.freebsd.org (Postfix) with ESMTP id D26646B6 for ; Thu, 9 Apr 2015 18:51:13 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by athena.awarent.com (Postfix) with ESMTP id AFF84231272 for ; Thu, 9 Apr 2015 14:51:07 -0400 (EDT) Received: from athena.awarent.com ([127.0.0.1]) by localhost (athena.awarent.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ui9SFfyxlfFZ for ; Thu, 9 Apr 2015 14:51:06 -0400 (EDT) Message-ID: <5526CA1A.9090403@gundogan.us> Date: Thu, 09 Apr 2015 14:51:06 -0400 From: Emre Gundogan MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: X server crash in 10-1-RELEASE-p9 (kvm guest) with syscons Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Apr 2015 18:51:14 -0000 [Sorry for the previous unintended test message I sent to the list]. Hi. I had a bizarre X server crash after updating the packages on my KVM guest running 10.1-RELEASE-p9 (Debian-8 host). X server with VESA driver crashes with signal 4 (illegal instruction) when console is set to 'sc' but not when it is 'vt'. After some tests, I've isolated this to be related to QEMU, as same config VirtualBox instance runs updated xorg/driver packages fine. I also tested it on a laptop with Nvidia driver, and no problems there, too. The simple fix for me to get my KVM instance back up and running XFCE4 was to set 'kern.vty=vt' in boot loader conf. Although my problem is fixed, I am curious why the Xorg update to 7.7_2 may exhibit such behavior in KVM. Thank you, Emre.