Re: [Testbed-admins] Can't bring up the first node

[Mike Hibler <mike@flux.utah.edu>]

This has happen to a couple of people now, and the time I tried to track
it down, it stopped happening.  The problem is that the code that asks the
BIOS for the memory map is not working (as indicated by the 0MB of RAM
available in the message below).

Just a couple of days ago, I built a 6.4 kernel based on the current 6.4
stable sources:

 http://www.emulab.net/downloads/kernel.GENERIC.6.4.gz

Download that into your /tftpboot/freebsd.newnode/boot directory,
unzip it, run "./prepare" and try again.  That way we can rule out any
bug that has already been fixed.

On Thu, Aug 06, 2009 at 01:39:26PM -0400, Espinola, Derek wrote:
> When pxe booting, it gets as far as:
> ....
> ...
> Real memory = 655360 ( 0MB )
> Avail memory = 1154688 ( 0MB )
> Panic : hashinit : bad elements
> Kdb : enter : panic
> [Threadpid 01 id 0 ]
> Stopped at kb_enter+0x2b :nop
> Db>
> 
> I checked the bootinfo.log
> 
> Aug  6 06:54:19 boss-nlet bootinfo[897]: iptonodeid: No such nodeid: 172.19.5.254
> Aug  6 06:54:19 boss-nlet bootinfo[897]: Unable to convert IP to nodeid for 172.19.5.254!
> Aug  6 06:54:19 boss-nlet bootinfo[897]: 172.19.5.254: nonexistent IP, booting 'emulab-ops,NEWNODE-MFS'
> Aug  6 06:54:19 boss-nlet bootinfo[897]: iptonodeid: No such nodeid: 172.19.5.254
> Aug  6 06:54:19 boss-nlet bootinfo[897]: Unable to convert IP to nodeid for 172.19.5.254!
> Aug  6 06:54:19 boss-nlet bootinfo[897]: 172.19.5.254: REPLY: boot from mfs /tftpboot/freebsd.newnode
> 
> Any suggestions?
> 
> Thanks,
> -Derek

> _______________________________________________
> Testbed-admins mailing list
> Testbed-admins@flux.utah.edu
> http://www.flux.utah.edu/mailman/listinfo/testbed-admins