AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080228185004.08c4b186@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<brian.stark@onstor.com>,<warren.gale@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	BB375AF679D4A34E9CA8DFA650E2B04E089F1971@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Thu, 28 Feb 2008 18:51:20 -0800
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Brian Stark" <brian.stark@onstor.com>
Cc: "Warren Gale" <warren.gale@onstor.com>
Subject: Re: concrete info on CF status problem
Message-ID: <20080228185120.016da30b@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E089F1971@onstor-exch02.onstor.net>
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>
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 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 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 with the way 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 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 means
nothing that between PROM, software and hardware, it's the only thing
that hasn't changed in months.  Because it couldn't be a hardware issue,
despite that this all started on the affected systems immediately after
they had their boards replaced.

On a serious side, can my old board be set up in the lab here in
Camphell tomorrow?  Are you or someone coming here tomorrow?  I assume
so, you guys couldn't be contemplating missing the ICS.
