From owner-freebsd-amd64@FreeBSD.ORG Mon Oct 8 17:00:12 2007 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 02E1216A468 for ; Mon, 8 Oct 2007 17:00:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id DE57013C4A7 for ; Mon, 8 Oct 2007 17:00:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.1/8.14.1) with ESMTP id l98H0Bod008162 for ; Mon, 8 Oct 2007 17:00:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.1/8.14.1/Submit) id l98H0Bb5008161; Mon, 8 Oct 2007 17:00:11 GMT (envelope-from gnats) Date: Mon, 8 Oct 2007 17:00:11 GMT Message-Id: <200710081700.l98H0Bb5008161@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Kostik Belousov Cc: Subject: Re: amd64/105514: FreeBSD/amd64 - Fails to boot on HP Pavilion dv8000 Laptop X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Kostik Belousov List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Oct 2007 17:00:12 -0000 The following reply was made to PR amd64/105514; it has been noted by GNATS. From: Kostik Belousov To: Scot Hetzel Cc: Remko Lodder , freebsd-amd64@freebsd.org, bug-followup@freebsd.org Subject: Re: amd64/105514: FreeBSD/amd64 - Fails to boot on HP Pavilion dv8000 Laptop Date: Mon, 8 Oct 2007 19:29:12 +0300 --MdJ3p2aQbVp3YFXz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Oct 06, 2007 at 02:38:59PM -0500, Scot Hetzel wrote: > On 9/24/07, Remko Lodder wrote: > > Does this occur with recent 7-CURRENT ISO images as well? > > Does this occur with other images then the AMD64 one? e.g. > > the I386 one? > >=20 > > Would it be possible for you to see what is going on there? > >=20 > I finally had a chance to retest, and so far FreeBSD is failing to boot w= ith the i386 ISO also. I have tested several versions: >=20 > 6.1-RELEASE-i386-bootonly.iso > 6.2-RELEASE-i386-disc1.iso > 7.0-20070928-SNAP-i386-bootonly.iso >=20 > And they all give me the same error: >=20 > corrupt symbol? > > /boot/kernel/acpi.ko text=3D0x53a80 data=3D0x23a0+0x184c syms=3D[0x4+0x85= 90+0x4+0xb030] > loading required module 'pci' > ACPI auto load failed - no such file or directory >=20 > int=3D00000006 err=3D00000000 efl=3D00010086 eip=3D00459b43 > eax=3D00459bc9 ebx=3D00459640 ecx=3Da0000075 edx=3D000488a0 > esi=3D00066254 edi=3D0005bf7c ebp=3D00094484 esp=3D0009e440 > cs=3D0008 ds=3D0010 es=3D0010 fs=3D0010 gs=3D0010 ss=3D0010 > cs:eip=3D f0 e8 57 ff ff ff 89 c2-83 f8 ff 75 d8 83 c7 34 > 81 ff e8 38 b8 c0 75 c3-8b 15 b8 0d bb c0 89 d0 > ss:esp=3D 40 9b 45 00 90 95 00 00-00 00 00 80 75 00 00 a0 > 00 00 00 00 00 00 00 00-00 00 00 00 a0 88 04 00 > BTX Halted >=20 > This was the output of the 7.0-20070928-SNAP-i386-bootonly CD. >=20 > I still get the crash with the FreeBSD/amd64 CD, but the output is unread= able due to it constantly scrolling on the screen. If I hold hold down the= space bar as detailed in the PR, it will boot into sysinstall (7.0-2007092= 8-SNAP-amd64-bootonly.iso) >=20 > I used the 7.0 SNAPs from: > http://snapshots.us.freebsd.org/snapshots/ I downloaded that image and looked what is located at the eip=3D00459b43 in the kernel image. Since low mapping + 0xc0000000 =3D virt mapping, we shall be at the 0xc0459b43. It appears that this is the following fragment of i386/i386/locore.s: movl %cr0,%eax /* get control word */ orl $CR0_PE|CR0_PG,%eax /* enable paging */ movl %eax,%cr0 /* and let's page NOW! */ ;;;; IT IS THERE pushl $begin /* jump to high virtualized address */ ret It faults immediately after enabling the paging. Instead of the pushl $begi= n, it points to the wrong opcode lock call something Might be, the initial page tables are corrupted somehow ? As a wild guess, might be A20 line is not turned on properly ? --MdJ3p2aQbVp3YFXz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHClrYC3+MBN1Mb4gRAmqHAJ4s8FGCnn2lBipZqLqKYGRqyerFHgCg3Log 7BtT/bE7a5s+qRlPAEheqqg= =koiD -----END PGP SIGNATURE----- --MdJ3p2aQbVp3YFXz--