Date: Wed, 28 Nov 2001 15:47:22 +0100 (MET) From: Martijn Pronk <martijn@smartie.xs4all.nl> To: alpha@freebsd.org Subject: Panic while booting -current on Alpha AXPpci33 Message-ID: <200111281447.fASEllC00667@obelix.smartie.xs4all.nl>
next in thread | raw e-mail | index | archive | help
Hi all, My -current Alpha machine (AXPpci33) panics while starting init it seems: <The rest of the kernel booting is snipped> da0 at sym0 bus 0 target 1 lun 0 da0: <SEAGATE ST12400N 8650> 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> <t0=0x0> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200111281447.fASEllC00667>