Date: Tue, 12 Jan 2010 11:36:28 +0200 From: Kostik Belousov <kostikbel@gmail.com> To: Timothy Bisson <bissont@gmail.com> Cc: freebsd-xen@freebsd.org Subject: Re: Can't boot 8/CURRENT hvm on Quad-Core Opteron 2352 Message-ID: <20100112093628.GH62907@deviant.kiev.zoral.com.ua> In-Reply-To: <BE5A8730-B0EA-4CE8-8C2F-B3DC7A5899EA@gmail.com> References: <BE5A8730-B0EA-4CE8-8C2F-B3DC7A5899EA@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--svZFHVx8/dhPCe52 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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-20= 1001-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? Set hw.clflush_disable=3D1 at the loader prompt. --svZFHVx8/dhPCe52 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAktMQpwACgkQC3+MBN1Mb4iwMQCfRsZmlC967tgmtAyRSvJtuQvu oMgAoLCRYGrnHH0WnHPKeD2eBdG4E06Q =aV2X -----END PGP SIGNATURE----- --svZFHVx8/dhPCe52--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100112093628.GH62907>