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:<Brian.Stark@lsi.com>,<Patrick.Haverty@lsi.com>
MAID:2
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/LSI/INBOX	0	E1EC65251D4B3D46BBC0AAA3C0629222AFF75B83@cosmail02.lsi.com
X-Sylpheed-End-Special-Headers: 1
Date: Thu, 3 Dec 2009 12:07:21 -0800
From: Andrew Sharp <andy.sharp@lsi.com>
To: "Stark, Brian" <Brian.Stark@lsi.com>
Cc: "Haverty, Patrick" <Patrick.Haverty@lsi.com>
Subject: Re: Compact Flash
Message-ID: <20091203120721.068e2626@ripper.onstor.net>
In-Reply-To: <E1EC65251D4B3D46BBC0AAA3C0629222AFF75B83@cosmail02.lsi.com>
References: <08A1E1BF683B9844B320294C380BF34C04256AA0@cosmail03.lsi.com>
	<20091202163247.6418e3f7@ripper.onstor.net>
	<E1EC65251D4B3D46BBC0AAA3C0629222AFF75B83@cosmail02.lsi.com>
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

On Wed, 2 Dec 2009 18:30:28 -0700 "Stark, Brian" <Brian.Stark@lsi.com>
wrote:

> We didn't pop out any secondary flashes that were mounted.  Surely, I
> checked for that before doing anything.

But of course ~:^)  Also, it might help to pop out the previous flash,
take a long slow breath, then pop in the new one.  I think it needs
5-10 seconds for the discovery code to get used to the idea that the
old card is truly gone.

> In looking at the code in ssc-nfxsh/cmd_flash.c, it looks like
> there's a minimum size requirement of 980MB.  The first question, of
> course, is why?

We have certain expectations about the size of /var and / and so on, so
some limitations have to be set.  When you start getting down into 955
and so forth, that's pretty crappy small.  IIRC the original wintec's
were true 1GiB.  An obvious sign of a decent piece of hardware.

If flash_install doesn't have a way to override, then I can mod a
custom one for you that will if you still want that.

