AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:
CFG:
PT:0
S:andy.sharp@lsi.com
RQ:
SSV:mhbs.lsil.com
NSV:
SSH:
R:<rendell.fong@lsi.com>,<bill.fisher@lsi.com>,<brian.stark@lsi.com>
MAID:2
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
X-Sylpheed-End-Special-Headers: 1
Date: Fri, 13 Nov 2009 16:05:37 -0800
From: Andrew Sharp <andy.sharp@lsi.com>
To: Rendell Fong <rendell.fong@lsi.com>
Cc: Bill Fisher <bill.fisher@lsi.com>, Brian Stark <brian.stark@lsi.com>
Subject: pcmcia/CF device discovery and IRQ issues
Message-ID: <20091113160537.72aae476@ripper.onstor.net>
Organization: LSI
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

Hi R & B,

Well, Brian and I may have narrowed things down just a tad.  It seems
to bollucks things up when the kernel is loaded off of the first slot
CF card, slot A.  Of course it's highly itermittent but he's got a
system that does it pretty repeatably.  Loading off of B seems to not
invoke the problem, nor does tftp loading.  Which is why I hardly ever
see it since I'm always tftp loading these days.

You can set your system to load off of B, or if you'd rather...

tftp loading is as simple as setting the boot device in the prom to be
sc0 instead of sda or sdb, and then setting the tftp boot server
IP address.  On that server, the filer's ip address has to be a
directory under the tftp root directory, and vmlinux.bin has to be in
that directory.  That is what it loads.

So, on your tftp server, if the tftp root directory is /tftpboot, and
your filer management IP address is 10.2.699.699, then you need to have
a file

/tftpboot/10.2.699.699/vmlinux.bin

for the filer to tftp load.

This all should actually be on the wiki somewhere.

Just thought I would update you guys so you could work around this
issue since I know it's impacting Bill at least quite a bit.

My laptop battery is dying any moment here, but email me back if you
have any questions.

Cheers,

a
