X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C87A86.C7A1B054@onstor-exch02.onstor.net>; Thu, 28 Feb 2008 20:54:27 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: concrete info on CF status problem
Date: Thu, 28 Feb 2008 20:54:27 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E089F19C5@onstor-exch02.onstor.net>
In-Reply-To: <20080228185120.016da30b@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: concrete info on CF status problem
Thread-Index: Ach6ffY8vhMvqi3FQWKitN3Y5dkFbgACEGzA
References: <20080225140859.55145d81@ripper.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E089F185F@onstor-exch02.onstor.net><20080228162754.3c0479e9@ripper.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E089F1902@onstor-exch02.onstor.net><20080228174605.206a0a38@ripper.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E089F1971@onstor-exch02.onstor.net> <20080228185120.016da30b@ripper.onstor.net>
From: "Brian Stark" <brian.stark@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>
Cc: "Warren Gale" <warren.gale@onstor.com>

You've sapped all my energy, so I'm taking tomorrow off.  I'll have to
miss the ice cream social tomorrow.  Darn it.

Seriously, I might have to be at home in the afternoon tomorrow, so I
won't be coming down to Campbell.  I'll be in Pleasanton in the morning
and will happily eject the CF to your heart's content.  I gave you the
terminal info, so just let me know if you want me to do this.  If we
don't figure it out tomorrow, then I'll bring the system down to
Campbell on Monday (again). =20

I look forward to winning the bet.  Then again, no matter what happens,
I'm sure we'll never admit it was either a kernel or hardware bug.
We'll somehow conclude it was a PROM bug and blame it on Rick.

=20

> -----Original Message-----
> From: Andy Sharp=20
> Sent: Thursday, February 28, 2008 6:51 PM
> To: Brian Stark
> Cc: Warren Gale
> Subject: Re: concrete info on CF status problem
>=20
> On Thu, 28 Feb 2008 17:51:50 -0800 "Brian Stark"
> <brian.stark@onstor.com> wrote:
>=20
> > =20
> >=20
> > > -----Original Message-----
> > > From: Andy Sharp
> > > Sent: Thursday, February 28, 2008 5:46 PM
> > > To: Brian Stark
> > > Cc: Warren Gale
> > > Subject: Re: concrete info on CF status problem
> > >=20
> > > On Thu, 28 Feb 2008 16:51:10 -0800 "Brian Stark"
> > > <brian.stark@onstor.com> wrote:
> > >=20
> > > > No, I see nothing.  This is not a board problem -- the=20
> interrupt=20
> > > > is firing and something is then reading the status reg in the=20
> > > > 1520.
> > >=20
> > > That's OK, I recognize your denial and it's only human, after all.
> >=20
> > Good one.
>=20
> Thangyouverymuch.  I'm here all week.  Until the Ice cream social
> (wtf?) tomorrow, that is.
>=20
> > > > I've tried your old Rev 2 board, a Rev 3 board, and a=20
> Rev 4 board.
> > > > Plus, I can show you the diffs in the netlists between Rev
> > > 2 - Rev 4,
> > > > and there's nothing in the hardware that's changed with=20
> any of the=20
> > > > connections between CF, 1520, and 1125.
> > >=20
> > > What about the 1520 itself?  Different rev, different part no.,=20
> > > different supplier, different version? Just because=20
> nothing changed=20
> > > in the netlists doesn't rule out something not right with the way=20
> > > they were built.  Or if we switched to a slightly different part=20
> > > that's RoHS compatible or something.
> >=20
> > Nope, the 1520 is sole-sourced to TI and it hasn't changed in eons.
> > Nice try.  It ain't the 1520 or the board -- the interrupt=20
> is firing=20
> > to the 1125 and then the status reg is read.  I think I=20
> need to draw=20
> > you a picture.
>=20
> Damn, you're right, its most likely a kernel bug.  It=20
> obviously means nothing that between PROM, software and=20
> hardware, it's the only thing that hasn't changed in months. =20
> Because it couldn't be a hardware issue, despite that this=20
> all started on the affected systems immediately after they=20
> had their boards replaced.
>=20
> On a serious side, can my old board be set up in the lab here=20
> in Camphell tomorrow?  Are you or someone coming here=20
> tomorrow?  I assume so, you guys couldn't be contemplating=20
> missing the ICS.
>=20
