From owner-freebsd-alpha Wed Nov 28 13:11:25 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from smartie.xs4all.nl (smartie.xs4all.nl [213.84.1.157]) by hub.freebsd.org (Postfix) with ESMTP id D234637B417 for ; Wed, 28 Nov 2001 13:11:10 -0800 (PST) Received: from pluto (pluto.smartie.xs4all.nl [192.168.10.66]) by obelix.smartie.xs4all.nl (8.11.6/8.11.6) with SMTP id fASEllC00667 for ; Wed, 28 Nov 2001 15:47:47 +0100 (CET) (envelope-from martijn@obelix.smartie.xs4all.nl) Message-Id: <200111281447.fASEllC00667@obelix.smartie.xs4all.nl> Date: Wed, 28 Nov 2001 15:47:22 +0100 (MET) From: Martijn Pronk Reply-To: Martijn Pronk Subject: Panic while booting -current on Alpha AXPpci33 To: alpha@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: E/BTLDrgnm+uDRFqpBA2GQ== X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4 SunOS 5.8 sun4m sparc Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi all, My -current Alpha machine (AXPpci33) panics while starting init it seems: da0 at sym0 bus 0 target 1 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da0: 2048MB (4194685 512 byte sectors: 255H 63S/T 261C) Mounting root from ufs:/dev/da0a fatal kernel trap: trap entry = 0x2 (memory management fault) faulting va = 0x28 type = access violation cause = load instructon pc = 0xfffffc00004f8260 ra = 0xfffffc000050082c sp = 0xfffffe00047f7c80 usp = 0x11fffca0 curproc = 0xfffffe00047e9840 pid = 1, comm = init Stopped at alpha_fpstate_check+0x20: ldq t0,0x28(t0) <0x28> db> if I do a trace I see: db> trace alpha_fpstate_check() at alpha_fpstate_check+0x20 syscall() at syscall+0xec XentSys() at XentSys+0x64 --- syscall (24, FreeBSD ELF, getuid) --- --- user mode --- This is a -current cvsupped yesterday (november 27) I have a kernel laying around which is a month old that doesn't have this problem. Can someone help me with this? Thanks, Martijn PS: I discovered that kldload always uses /boot/kernel as location for modules, which can a bit problematic when you boot a kernel from /boot/kernel.good/ ... Maybe it's an idea to have kldload look at the directory where the current kernel is located to find modules To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message