> Depending on the answer to that, should we consider changing it?  We
> really need to get at least 2 more CF vendors qualified since we only
> have 1 right now.
> 
> And what about the throughput question?
> 
> 
> -----Original Message-----
> From: Andrew Sharp [mailto:andy.sharp@lsi.com] 
> Sent: Wednesday, December 02, 2009 4:33 PM
> To: Haverty, Patrick
> Cc: Stark, Brian
> Subject: Re: Compact Flash
> 
> I can answer all your questions in one sentence.  Oops, no I can't.
> 
> Anyway, the first series of errors is because you popped out/in CF
> card(s) in a bad way.  Bad Pattie.
> <slap-don't-slap-do-slap-that-slap-again-slap>
> 
> Be nice to your kernel, and it will be nice to you ~:^)  Always make
> sure you unmount any mounted partitions *before* pulling a CF card.
> Ignore the LEDs, I've seen the code that controls those ~:^)
> 
> As for the second message, yes, "system copy init" has a minimum
> size requirement.  That card is too small.  I think there's a secret
> hidden option to ignore that, but I don't remember.  There's also
> flash-install.sh, which you should remember.  That's documented in the
> wiki somewhere.  And that doc is probably not more than 3 years out
> of date.  flash-install very likely has a way to override the min size
> limit, because I wrote it and that's the way I roll; it's a shell
> script, so it might be "easy" to look at it and see if you can figure
> out what the secret option is for that.
> 
> I think that's it.  Good!  Time for my nap.
> 
> 
> 
> On Wed, 2 Dec 2009 16:13:04 -0700 "Haverty, Patrick"
> <Patrick.Haverty@lsi.com> wrote:
> 
> > And I meant to ask if you had a method to test the read/write
> > throughput of CF modules which I might use?
> > 
> > Thanks,
> > 
> > Pat
> > 
> > ________________________________
> > From: Haverty, Patrick
> > Sent: Wednesday, December 02, 2009 2:51 PM
> > To: Sharp, Andy
> > Cc: Stark, Brian
> > Subject: Compact Flash
> > 
> > Hello Andy,
> > 
> > Brian and I are trying out some new Compact Flash modules to try and
> > find an alternate part.  Below I'll paste some of the console
> > messages seen when trying the new modules.  Do you know if the size
> > error could be caused by a mismatch between the CF module
> > configurations (different vendors in each slot), and if so can you
> > tell me how I can create a new CF rather than copy an existing one?
> > 
> > Brian could probably speak more intelligently about what we are
> > seeing, but he's tied up in a phone meeting right now.
> > 
> > Thanks,
> > 
> > Pat
> > 
> > Stec CF Module
> > 
> > (Insert module)
> > 
> > ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> > ata3.00: cmd c4/00:08:00:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data
> > 4096 in ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> > ata3.00: cmd c4/00:08:00:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data
> > 4096 in ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> > ata3.00: cmd c4/00:08:00:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data
> > 4096 in ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> > ata3.00: cmd c4/00:08:00:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data
> > 4096 in ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> > ata3.00: cmd c4/00:08:00:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data
> > 4096 in Buffer I/O error on device sdb, logical block 0
> > ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> > ata3.00: cmd c4/00:08:00:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data
> > 4096 in ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> > ata3.00: cmd c4/00:08:00:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data
> > 4096 in ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> > ata3.00: cmd c4/00:08:00:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data
> > 4096 in ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> > ata3.00: cmd c4/00:08:00:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data
> > 4096 in ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> > ata3.00: cmd c4/00:08:00:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data
> > 4096 in ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> > ata3.00: cmd c4/00:08:00:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data
> > 4096 in Buffer I/O error on device sdb, logical block 0
> > 
> > 
> > (Try copy init)
> > 
> > pleasanton diag> system copy init
> > ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> > ata3.00: cmd c4/00:20:00:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data
> > 16384 in ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> > ata3.00: cmd c4/00:20:00:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data
> > 16384 in ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> > ata3.00: cmd c4/00:20:00:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data
> > 16384 in ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> > ata3.00: cmd c4/00:20:00:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data
> > 16384 in ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> > ata3.00: cmd c4/00:20:00:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data
> > 16384 in ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> > ata3.00: cmd c4/00:20:00:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data
> > 16384 in Buffer I/O error on device sdb, logical block 0
> > Buffer I/O error on device sdb, logical block 1
> > Buffer I/O error on device sdb, logical block 2
> > Buffer I/O error on device sdb, logical block 3
> > ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> > ata3.00: cmd c4/00:08:00:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data
> > 4096 in ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> > ata3.00: cmd c4/00:08:00:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data
> > 4096 in ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> > ata3.00: cmd c4/00:08:00:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data
> > 4096 in ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> > ata3.00: cmd c4/00:08:00:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data
> > 4096 in ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> > ata3.00: cmd c4/00:08:00:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data
> > 4096 in ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> > ata3.00: cmd c4/00:08:00:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data
> > 4096 in Buffer I/O error on device sdb, logical block 0
> > Secondary CF card is 977 MiB
> > Disk size 1024966656 bytes is not supported
> > Problem initializing CF card /dev/sdb
> > % Command failure.
> > ******************
> > 
> > Unmarked CF Module
> > 
> > (No console messages upon insertion)
> > 
> > (Try copy init)
> > 
> > pleasanton diag> system copy init
> > Secondary CF card is 977 MiB
> > Disk size 1024966656 bytes is not supported
> > Problem initializing CF card /dev/sdb
> > % Command failure.
> > 
> > ******************
> > 
> > Viking CF Module
> > 
> > (No console messages upon insertion)
> > 
> > (Try copy init)
> > 
> > 
> > pleasanton diag> system copy init
> > Secondary CF card is 955 MiB
> > Disk size 1002258432 bytes is not supported
> > Problem initializing CF card /dev/sdb
> > % Command failure.
> > 
