AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20081020151742.3bb16619@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<paul.negus@onstor.com>,<joe.fuller@onstor.com>,<brian.stark@onstor.com>,<eugene.rosario@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	54678	BB375AF679D4A34E9CA8DFA650E2B04E0C0D820D@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Mon, 20 Oct 2008 15:18:04 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Paul Negus" <paul.negus@onstor.com>
Cc: "Joe Fuller" <joe.fuller@onstor.com>, "Brian Stark"
 <brian.stark@onstor.com>, "Eugene Rosario" <eugene.rosario@onstor.com>
Subject: Re: Cougar Stop Ship
Message-ID: <20081020151804.2ef242ae@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E0C0D820D@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E0C0D7BF9@onstor-exch02.onstor.net>
 <BB375AF679D4A34E9CA8DFA650E2B04E0C0D81AB@onstor-exch02.onstor.net>
 <20081015110133.2c2b1338@ripper.onstor.net>
 <BB375AF679D4A34E9CA8DFA650E2B04E0C0D820D@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

The performance issue was only that they didn't perform quite as fast
as the original Wintecs.  But it seems the new Wintecs are about the
same.  Once you get a little bit of fragmentation on the original
Wintec's, they are all pretty much about the same.

On Wed, 15 Oct 2008 11:03:27 -0700 "Paul Negus" <paul.negus@onstor.com>
wrote:

