From owner-freebsd-xen@FreeBSD.ORG Wed Jan 13 03:53:37 2010 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E3CC01065670 for ; Wed, 13 Jan 2010 03:53:36 +0000 (UTC) (envelope-from bissont@gmail.com) Received: from mail-qy0-f174.google.com (mail-qy0-f174.google.com [209.85.221.174]) by mx1.freebsd.org (Postfix) with ESMTP id 964768FC13 for ; Wed, 13 Jan 2010 03:53:36 +0000 (UTC) Received: by qyk4 with SMTP id 4so10500043qyk.7 for ; Tue, 12 Jan 2010 19:53:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=sRKTTOFOnP3OIx7TF7RDwbKjdWmpBVEy/tfKdzO6Www=; b=TD3ubH/7NPRK8LRCtkIqpnDFTuxzw97LJzwVhymEDLeVG3si1kT/2Q4qJmQv8y1S1M arQUc5yMtIzMCoU3OSWKGX6I2iqJbjwtk6Ep196nn85HcRqCu174Eu1/u/ePRxl47yNz JQWv/U1cn0ii94toIWbbPkIPI6kjDOKEa9dN0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=PkScxUted9Mm70h6l0WnTidRkUMp3iAw6Lys+17kRwWetvQV+wym/XfjaTSaPuOXdg hXXLlG0k5+g6OKfa7ccx4FzqM+Xw6Wq8HVLHKft+tt8MK8pO+C4f5Bs/oeET88/WC2ke T05A3mX/YXr2kFZVFunAEH0rETQ73vEnlSZNM= Received: by 10.224.96.70 with SMTP id g6mr18248628qan.247.1263354809022; Tue, 12 Jan 2010 19:53:29 -0800 (PST) Received: from chow3-lxp.hq.netapp.com (nat-198-95-226-231.netapp.com [198.95.226.231]) by mx.google.com with ESMTPS id 21sm6062743qyk.0.2010.01.12.19.53.26 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 12 Jan 2010 19:53:27 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=us-ascii From: Tim Bisson In-Reply-To: <20100112093628.GH62907@deviant.kiev.zoral.com.ua> Date: Tue, 12 Jan 2010 19:53:25 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20100112093628.GH62907@deviant.kiev.zoral.com.ua> To: Kostik Belousov X-Mailer: Apple Mail (2.1077) Cc: freebsd-xen@freebsd.org Subject: Re: Can't boot 8/CURRENT hvm on Quad-Core Opteron 2352 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jan 2010 03:53:37 -0000 On Jan 12, 2010, at 1:36 AM, Kostik Belousov wrote: > On Mon, Jan 11, 2010 at 11:36:00PM -0800, Timothy Bisson wrote: >> Hi, >>=20 >> I'm trying to run a FreeBSD 8/CURRENT hvm on XEN, but booting FreeBSD = =20 >> currently panics on a quad-core Operton 2352 box while booting from =20= >> the iso (disabling ACPI doesn't help). >>=20 >> However, I'm successful at running a FreeBSD 8/CURRENT hvm on XEN on = a =20 >> Intel Xeon Nehalem box. I tried booting the same installed disk image = =20 >> (from the Nehalem box) on the Operteron box, but that also resulted = in =20 >> a panic while booting. >>=20 >> The CURRENT iso I'm using is from: >> = ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201001/FreeBSD-9.0-CURRENT-201= 001-amd64-bootonly.iso >>=20 >> I'm using Xen-3.3.1 on both physical boxes, and a BSD 6 hvm works on =20= >> both the Nehalem and Operton boxes... >>=20 >> Here's the backtrace from the opteron box: >> kernel trap 9 with interrupts disabled >>=20 >>=20 >> Fatal trap 9: general protection fault while in kernel mode >> cpuid =3D 0; apic id =3D 00 >> instruction pointer =3D 0x20:0xffffffff80878193 >> stack pointer =3D 0x28:0xffffffff81044bb0 >> frame pointer =3D 0x28:0xffffffff81044bc0 >> code segment =3D base 0x0, limit 0xfffff, type 0x1b >> =3D DPL 0, pres 1, long 1, def32 0, gran 1 >> processor eflags =3D resume, IOPL =3D 0 >> current process =3D 0 () >> [thread pid 0 tid 0 ] >> Stopped at pmap_invalidate_cache_range+0x43: =20 >> clflushl (%rdi) >> db> bt >> bt >> Tracing pid 0 tid 0 td 0xffffffff80c51fc0 >> pmap_invalidate_cache_range() at pmap_invalidate_cache_range+0x43 >> pmap_change_attr_locked() at pmap_change_attr_locked+0x368 >> pmap_change_attr() at pmap_change_attr+0x43 >> pmap_mapdev_attr() at pmap_mapdev_attr+0x112 >> lapic_init() at lapic_init+0x29 >> madt_setup_local() at madt_setup_local+0x26 >> apic_setup_local() at apic_setup_local+0x13 >> mi_startup() at mi_startup+0x59 >> btext() at btext+0x2c >>=20 >>=20 >> I took a look through the bug database and didn't see any similar =20 >> problem reports. Is it reasonable to file a bug report? Is there =20 >> additional information that I should be reporting? >=20 > Set hw.clflush_disable=3D1 at the loader prompt. Thank you. I should have read the Release Notes...=