Ken Smith writes: > > The alpha architecture reference machine in the cluster has been grumpy > about the -current kernel for the past two days. This is what we're > getting on the console: > > FreeBSD/alpha SRM disk boot, Revision 1.2 > (root_at_beast.freebsd.org, Mon Feb 23 07:07:25 PST 2004) > Memory: 2097152 k > Loading /boot/defaults/loader.conf > /boot/kernel/kernel data=0x34d3f0+0x3cb60 syms=[0x8+0x50580+0x8+0x40604] > > Hit [Enter] to boot immediately, or any other key for command prompt. > Booting [/boot/kernel/kernel]... > Entering /boot/kernel/kernel at 0xfffffc000033e3e0... > > halted CPU 0 > > halt code = 2 > kernel stack not valid halt > PC = 4 > boot failure > P00>>> > > If anyone has hints what the problem is or if anyone needs me to > do anything to help track it down let me know. It (beast) is back I'm guessing it followed a null function pointer. Maybe the recent device changes had some special affect on alpha. When it crashes, take a look at the return address. Its been a while, but I think its "e RA" at the P00>>> prompt. DrewReceived on Mon Feb 23 2004 - 12:43:53 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:44 UTC