Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 27 Jun 2012 09:41:42 +0900 (JST)
From:      Hiroki Sato <hrs@FreeBSD.org>
To:        mike@wizardlike.ca
Cc:        freebsd-ia64@FreeBSD.org
Subject:   Re: Installing on zx6000
Message-ID:  <20120627.094142.1522794524525361446.hrs@allbsd.org>
In-Reply-To: <4FE4EB9F.6070307@wizardlike.ca>
References:  <20120622103426.GA98040@mech-cluster241.men.bris.ac.uk> <CAA9xbM7h8b68%2B8rvu6wcXQgt3310knQ4XjR7r8NdF%2BSh7aOzrw@mail.gmail.com> <4FE4EB9F.6070307@wizardlike.ca>

next in thread | previous in thread | raw e-mail | index | archive | help
----Security_Multipart(Wed_Jun_27_09_41_42_2012_178)--
Content-Type: Text/Plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Mike Burrell <mike@wizardlike.ca> wrote
  in <4FE4EB9F.6070307@wizardlike.ca>:

mi> On 12-06-22 02:59 PM, =C9meric Maschino wrote:
mi> > Hi,
mi> > =

mi> > Same problem here. I didn't get an answer when reported back in M=
ay
mi> > (http://lists.freebsd.org/pipermail/freebsd-ia64/2012-May/003236.=
html).
mi> > My zx6000 has the latest firmware. From what I understand, this i=
ssue
mi> > is specific to Madison CPUs.
mi> =

mi> It's not clear to me whether this is the same issue (or whether the=

mi> thinks you linked to are all the same issue), though it definitely =
could
mi> be. In the post I made in January I mentioned that I'd successfully=

mi> installed other things (specifically Debian and HP-UX) without any
mi> problems at all, so I'm inclined to believe this is a problem with
mi> either FreeBSD's GENERIC kernel or FreeBSD's EFI loader.
mi> =

mi> Mostly my frustration at this point is trying to determine whether =
this
mi> is a known issue or not.
mi> =

mi> I guess I'll have to live with Debian for a while....

 Can you try to reset the EFI configuration to the factory default?
 After installing non-FreeBSD OSs such as HP-UX or Linux, some
 configurations which prevent FreeBSD from working may be added.

 I am using a zx6000 with the following CPUs for a long time:

 CPU 0 present and active
  Vendor  =3D "GenuineIntel"
  Serial# =3D 0002eaeb35795acf
  Version =3D 0x001f010504 (B1 Madison)
 CPU 1 present and active
  Vendor  =3D "GenuineIntel"
  Serial# =3D 0002be5b6e50a43b
  Version =3D 0x001f010504 (B1 Madison)

 I experienced a similar boot failure on a new box where Linux was
 installed long time ago.  At that time resetting all of EFI
 configuration to the factory default solved the issue.  A boot log of
 a running box is something like this:

----
 Entering /boot/kernel/kernel at 0xe000000004090000...
 GDB: debug ports: uart
 GDB: current port: uart
 KDB: debugger backends: ddb gdb
 KDB: current backend: ddb
 Copyright (c) 1992-2011 The FreeBSD Project.
 Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 19=
94
        The Regents of the University of California. All rights reserve=
d.
 FreeBSD is a registered trademark of The FreeBSD Foundation.
 FreeBSD 8.2-STABLE #0: Mon Aug  8 03:42:11 JST 2011
     hrs@ref-ia64-fbsd.allbsd.org:/usr/obj/usr/src/sys/IA64 ia64
 CPU: Madison (1500 Mhz Itanium 2)
   Origin =3D "GenuineIntel"  Revision =3D 5
   Features =3D 0x1<LB>
 real memory  =3D 25748930560 (24556 MB)
 avail memory =3D 25236807680 (24067 MB)
 FPSWA Revision =3D 0x10012, Entry =3D 0xe0000040ffe62050
 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
----

-- Hiroki

----Security_Multipart(Wed_Jun_27_09_41_42_2012_178)--
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (FreeBSD)

iEUEABECAAYFAk/qVsYACgkQTyzT2CeTzy3qyACeKLyE5NkoxE0+NT5DtqEzbXEO
2t8AmLlW/DSmfiMB3pOBy+bANYseEGQ=
=GPkY
-----END PGP SIGNATURE-----

----Security_Multipart(Wed_Jun_27_09_41_42_2012_178)----



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120627.094142.1522794524525361446.hrs>