AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080124112329.6e2a4df7@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<larry.scheer@onstor.com>,<vikas.saini@onstor.com>,<ken.renshaw@onstor.com>,<rick.lund@onstor.com>,<warren.gale@onstor.com>,<brian.stark@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	BB375AF679D4A34E9CA8DFA650E2B04E056C9306@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Thu, 24 Jan 2008 11:25:03 -0800
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Larry Scheer" <larry.scheer@onstor.com>
Cc: "Vikas Saini" <vikas.saini@onstor.com>, "Ken Renshaw"
 <ken.renshaw@onstor.com>, Rick Lund <rick.lund@onstor.com>, Warren Gale
 <warren.gale@onstor.com>, Brian Stark <brian.stark@onstor.com>
Subject: Re: Boot issues with g9r204 and g10r204
Message-ID: <20080124112503.409c9845@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E056C9306@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E056C9306@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

On Wed, 23 Jan 2008 20:09:34 -0800 "Larry Scheer"
<larry.scheer@onstor.com> wrote:

> Ken, Vikas,
>    Got the issue sorted out. The reason my system (g4r5) booted with
> the default (Ken's build) kernel configuration was because that
> system had a compact flash loaded with a release. When it booted it
> mounted the compact flash and is using the SSC daemons and Linux from
> the flash and not the NFS root.
> 
> Andy looked at this issue and determined this is a PROM bug. The PROM
> is not constructing the correct command line after boot. We should be
> able to build the kernel with the default boot command line (as it is
> currently checked into Perforce) and the PROM should create the
> correct boot arguments in the case of a network boot. 

This not necessarily a prom bug so much as a newly identified situation
with Linux that we might want to handle with some prom help.  It also
might be possible to sort this out by utilizing some dhcp
capabilities.  I'm looking into that but if someone has some time and
wants to also look into it, check out if we can specify boot options
with dhcp, similar to how we specify NFS root path and the like.  I
seem to recall there is a parameter for this.

> Andy has notified Rick Lund of the situation. We won't be changing the
> kernel source in perforce. So for the time being the work-around is to
> modify linux/kernel/linux-mips-2.6/cougar-config in your local
> workspace until the PROM is fixed.

I will change the kernel if that's the right way to go.  We are still
analyzing this and a few other situations and trying to figure out the
best way to handle all of them.  Feel free to send my opinions and
ideas.

Cheers,

a
