On Mon, 23 Feb 2004, Ken Smith wrote: > > 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 > up and running a 3-day old kernel. The other two ref machines in > the cluster (amd64/sparc64) don't seem to be suffering from whatever > this problem is, their daily rebuild/reboot cron jobs have been > working fine. same problem here, on a ds10. I initially blamed it one ule, but it seems to be something else introduced a few days ago. -- Sten Spans "There is a crack in everything, that's how the light gets in." Leonard Cohen - AnthemReceived on Mon Feb 23 2004 - 12:12:31 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:44 UTC