AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20070413195745.7d417ab0@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<larry.scheer@onstor.com>,<tim.gardner@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E02215735@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Fri, 13 Apr 2007 19:58:39 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Larry Scheer" <larry.scheer@onstor.com>
Cc: "Tim Gardner" <tim.gardner@onstor.com>
Subject: Re: Bobcat linux kernel won't start
Message-ID: <20070413195839.42c6e168@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E02215735@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E02215735@onstor-exch02.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

One thing you can do is boot the kernel on my tftp server.  It will
have the wrong IP addresses bit it should still boot until it conflicts
with the IP address of my bobcat and brings down the whole lab network.
But at least it should boot.  Is there anything "special" about your
bobcat that we should know about?  Are you sure you're loading the
kernel I gave you and not one of Dan's old kernels?  Etc.

Have a cheerie weekend,

a

On Fri, 13 Apr 2007 18:00:23 -0700 "Larry Scheer"
<larry.scheer@onstor.com> wrote:

> Hey Andy,
>    I am making some progress. I used seep to set the IP address on my
> filer and I can load the kernel but I get this exception when it tries
> to start 
> 
> 		SSC-PROM> load -a 83000000 10.2.0.4 vmlinux-bc
> 		load, ip addr = 0xa020004, fname = vmlinux-bc
> 		loading vmlinux-bc from 0xa020004 at 0x83000000
> 		tpl_findBindCb prot=17 lport=9736
> 		tpl_allocBindCb
> 		tftp_tplAddConnInd
> 		TFTP transfer completed.
> 		tftp_tplDelConnInd
> 		binary load, 3593552 bytes (0x36d550)
> 		SSC-PROM> g
> 		env[0] = 80385be8:.cpuclock=799988250.
> 		env[1] = 80385c38:.memsize=512.
> 		env[2] = 80385c88:.osloadoptions=mAt.
> 		env[3] = 80385cd8:.boot=cold.
> 		env[4] = 80385d28:.busclock=133.
> 		env[5] = 80385d78:.ipaddr=10.2.11.4.
> 		env[6] = 80385dc8:.netmask=255.255.0.0.
> 		env[7] = 80385e18:.macaddr0=.00:07:34:02:d8:00.
> 		env[8] = 80385e68:.macaddr1=.00:07:34:02:d8:01.
> 		env[9] = 80385eb8:.bootdev=/dev/wd0a.
> 
> 		PMON AdEL exception
> 		EPC:      0x83060a88
> 		RA:       0x83060fb0
> 		Cause:    00808010
> 		BadVaddr: 0x46ce0d9c
> 		Autoreboot set "off", stopping in debug mode
> 		DEBUG-PROM-SSC:8 >
> 
> 
> Is there anything I need to adjust in my prom environment? Here is
> what I have:
> 
> 		Current Environment Settings:
> 		        autoload     = on         ( off on )
> 		        autoreboot   = off        ( off on )
> 		        load_src     = disk       ( disk network )
> 		        load_opts    = mAt        ( m/s|A/a|d|t )
> 		        boot_dev     = wd0a       ( wd0a wd1a sc1 )
> 		        upgrade_prom = yes        ( no yes )
> 		        env_reset    = no         ( no yes )
> 		        autolinkenable = 3          ( 0 1 2 3 )
> 		        hw_qt        = off        ( off on )
> 		        hw_ft        = off        ( off on )
> 		        hw_diag      = off        ( off on )
