X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C8700A.366A961E@onstor-exch02.onstor.net>; Fri, 15 Feb 2008 12:37:34 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8700A.366A961E"
References: <BB375AF679D4A34E9CA8DFA650E2B04E0856E52F@onstor-exch02.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E05C7424C@onstor-exch02.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E0856E634@onstor-exch02.onstor.net> <20080214145022.4c95aa7e@ripper.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E0856E6BC@onstor-exch02.onstor.net>
Content-class: urn:content-classes:message
Subject: RE: Status of today's build.
Date: Fri, 15 Feb 2008 12:37:34 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E07797B97@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Status of today's build.
Thread-Index: AchvW/w/DoOAS661TTmeYZI7pMoXigAAC4OQACs5aVg=
From: "Ken Renshaw" <ken.renshaw@onstor.com>
To: "Brian Stark" <brian.stark@onstor.com>,
	"Andy Sharp" <andy.sharp@onstor.com>,
	"Warren Gale" <warren.gale@onstor.com>
Cc: "Sandrine Boulanger" <sandrine.boulanger@onstor.com>,
	"Larry Scheer" <larry.scheer@onstor.com>,
	"Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>,
	"dl-Cougar" <dl-Cougar@onstor.com>,
	"Jobi Ariyamannil" <jobi.ariyamannil@onstor.com>,
	"Vikas Saini" <vikas.saini@onstor.com>,
	"Paul Hammer" <paul.hammer@onstor.com>,
	"Ed Kwan" <ed.kwan@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8700A.366A961E
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Actually, in the past most all the released PROM images for bobcats and =
cheetahs have come out of Build. The PROM release forms going into Agile =
used to be the trigger to build and checkin the new PROM versions to the =
nfx-tree for inclusion. The master flashes for the filers pick them up =
from there, but I'm not sure where the hexfiles come from that burn the =
PROMs during production of the boards.

Thanks,

-Ken

-----Original Message-----
From: Brian Stark
Sent: Thu 2/14/2008 3:06 PM
To: Andy Sharp; Warren Gale
Cc: Sandrine Boulanger; Larry Scheer; Maxim Kozlovsky; dl-Cougar; Jobi =
Ariyamannil; Vikas Saini; Ken Renshaw; Paul Hammer; Ed Kwan
Subject: RE: Status of today's build.
=20
This is exactly why I've said that PROMs should only come from PROM =
developers, and once an official release is made, it's attached into =
Agile Software, which is the database used by Hardware and Ops. =20
=20