> What was the performance issue?  Just the ID?
> 
> Paul
> 
> -----Original Message-----
> From: Andy Sharp 
> Sent: Wednesday, October 15, 2008 11:02 AM
> To: Joe Fuller
> Cc: Brian Stark; Paul Negus; Eugene Rosario
> Subject: Re: Cougar Stop Ship
> 
> Hi Joe,
> 
> The issue was the same as for these "new" Wintec cards, the UNIGEN
> cards don't ID themselves, so their product strings and codes had to
> be put into the kernel so it could boot off them.  That mod was part
> of the original 4.0.0 release.
> 
> Cheers,
> 
> a
> 
> On Wed, 15 Oct 2008 10:10:43 -0700 "Joe Fuller"
> <joe.fuller@onstor.com> wrote:
> 
> > Hi Andy,
> > 
> >  
> > 
> > We are working on testing the Unigen compactflash again for
> > Production. Is it possible for you to give me a brief on what was
> > the issue and what was the fix?
> > 
> >  
> > 
> > Thanks,
> > 
> > Joe Fuller
> > 
> >  
> > 
> > ________________________________
> > 
> > From: Brian Stark 
> > Sent: Monday, October 13, 2008 6:26 PM
> > To: Paul Negus
> > Cc: Joe Fuller; Eugene Rosario
> > Subject: RE: Cougar Stop Ship
> > 
> >  
> > 
> > Paul,
> > 
> >  
> > 
> > I just got off the phone with Andy and think that adding the Unigens
> > back to the AVL is the way to go.  I have some 1GB Unigens in
> > Pleasanton that can be used if you can't find new ones, although
> > these have been sitting in the lab for several months.  
> > 
> >  
> > 
> > Andy is going to check the fix for the Wintec issue into the dev
> > branch and then we have the option of including the fix in 4.0.1 or
> > in a patch. The fix is straightforward, but as you mentioned, it
> > will have a small test impact.  At this point, I think the patch is
> > the way to go so that we don't further delay 4.0.1, but that
> > assumes you can get Unigens.
> > 
> >  
> > 
> > Let me know what you guys find with the Unigens and then we can
> > further discuss where the Wintec fix goes.
> > 
> >  
> > 
> >  
> > 
> > Thanks,
> > 
> > Brian
> > 
> >  
> > 
> >  
> > 
> > ________________________________
> > 
> > From: Paul Negus 
> > Sent: Monday, October 13, 2008 4:06 PM
> > To: Brian Stark
> > Cc: Joe Fuller; Eugene Rosario
> > Subject: Cougar Stop Ship
> > Importance: High
> > 
> >  
> > 
> > Brian,
> > 
> >  
> > 
> > We have a stop ship in place on Cougar for a Compact Flash issue
> > that we need your input on urgently.
> > 
> >  
> > 
> > You can see from the email thread below that Wintec made a change
> > that they assumed nobody would realize.   Unfortunately this has
> > resulted in a kernel panic and failure to boot from this revised
> > device.
> > 
> >  
> > 
> > We do not believe that we can send anymore units out to the field
> > until we have this resolved.  Wintec have said that they will not be
> > setting this id in their products going forward.
> > 
> >  
> > 
> > Andy Sharp and Larry both stated on Friday that we can switch to
> > Unigen parts.  Under MCO 00273 we disqualified the Unigen parts for
> > a performance issue with cougar that were stated as being addressed
> > later. We have not amended that MCO so Unigen are currently not on
> > the avl.
> > 
> >  
> > 
> > Andy has also stated that he can change our software to recognize
> > the Wintec part but I do not know when that will be ready and
> > tested so that we can use it.
> > 
> >  
> > 
> > We have a few options that I can see:
> > 
> >  
> > 
> > 1.	Ask Wintec to reprogram the devices that we have in house
> > so that our software can recognize it.  The worse case situation if
> > a unit crashes with the old version of the CF and the CF card gets
> > corrupted then there is no way to recover that system in the field
> > and the system would require a mandatory software upgrade which all
> > leads to a big customer sat negative.
> > 2.	Re-institute the Unigen parts on the avl.  We do not have
> > these in stock at present but are looking at what the lead-time
> > would be. 3.	Change our software.  This has been stated as a
> > simple fix but would require testing to validate, so far an unknown
> > time frame.
> > 
> >  
> > 
> > At present I see switching to unigen parts as being the fastest way
> > to a resolution but we need you take on the situation to help move
> > us forward.
> > 
> >  
> > 
> > Paul
> > 
> >  
> > 
> >  
> > 
> >  
> > 
> >  
> > 
> >  
> > 
> > From: Eric Epding -OEM [mailto:oem_erice@wintecind.com] 
> > Sent: Friday, October 10, 2008 12:04 PM
> > To: Joe Fuller
> > Cc: Felix Chen - ENG; Matthew Gallagher
> > Subject: RE: 1GB compactflash W7CF010G1XA-HOP5
> > 
> >  
> > 
> > Hi Joe, We did do a change. Can you just change your software to
> > recognize the new ID info? All else  from an IC point of view is the
> > same. And of course if there was a change there that would be a PCN
> > issue.
> > 
> > Thanks,
> > 
> > Eric
> > 
> >  
> > 
> >  
> > 
> > ________________________________
> > 
> > From: Joe Fuller [mailto:joe.fuller@onstor.com] 
> > Sent: Friday, October 10, 2008 10:08 AM
> > To: Eric Epding -OEM
> > Cc: Felix Chen - ENG; Matthew Gallagher
> > Subject: RE: 1GB compactflash W7CF010G1XA-HOP5
> > 
> > This is what we found.
> > 
> >  
> > 
> > Good card read:
> > 
> > Product Name:   Wintec Industries CF 1GB
> > Identification: manf_id: 0x000a card_id: 0x0000
> > 
> >  
> > 
> > Failed card read:
> > 
> > Product Name:   Wintec Model1
> > Identification: manf_id: 0x0000 card_id: 0x0000
> > 
> >  
> > 
> >  
> > 
> > ________________________________
> > 
> > From: Eric Epding -OEM [mailto:oem_erice@wintecind.com] 
> > Sent: Friday, October 10, 2008 10:00 AM
> > To: Joe Fuller
> > Cc: Felix Chen - ENG; Matthew Gallagher
> > Subject: RE: 1GB compactflash W7CF010G1XA-HOP5
> > 
> >  
> > 
> > Hi Joe,  We have been shipping the 1GB CF for about two years..no
> > problems.
> > 
> >  
> > 
> > Felex , Have we changed in thing ?? Manufacture ID code changed
> > recently??
> > 
> > Thanks,
> > 
> > Eric
> > 
> >  
> > 
> > ________________________________
> > 
> > From: Joe Fuller [mailto:joe.fuller@onstor.com] 
> > Sent: Friday, October 10, 2008 8:47 AM
> > To: Eric Epding -OEM
> > Subject: 1GB compactflash W7CF010G1XA-HOP5
> > 
> > Hi Eric,
> > 
> > Did Wintec make a change in this part recently?
> > 
> > We have been using it for a few months now with no problem. But
> > recently they fail due to our software not recognizing the manuf_id.
> > Has the manuf_id of this part changed?
> > 
> > Thanks,
> > 
> > Joe fuller
> > 
> >  
> > 
