X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C87FF6.7E9359E0@onstor-exch02.onstor.net>; Thu, 6 Mar 2008 18:56:44 -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, 6 Mar 2008 18:56:43 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E08C0EF0D@onstor-exch02.onstor.net>
In-Reply-To: <3245C796-9B2A-4682-8EDB-7844F2EF984F@onstor.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: concrete info on CF status problem
Thread-Index: Ach/8nsJJJ+lQkLSSJGBRTRcWtdnGAAA+LZQ
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><BB375AF679D4A34E9CA8DFA650E2B04E089F19C5@onstor-exch02.onstor.net> <20080228202749.036b8be7@ripper.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E089F19E7@onstor-exch02.onstor.net> <3245C796-9B2A-4682-8EDB-7844F2EF984F@onstor.com>
From: "Brian Stark" <brian.stark@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>
Cc: "Warren Gale" <warren.gale@onstor.com>

Are you implying that you're coming to Pleasanton tomorrow?  If so, I'm
not gonna be here because Bob has scheduled some meetings down in
Campbell that I'll be attending...

=20

> -----Original Message-----
> From: Andy Sharp=20
> Sent: Thursday, February 28, 2008 8:41 PM
> To: Brian Stark
> Cc: Warren Gale
> Subject: Re: concrete info on CF status problem
>=20
>=20
> On Feb 28, 2008, at 8:37 PM, Brian Stark wrote:
>=20
> > As much as I'd love to see your shiny, happy face tomorrow,=20
> I hate for=20
> > you to make a trip all the way up to P'town just so you can=20
> sit in the=20
> > lab and eject CF cards on your old board that doesn't work like you=20
> > think.  Then again, you'll get more work done since it's so=20
> pleasant=20
> > in Pleasanton...
>=20
> Oh, that one's going to cost you.
>=20
> >
> >
> >
> >
> >> -----Original Message-----
> >> From: Andy Sharp
> >> Sent: Thursday, February 28, 2008 8:28 PM
> >> To: Brian Stark
> >> Cc: Warren Gale
> >> Subject: Re: concrete info on CF status problem
> >>
> >> On Thu, 28 Feb 2008 19:54:27 -0800 "Brian Stark"
> >> <brian.stark@onstor.com> wrote:
> >>
> >>> You've sapped all my energy, so I'm taking tomorrow off.
> >> I'll have to
> >>> miss the ice cream social tomorrow.  Darn it.
> >>
> >> Ah, too bad.  You're going to miss out, because I've=20
> already picked=20
> >> up a case of Jack Daniels to bring to the ICS tomorrow,=20
> along with a=20
> >> fresh batch of grenades. Should be very interesting.
> >>
> >>> 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=20
> >>> 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).
> >>
> >> I'm dying to get after this, it's the only non-ignorable bug on my=20
> >> list, and I've fixed all the ignorable ones anyway.  I think I'll=20
> >> head up to P-town in the morning.
> >>
> >>> I look forward to winning the bet.  Then again, no matter what=20
> >>> 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=20
> it on Rick.
> >>
> >> Well duh.  I mean, wait, Rick who?  Actually I think the answer is
> >> clear: there is no bug because there couldn't be.  QA=20
> "sees things"=20
> >> all the time, it's obviously just another one of those.
> >>
> >>>
> >>>
> >>>
> >>>> -----Original Message-----
> >>>> From: Andy Sharp
> >>>> Sent: Thursday, February 28, 2008 6:51 PM
> >>>> To: Brian Stark
> >>>> Cc: Warren Gale
> >>>> Subject: Re: concrete info on CF status problem
> >>>>
> >>>> On Thu, 28 Feb 2008 17:51:50 -0800 "Brian Stark"
> >>>> <brian.stark@onstor.com> wrote:
> >>>>
> >>>>>
> >>>>>
> >>>>>> -----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
> >>>>>>
> >>>>>> On Thu, 28 Feb 2008 16:51:10 -0800 "Brian Stark"
> >>>>>> <brian.stark@onstor.com> wrote:
> >>>>>>
> >>>>>>> No, I see nothing.  This is not a board problem -- the
> >>>> interrupt
> >>>>>>> is firing and something is then reading the status
> >> reg in the
> >>>>>>> 1520.
> >>>>>>
> >>>>>> That's OK, I recognize your denial and it's only human, after=20
> >>>>>> all.
> >>>>>
> >>>>> Good one.
> >>>>
> >>>> Thangyouverymuch.  I'm here all week.  Until the Ice cream social
> >>>> (wtf?) tomorrow, that is.
> >>>>
> >>>>>>> I've tried your old Rev 2 board, a Rev 3 board, and a
> >>>> 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
> >>>> any of the
> >>>>>>> connections between CF, 1520, and 1125.
> >>>>>>
> >>>>>> What about the 1520 itself?  Different rev, different
> >> part no.,
> >>>>>> different supplier, different version? Just because
> >>>> nothing changed
> >>>>>> in the netlists doesn't rule out something not right=20
> with the way=20
> >>>>>> they were built.  Or if we switched to a slightly
> >> different
> >>>>>> part that's RoHS compatible or something.
> >>>>>
> >>>>> Nope, the 1520 is sole-sourced to TI and it hasn't changed in=20
> >>>>> eons. Nice try.  It ain't the 1520 or the board -- the interrupt
> >>>> is firing
> >>>>> to the 1125 and then the status reg is read.  I think I
> >>>> need to draw
> >>>>> you a picture.
> >>>>
> >>>> Damn, you're right, its most likely a kernel bug.  It obviously=20
> >>>> means nothing that between PROM, software and hardware, it's the=20
> >>>> only thing that hasn't changed in months.
> >>>> Because it couldn't be a hardware issue, despite that this all=20
> >>>> started on the affected systems immediately after they had their=20
> >>>> boards replaced.
> >>>>
> >>>> On a serious side, can my old board be set up in the lab here in=20
> >>>> Camphell tomorrow?  Are you or someone coming here tomorrow?  I=20
> >>>> assume so, you guys couldn't be contemplating missing the ICS.
> >>>>
> >>
>=20
>=20