> -----Original Message-----
> From: Andy Sharp=20
> Sent: Thursday, February 14, 2008 2:50 PM
> To: Warren Gale
> Cc: Sandrine Boulanger; Larry Scheer; Maxim Kozlovsky;=20
> dl-Cougar; Jobi Ariyamannil; Vikas Saini; Ken Renshaw; Paul=20
> Hammer; Ed Kwan
> Subject: Re: Status of today's build.
>=20
> I'm sorry, but Sandrine is completely correct, there never=20
> should have been two different 1.0.3 proms.  That was a no-no.
>=20
> On Thu, 14 Feb 2008 14:10:36 -0800 "Warren Gale"
> <warren.gale@onstor.com> wrote:
>=20
> > Since the PROMs have moved under the dev tree, any developer could=20
> > make their own proms which would have the current=20
> "tree-name" inserted=20
> > in the version string. With Wiki page build and upgrade=20
> instructions,=20
> > anyone could have done an update with a non-released version.
> > Notes were kept by Rick based on Change List numbers, which I am=20
> > looking for at this point.
> > As far as I know there was pro-active work done to update=20
> all QA and=20
> > dev systems.
> >=20
> > _____________________________________________
> > From: Sandrine Boulanger
> > Sent: Thursday, February 14, 2008 1:43 PM
> > To: Warren Gale; Larry Scheer; Maxim Kozlovsky; dl-Cougar
> > Cc: Jobi Ariyamannil; Vikas Saini; Ken Renshaw; Paul Hammer; Ed Kwan
> > Subject: RE: Status of today's build.
> >=20
> > Also, how come there would be multiple versions of 1.0.3 proms, and=20
> > why there is no pro-active update when new proms are=20
> available, along=20
> > with some notes that explain what has changed?
> >=20
> > _____________________________________________
> > From: Warren Gale
> > Sent: Thursday, February 14, 2008 11:58 AM
> > To: Larry Scheer; Maxim Kozlovsky; dl-Cougar
> > Cc: Jobi Ariyamannil; Sandrine Boulanger; Vikas Saini; Ken Renshaw;=20
> > Paul Hammer; Ed Kwan
> > Subject: RE: Status of today's build.
> >=20
> > Ok, at this point we need to have physical consoles=20
> attached to TXRX ,=20
> > FP, and SSC, to be able to do the upgrade.
> >=20
> > _____________________________________________
> > From: Larry Scheer
> > Sent: Thursday, February 14, 2008 11:44 AM
> > To: Maxim Kozlovsky; dl-Cougar
> > Cc: Jobi Ariyamannil; Sandrine Boulanger; Vikas Saini; Ken Renshaw;=20
> > Paul Hammer; Ed Kwan
> > Subject: RE: Status of today's build.
> >=20
> > Yes indeed! My answer was right there in my email. Notice=20
> the the TXRX=20
> > prompt : "DEBUG-TXRX0:0 >" The TXRX is crashed!
> >=20
> > To be redundant... I need new PROM images!
> >=20
> > _____________________________________________
> > From: Maxim Kozlovsky
> > Sent: Thursday, February 14, 2008 11:40 AM
> > To: Larry Scheer; dl-Cougar
> > Cc: Jobi Ariyamannil; Sandrine Boulanger; Vikas Saini; Ken Renshaw;=20
> > Paul Hammer; Ed Kwan
> > Subject: RE: Status of today's build.
> >=20
> > Actually that problem with the optimized build was not fixed until=20
> > January 17, so your prom can not be right.
> >=20
> > _____________________________________________
> > From: Larry Scheer
> > Sent: Thursday, February 14, 2008 11:30 AM
> > To: Larry Scheer; Maxim Kozlovsky; dl-Cougar
> > Cc: Jobi Ariyamannil; Sandrine Boulanger; Vikas Saini; Ken Renshaw;=20
> > Paul Hammer; Ed Kwan
> > Subject: RE: Status of today's build.
> >=20
> > I'm talking to Warren. He pointed out that I need to look=20
> at the TXRX=20
> > and FP PROM. Here is the versions from the other processors:
> >=20
> > FP0:1 > ver
> > ver
> >=20
> > NFP_FP : R4.0.0.DEV-CG-021308 : Wed Feb 13 23:47:44 2008=20
> > PROM_SIBYTE_CG : Cougar-prom-1.0.3 : Thu Dec 20 11:25:51 2007
> >=20
> > DEBUG-TXRX0:0 > ver
> > ver
> >=20
> > NFP_TXRX : R4.0.0.DEV-CG-021308 : Wed Feb 13 23:51:17 2008=20
> > PROM_SIBYTE_CG : Cougar-prom-1.0.3 : Thu Dec 20 11:25:51 2007
> >=20
> > Warren says he thinks I am ok, even though it is not the=20
> latest 1.0.3.
> >=20
> > _____________________________________________
> > From: Larry Scheer
> > Sent: Thursday, February 14, 2008 11:17 AM
> > To: Maxim Kozlovsky; dl-Cougar
> > Cc: Jobi Ariyamannil; Sandrine Boulanger; Vikas Saini; Ken Renshaw;=20
> > Paul Hammer; Ed Kwan
> > Subject: RE: Status of today's build.
> >=20
> > Yes, I do. At least this was the last release that Brian S.=20
> said was=20
> > "official."
> >=20
> > SSC-PROM> ver
> >=20
> > PROM_SIBYTE_CG : Cougar-prom-1.0.3 : Thu Jan 17 15:57:20 2008
> >=20
> > _____________________________________________
> > From: Maxim Kozlovsky
> > Sent: Thursday, February 14, 2008 10:34 AM
> > To: Larry Scheer; dl-Cougar
> > Cc: Jobi Ariyamannil; Sandrine Boulanger; Vikas Saini; Ken Renshaw;=20
> > Paul Hammer; Ed Kwan
> > Subject: RE: Status of today's build.
> >=20
> > Hello,
> >=20
> > Did you have the latest prom (1.3) when trying to run the optimized=20
> > build? The txrx will crash if optimized build is run with=20
> the earlier=20
> > prom releases.
> >=20
> > Max
> >=20
> > _____________________________________________
> > From: Larry Scheer
> > Sent: Wednesday, February 13, 2008 10:43 PM
> > To: dl-Cougar
> > Cc: Jobi Ariyamannil; Sandrine Boulanger; Vikas Saini; Ken Renshaw;=20
> > Paul Hammer; Ed Kwan
> > Subject: Status of today's build.
> >=20
> > Today we scrambled around to fix a problem with the SCSI=20
> message code=20
> > that manifested in problems with LUN label, volume create,=20
> etc. Change
> > 27822 fixed the problem; at least it appears that way with=20
> the debug=20
> > builds on both bobcat BSD and cougar systems.
> >=20
> > Jonathan checked in his changes this afternoon (27831) and=20
> there was=20
> > some question tonight whether everything still worked. I built from=20
> > the top of the tree (27835) and tested the debug build and=20
> everything=20
> > appears to be working with the debug build, both cougar and bobcat=20
> > BSD.
> >=20
> > However the cougar opt build from the top of the tree is=20
> not working.
> > I am seeing deadbeef messages in the console.
> > I also saw this when the opt build was booted from compact flash:
> >=20
> > Starting ONStor initial configuration utility:.
> > Setting up networking....
> > Configuring network interfaces...SIOCADDRT: Network is unreachable
> > run-parts: /etc/network/if-up.d/addroutes exited with return code 7
> > SIOCADDRT: File exists
> > run-parts: /etc/network/if-up.d/addroutes exited with return code 7=20
> > done.
> >=20
> > Just wanted to give everyone a status and answer some=20
> questions about=20
> > what works and what doesn't.
> >=20
> > Larry
> >=20
>=20

