From owner-freebsd-xen@FreeBSD.ORG Tue Jan 12 07:58:16 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 B5873106566B for ; Tue, 12 Jan 2010 07:58:16 +0000 (UTC) (envelope-from bissont@gmail.com) Received: from mail-iw0-f177.google.com (mail-iw0-f177.google.com [209.85.223.177]) by mx1.freebsd.org (Postfix) with ESMTP id 7A20C8FC16 for ; Tue, 12 Jan 2010 07:58:16 +0000 (UTC) Received: by iwn7 with SMTP id 7so6989637iwn.7 for ; Mon, 11 Jan 2010 23:58:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to :content-type:content-transfer-encoding:mime-version:subject:date :x-mailer; bh=bOFhaYGZGU1vl/93hH8cGbq9fCZTjVA4XZQunEP94RY=; b=C6uFGScPXI5nyF9PsTMWC4PJONQJwi353WY7cigj9Cl6wQob2pC6GsO09+fUri2b5D g3cp6g0h9FKVYs8Cq30vkkBYh+2Vd0e2R9S7quVoCoTNeM9LKj/ohH2TsY7t7cVFiVQU yELdToax5nDzCHbiukc1oOmIYXDzXbAFboYUA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:content-type:content-transfer-encoding :mime-version:subject:date:x-mailer; b=jrAaweoaCgGuO7CoWYPkHNR0b4oTy7K9qw/kgfG0+sqPQuUNdKFdju1avFq91rm2CU F3A7sahJoM5xiqGlbFH4gBA9ZSGqo3qyqaFZOj/E4AHtFlqAkPtixj69hxVz65hqZAua VpI8sBOEj9eHKtIAnObKVgkdkk0lDyXnKiPFQ= Received: by 10.231.170.136 with SMTP id d8mr588491ibz.17.1263281763152; Mon, 11 Jan 2010 23:36:03 -0800 (PST) Received: from vshukla-lxp.hq.netapp.com (nat-198-95-226-230.netapp.com [198.95.226.230]) by mx.google.com with ESMTPS id 20sm5438863iwn.1.2010.01.11.23.36.01 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 11 Jan 2010 23:36:02 -0800 (PST) Message-Id: From: Timothy Bisson To: freebsd-xen@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Date: Mon, 11 Jan 2010 23:36:00 -0800 X-Mailer: Apple Mail (2.936) Subject: 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: Tue, 12 Jan 2010 07:58:16 -0000 Hi, I'm trying to run a FreeBSD 8/CURRENT hvm on XEN, but booting FreeBSD currently panics on a quad-core Operton 2352 box while booting from the iso (disabling ACPI doesn't help). However, I'm successful at running a FreeBSD 8/CURRENT hvm on XEN on a Intel Xeon Nehalem box. I tried booting the same installed disk image (from the Nehalem box) on the Operteron box, but that also resulted in a panic while booting. The CURRENT iso I'm using is from: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201001/FreeBSD-9.0-CURRENT-201001-amd64-bootonly.iso I'm using Xen-3.3.1 on both physical boxes, and a BSD 6 hvm works on both the Nehalem and Operton boxes... Here's the backtrace from the opteron box: kernel trap 9 with interrupts disabled Fatal trap 9: general protection fault while in kernel mode cpuid = 0; apic id = 00 instruction pointer = 0x20:0xffffffff80878193 stack pointer = 0x28:0xffffffff81044bb0 frame pointer = 0x28:0xffffffff81044bc0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = resume, IOPL = 0 current process = 0 () [thread pid 0 tid 0 ] Stopped at pmap_invalidate_cache_range+0x43: 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 I took a look through the bug database and didn't see any similar problem reports. Is it reasonable to file a bug report? Is there additional information that I should be reporting? Thanks, Tim