------_=_NextPart_001_01C8700A.366A961E
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7653.38">
<TITLE>RE: Status of today's build.</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Actually, in the past most all the released PROM =
images for bobcats and cheetahs have come out of Build. The PROM release =
forms going into Agile used to be the trigger to build and checkin the =
new PROM versions to the nfx-tree for inclusion. The master flashes for =
the filers pick them up from there, but I'm not sure where the hexfiles =
come from that burn the PROMs during production of the boards.<BR>
<BR>
Thanks,<BR>
<BR>
-Ken<BR>
<BR>
-----Original Message-----<BR>
From: Brian Stark<BR>
Sent: Thu 2/14/2008 3:06 PM<BR>
To: Andy Sharp; Warren Gale<BR>
Cc: Sandrine Boulanger; Larry Scheer; Maxim Kozlovsky; dl-Cougar; Jobi =
Ariyamannil; Vikas Saini; Ken Renshaw; Paul Hammer; Ed Kwan<BR>
Subject: RE: Status of today's build.<BR>
<BR>
This is exactly why I've said that PROMs should only come from PROM =
developers, and once an official release is made, it's attached into =
Agile Software, which is the database used by Hardware and =
Ops.&nbsp;<BR>
<BR>
<BR>
&gt; -----Original Message-----<BR>
&gt; From: Andy Sharp<BR>
&gt; Sent: Thursday, February 14, 2008 2:50 PM<BR>
&gt; To: Warren Gale<BR>
&gt; Cc: Sandrine Boulanger; Larry Scheer; Maxim Kozlovsky;<BR>
&gt; dl-Cougar; Jobi Ariyamannil; Vikas Saini; Ken Renshaw; Paul<BR>
&gt; Hammer; Ed Kwan<BR>
&gt; Subject: Re: Status of today's build.<BR>
&gt;<BR>
&gt; I'm sorry, but Sandrine is completely correct, there never<BR>
&gt; should have been two different 1.0.3 proms.&nbsp; That was a =
no-no.<BR>
&gt;<BR>
&gt; On Thu, 14 Feb 2008 14:10:36 -0800 &quot;Warren Gale&quot;<BR>
&gt; &lt;warren.gale@onstor.com&gt; wrote:<BR>
&gt;<BR>
&gt; &gt; Since the PROMs have moved under the dev tree, any developer =
could<BR>
&gt; &gt; make their own proms which would have the current<BR>
&gt; &quot;tree-name&quot; inserted<BR>
&gt; &gt; in the version string. With Wiki page build and upgrade<BR>
&gt; instructions,<BR>
&gt; &gt; anyone could have done an update with a non-released =
version.<BR>
&gt; &gt; Notes were kept by Rick based on Change List numbers, which I =
am<BR>
&gt; &gt; looking for at this point.<BR>
&gt; &gt; As far as I know there was pro-active work done to update<BR>
&gt; all QA and<BR>
&gt; &gt; dev systems.<BR>
&gt; &gt;<BR>
&gt; &gt; _____________________________________________<BR>
&gt; &gt; From: Sandrine Boulanger<BR>
&gt; &gt; Sent: Thursday, February 14, 2008 1:43 PM<BR>
&gt; &gt; To: Warren Gale; Larry Scheer; Maxim Kozlovsky; dl-Cougar<BR>
&gt; &gt; Cc: Jobi Ariyamannil; Vikas Saini; Ken Renshaw; Paul Hammer; =
Ed Kwan<BR>
&gt; &gt; Subject: RE: Status of today's build.<BR>
&gt; &gt;<BR>
&gt; &gt; Also, how come there would be multiple versions of 1.0.3 =
proms, and<BR>
&gt; &gt; why there is no pro-active update when new proms are<BR>
&gt; available, along<BR>
&gt; &gt; with some notes that explain what has changed?<BR>
&gt; &gt;<BR>
&gt; &gt; _____________________________________________<BR>
&gt; &gt; From: Warren Gale<BR>
&gt; &gt; Sent: Thursday, February 14, 2008 11:58 AM<BR>
&gt; &gt; To: Larry Scheer; Maxim Kozlovsky; dl-Cougar<BR>
&gt; &gt; Cc: Jobi Ariyamannil; Sandrine Boulanger; Vikas Saini; Ken =
Renshaw;<BR>
&gt; &gt; Paul Hammer; Ed Kwan<BR>
&gt; &gt; Subject: RE: Status of today's build.<BR>
&gt; &gt;<BR>
&gt; &gt; Ok, at this point we need to have physical consoles<BR>
&gt; attached to TXRX ,<BR>
&gt; &gt; FP, and SSC, to be able to do the upgrade.<BR>
&gt; &gt;<BR>
&gt; &gt; _____________________________________________<BR>
&gt; &gt; From: Larry Scheer<BR>
&gt; &gt; Sent: Thursday, February 14, 2008 11:44 AM<BR>
&gt; &gt; To: Maxim Kozlovsky; dl-Cougar<BR>
&gt; &gt; Cc: Jobi Ariyamannil; Sandrine Boulanger; Vikas Saini; Ken =
Renshaw;<BR>
&gt; &gt; Paul Hammer; Ed Kwan<BR>
&gt; &gt; Subject: RE: Status of today's build.<BR>
&gt; &gt;<BR>
&gt; &gt; Yes indeed! My answer was right there in my email. Notice<BR>
&gt; the the TXRX<BR>
&gt; &gt; prompt : &quot;DEBUG-TXRX0:0 &gt;&quot; The TXRX is =
crashed!<BR>
&gt; &gt;<BR>
&gt; &gt; To be redundant... I need new PROM images!<BR>
&gt; &gt;<BR>
&gt; &gt; _____________________________________________<BR>
&gt; &gt; From: Maxim Kozlovsky<BR>
&gt; &gt; Sent: Thursday, February 14, 2008 11:40 AM<BR>
&gt; &gt; To: Larry Scheer; dl-Cougar<BR>
&gt; &gt; Cc: Jobi Ariyamannil; Sandrine Boulanger; Vikas Saini; Ken =
Renshaw;<BR>
&gt; &gt; Paul Hammer; Ed Kwan<BR>
&gt; &gt; Subject: RE: Status of today's build.<BR>
&gt; &gt;<BR>
&gt; &gt; Actually that problem with the optimized build was not fixed =
until<BR>
&gt; &gt; January 17, so your prom can not be right.<BR>
&gt; &gt;<BR>
&gt; &gt; _____________________________________________<BR>
&gt; &gt; From: Larry Scheer<BR>
&gt; &gt; Sent: Thursday, February 14, 2008 11:30 AM<BR>
&gt; &gt; To: Larry Scheer; Maxim Kozlovsky; dl-Cougar<BR>
&gt; &gt; Cc: Jobi Ariyamannil; Sandrine Boulanger; Vikas Saini; Ken =
Renshaw;<BR>
&gt; &gt; Paul Hammer; Ed Kwan<BR>
&gt; &gt; Subject: RE: Status of today's build.<BR>
&gt; &gt;<BR>
&gt; &gt; I'm talking to Warren. He pointed out that I need to look<BR>
&gt; at the TXRX<BR>
&gt; &gt; and FP PROM. Here is the versions from the other =
processors:<BR>
&gt; &gt;<BR>
&gt; &gt; FP0:1 &gt; ver<BR>
&gt; &gt; ver<BR>
&gt; &gt;<BR>
&gt; &gt; NFP_FP : R4.0.0.DEV-CG-021308 : Wed Feb 13 23:47:44 2008<BR>
&gt; &gt; PROM_SIBYTE_CG : Cougar-prom-1.0.3 : Thu Dec 20 11:25:51 =
2007<BR>
&gt; &gt;<BR>
&gt; &gt; DEBUG-TXRX0:0 &gt; ver<BR>
&gt; &gt; ver<BR>
&gt; &gt;<BR>
&gt; &gt; NFP_TXRX : R4.0.0.DEV-CG-021308 : Wed Feb 13 23:51:17 2008<BR>
&gt; &gt; PROM_SIBYTE_CG : Cougar-prom-1.0.3 : Thu Dec 20 11:25:51 =
2007<BR>
&gt; &gt;<BR>
&gt; &gt; Warren says he thinks I am ok, even though it is not the<BR>
&gt; latest 1.0.3.<BR>
&gt; &gt;<BR>
&gt; &gt; _____________________________________________<BR>
&gt; &gt; From: Larry Scheer<BR>
&gt; &gt; Sent: Thursday, February 14, 2008 11:17 AM<BR>
&gt; &gt; To: Maxim Kozlovsky; dl-Cougar<BR>
&gt; &gt; Cc: Jobi Ariyamannil; Sandrine Boulanger; Vikas Saini; Ken =
Renshaw;<BR>
&gt; &gt; Paul Hammer; Ed Kwan<BR>
&gt; &gt; Subject: RE: Status of today's build.<BR>
&gt; &gt;<BR>
&gt; &gt; Yes, I do. At least this was the last release that Brian =
S.<BR>
&gt; said was<BR>
&gt; &gt; &quot;official.&quot;<BR>
&gt; &gt;<BR>
&gt; &gt; SSC-PROM&gt; ver<BR>
&gt; &gt;<BR>
&gt; &gt; PROM_SIBYTE_CG : Cougar-prom-1.0.3 : Thu Jan 17 15:57:20 =
2008<BR>
&gt; &gt;<BR>
&gt; &gt; _____________________________________________<BR>
&gt; &gt; From: Maxim Kozlovsky<BR>
&gt; &gt; Sent: Thursday, February 14, 2008 10:34 AM<BR>
&gt; &gt; To: Larry Scheer; dl-Cougar<BR>
&gt; &gt; Cc: Jobi Ariyamannil; Sandrine Boulanger; Vikas Saini; Ken =
Renshaw;<BR>
&gt; &gt; Paul Hammer; Ed Kwan<BR>
&gt; &gt; Subject: RE: Status of today's build.<BR>
&gt; &gt;<BR>
&gt; &gt; Hello,<BR>
&gt; &gt;<BR>
&gt; &gt; Did you have the latest prom (1.3) when trying to run the =
optimized<BR>
&gt; &gt; build? The txrx will crash if optimized build is run with<BR>
&gt; the earlier<BR>
&gt; &gt; prom releases.<BR>
&gt; &gt;<BR>
&gt; &gt; Max<BR>
&gt; &gt;<BR>
&gt; &gt; _____________________________________________<BR>
&gt; &gt; From: Larry Scheer<BR>
&gt; &gt; Sent: Wednesday, February 13, 2008 10:43 PM<BR>
&gt; &gt; To: dl-Cougar<BR>
&gt; &gt; Cc: Jobi Ariyamannil; Sandrine Boulanger; Vikas Saini; Ken =
Renshaw;<BR>
&gt; &gt; Paul Hammer; Ed Kwan<BR>
&gt; &gt; Subject: Status of today's build.<BR>
&gt; &gt;<BR>
&gt; &gt; Today we scrambled around to fix a problem with the SCSI<BR>
&gt; message code<BR>
&gt; &gt; that manifested in problems with LUN label, volume create,<BR>
&gt; etc. Change<BR>
&gt; &gt; 27822 fixed the problem; at least it appears that way with<BR>
&gt; the debug<BR>
&gt; &gt; builds on both bobcat BSD and cougar systems.<BR>
&gt; &gt;<BR>
&gt; &gt; Jonathan checked in his changes this afternoon (27831) and<BR>
&gt; there was<BR>
&gt; &gt; some question tonight whether everything still worked. I built =
from<BR>
&gt; &gt; the top of the tree (27835) and tested the debug build and<BR>
&gt; everything<BR>
&gt; &gt; appears to be working with the debug build, both cougar and =
bobcat<BR>
&gt; &gt; BSD.<BR>
&gt; &gt;<BR>
&gt; &gt; However the cougar opt build from the top of the tree is<BR>
&gt; not working.<BR>
&gt; &gt; I am seeing deadbeef messages in the console.<BR>
&gt; &gt; I also saw this when the opt build was booted from compact =
flash:<BR>
&gt; &gt;<BR>
&gt; &gt; Starting ONStor initial configuration utility:.<BR>
&gt; &gt; Setting up networking....<BR>
&gt; &gt; Configuring network interfaces...SIOCADDRT: Network is =
unreachable<BR>
&gt; &gt; run-parts: /etc/network/if-up.d/addroutes exited with return =
code 7<BR>
&gt; &gt; SIOCADDRT: File exists<BR>
&gt; &gt; run-parts: /etc/network/if-up.d/addroutes exited with return =
code 7<BR>
&gt; &gt; done.<BR>
&gt; &gt;<BR>
&gt; &gt; Just wanted to give everyone a status and answer some<BR>
&gt; questions about<BR>
&gt; &gt; what works and what doesn't.<BR>
&gt; &gt;<BR>
&gt; &gt; Larry<BR>
&gt; &gt;<BR>
&gt;<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C8700A.366A961E--
