Errors with M-Systems' DOC v MD2200 D16 and ext2

Errors with M-Systems' DOC v MD2200 D16 and ext2

[Mendel Mobach]

Hello

I've got 2 systems with M-systems' DOC
1 with the MD2800 (linux says using the milenium driver) 
(8MD, 1 chip)
and 1 with the MD2200 (16 MB, 2 chips of 8 for mtd0)

With the 2800 I've got no problems but with the 
2200 I've got problems and get some very strange kernel messages

I'm running kernel 2.4.2-pre2 on this system and I attached a harddisk
for development

See below for the kernel and boot messages what kind of problems I've
got

so this is a HELP request from a (l?)user who don't know how to
handle it but wants some help from a expert or someone who knows this
problem
and how I can solve it.

Regards

Mendel Mobach

--------------------- the messages I got yesterday: --------------
kernel:  nftl/disc0/disc: p1 
kernel: EXT2-fs error (device nftl(93,1)): ext2_readdir: bad entry in
directory #11: directory entry across blocks - offset=0, inode=757083762
kernel: EXT2-fs warning (device nftl(93,1)): empty_dir: bad directory
(dir #2025) - no `.' or `..' 
kernel: EXT2-fs error (device nftl(93,1)): ext2_readdir: bad entry in
directory #11: directory entry across blocks - offset=0, inode=757083762
kernel: EXT2-fs error (device nftl(93,1)): ext2_readdir: bad entry in
directory #11: directory entry across blocks - offset=0, inode=757083762
kernel: No Virtual Unit Chains available for folding. Failing request 
kernel: Cannot make free space. 
kernel: NFTL_writeblock(): Cannot find block to write to 
kernel: end_request: I/O error, dev 5d:01 (unknown), sector 2 
kernel: No Virtual Unit Chains available for folding. Failing request 
-------------------------------------------------------------------

-------- today messages stuff -------------
kernel:  nftl/disc0/disc: p1 
kernel: devfs: devfs_register(part1): NULL ops, got c026b960 from major
table 
kernel:  nftl/disc0/disc: p1 
kernel: end_request: I/O error, dev 5d:01 (unknown), sector 14 
kernel: EXT2-fs error (device nftl(93,1)): ext2_write_inode: unable to
read inode block - inode=17, block=7 
kernel: end_request: I/O error, dev 5d:01 (unknown), sector 14 
kernel: EXT2-fs error (device nftl(93,1)): ext2_write_inode: unable to
read inode block - inode=18, block=7 
kernel: end_request: I/O error, dev 5d:01 (unknown), sector 14 
kernel: EXT2-fs error (device nftl(93,1)): ext2_write_inode: unable to
read inode block - inode=19, block=7 
kernel: end_request: I/O error, dev 5d:01 (unknown), sector 14 
kernel: EXT2-fs error (device nftl(93,1)): ext2_write_inode: unable to
read inode block - inode=20, block=7 
kernel: end_request: I/O error, dev 5d:01 (unknown), sector 14 
kernel: EXT2-fs error (device nftl(93,1)): ext2_write_inode: unable to
read inode block - inode=21, block=7 
kernel: end_request: I/O error, dev 5d:01 (unknown), sector 14 
kernel: EXT2-fs error (device nftl(93,1)): ext2_write_inode: unable to
read inode block - inode=22, block=7 
kernel: end_request: I/O error, dev 5d:01 (unknown), sector 14 
kernel: EXT2-fs error (device nftl(93,1)): ext2_write_inode: unable to
read inode block - inode=23, block=7 
kernel: end_request: I/O error, dev 5d:01 (unknown), sector 14 
kernel: EXT2-fs error (device nftl(93,1)): ext2_write_inode: unable to
read inode block - inode=24, block=7 
kernel: end_request: I/O error, dev 5d:01 (unknown), sector 14 
kernel: EXT2-fs error (device nftl(93,1)): ext2_write_inode: unable to
read inode block - inode=22, block=7 
kernel: EXT2-fs warning: mounting fs with errors, running e2fsck is
recommended 
kernel: end_request: I/O error, dev 5d:01 (unknown), sector 14 
kernel: EXT2-fs error (device nftl(93,1)): ext2_read_inode: unable to
read inode block - inode=21, block=7 
kernel: end_request: I/O error, dev 5d:01 (unknown), sector 14 
kernel: EXT2-fs error (device nftl(93,1)): ext2_read_inode: unable to
read inode block - inode=22, block=7 
kernel: Error programming flash 
last message repeated 6 times 
------------------------------------------------------------

-----------------------Kernelmessages-----------------------
M-Systems DiskOnChip driver. (C) 1999 Machine Vision Holdings, Inc.
Possible DiskOnChip with unknown ChipID FF found at 0xc8000
Possible DiskOnChip with unknown ChipID FF found at 0xca000
Possible DiskOnChip with unknown ChipID FF found at 0xcc000
Possible DiskOnChip with unknown ChipID FF found at 0xce000
DiskOnChip 2000 found at address 0xD0000
Flash chip found: Manufacturer ID: 98, Chip ID: E6 (Toshiba
TC58V64AFT/DC)
2 flash chips found. Total DiskOnChip size: 16 Mb
mtd: Giving out device 0 to DiskOnChip 2000
Ignoring DiskOnChip 2000 at 0xD2000 - already configured
Ignoring DiskOnChip 2000 at 0xD4000 - already configured
Ignoring DiskOnChip 2000 at 0xD6000 - already configured
Possible DiskOnChip with unknown ChipID FF found at 0xd8000
Possible DiskOnChip with unknown ChipID FF found at 0xda000
Possible DiskOnChip with unknown ChipID FF found at 0xdc000
Possible DiskOnChip with unknown ChipID FF found at 0xde000
Possible DiskOnChip with unknown ChipID FF found at 0xe0000
Possible DiskOnChip with unknown ChipID FF found at 0xe2000
Possible DiskOnChip with unknown ChipID FF found at 0xe4000
Possible DiskOnChip with unknown ChipID FF found at 0xe6000
Possible DiskOnChip with unknown ChipID FF found at 0xe8000
Possible DiskOnChip with unknown ChipID FF found at 0xea000
Possible DiskOnChip with unknown ChipID FF found at 0xec000
Possible DiskOnChip with unknown ChipID FF found at 0xee000
M-Systems NAND Flash Translation Layer driver. (C) 1999 MVHI
$Id: nftl.c,v 1.57 2000/12/01 17:51:54 dwmw2 Exp $
 nftla: unknown partition table  <--- (#comment) not strange, i just
used nflt_format and rebooted
-----------------------------------------------------------

---
Mendel Mobach aka BugBlue - mendel@mobach.nl - bugblue@dds.nl
ICQ: 40200278 - IRC: BugBlue (ircnet:#ne2000 undernet:#groningen)
/"\                        |   [Student]           
\ /                        |   [IPv6 tester]
 X  ASCII RIBBON CAMPAIGN  |   [coder]
/ \ AGAINST HTML MAIL      |   [Possible security tester]


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

Re: Errors with M-Systems' DOC v MD2200 D16 and ext2

[David Woodhouse]

mendel@mobach.nl said:
>  With the 2800 I've got no problems but with the  2200 I've got
> problems and get some very strange kernel messages 

Running out of free blocks to write to - again. This has happened to a few 
people. I'm confused. I put a change into the CVS tree to attempt to fix 
this - can you try it? Just drop nftl.c and nftlmount.c from CVS on top of 
the versions in your kernel tree.

--
dwmw2




To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

Re: Errors with M-Systems' DOC v MD2200 D16 and ext2

[Vipin Malik]

David,

I got something similar. I'm (I think) using the latest versions from CVS
(nftl.c is ver. 1.66 and
nftlmount.c is ver. 1.12). I just did a cvs update and no new versions came
down.

Here is my situation:

 I have a DOC2000 32MB w/ 0x4000 (16k) erase size.
   This causes nftl_format to bail out as it explicitely checks for an erase
size of 0x2000 (8k) before it does anything.
Since not having much to loose, I removed that check and went ahead and
formatted the disk anyway. It did not complain.
I could then modprobe in docprobe (After removing the module after the
format). This time, it detected AND installed the NFTL device under
/dev/nftla.
   I could then fdisk it and create a partition on it, create a fs on (ext2
with mke2fs) and mount it.

   My question is: Why was the explicit check being done? Are there any traps
"lurking" for me now that I have removed the check and formatted my disk with
nftl_format?

   While copying data to the disk (cp -a /bin /mnt/doc2000 etc.) I would get
the data to copy, but after a few seconds (I guess when the cache is flushed
to disk) I would get a bunch of ext2-fs errors like:

end_request: I/O error, dev 5d:01 (unknown) sector 28
EXT2-fs error (device nftl(93,1)): ext2_write_inode: unable to read inode
block - inode=73, block=14
....
...
repeat above for inodes 74...80 rest of error same (same sector (28), block
=14).

I then unmounted the fs and did an e2fsck on /dev/nftl1

I then got error messages regarding short reads reading block 14 (on sector
28). Same problem as above.

Is this related to the format kludge that I did or something else?

Thanks

Vipin

Vipin Malik
Sr. Design Engr.
Daniel Industries
Houston, TX






David Woodhouse wrote:

> mendel@mobach.nl said:
> >  With the 2800 I've got no problems but with the  2200 I've got
> > problems and get some very strange kernel messages
>
> Running out of free blocks to write to - again. This has happened to a few
> people. I'm confused. I put a change into the CVS tree to attempt to fix
> this - can you try it? Just drop nftl.c and nftlmount.c from CVS on top of
> the versions in your kernel tree.
>
> --
> dwmw2
>
> To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org



To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

Re: Errors with M-Systems' DOC v MD2200 D16 and ext2

[Mendel Mobach]

David Woodhouse wrote:
> 
> mendel@mobach.nl said:
> >  With the 2800 I've got no problems but with the  2200 I've got
> > problems and get some very strange kernel messages
> 
> Running out of free blocks to write to - again. This has happened to a few
> people. I'm confused. I put a change into the CVS tree to attempt to fix
> this - can you try it? Just drop nftl.c and nftlmount.c from CVS on top of
> the versions in your kernel tree.
I trid this from the latest version of the CVS tree..
($Id: nftl.c,v 1.57 2000/12/01 17:51:54 dwmw2 Exp $)
But I'v got still the same errors
(I build from a clean kernel source tree)

Regards

Mendel Mobach
> 
> --
> dwmw2

-- 
Mendel Mobach aka BugBlue - mendel@mobach.nl - bugblue@dds.nl
ICQ: 40200278 - IRC: BugBlue (ircnet:#ne2000 undernet:#groningen)
/"\                        |   [Student]           
\ /                        |   [IPv6 tester]
 X  ASCII RIBBON CAMPAIGN  |   [coder]
/ \ AGAINST HTML MAIL      |   [Possible security tester]


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

Re: Errors with M-Systems' DOC v MD2200 D16 and ext2

[David Woodhouse]

mendel@mobach.nl said:
> I trid this from the latest version of the CVS tree..
> ($Id: nftl.c,v 1.57 2000/12/01 17:51:54 dwmw2 Exp $) 
> But I'v got still the same errors (I build from a clean kernel source tree)

Argh. -ENOTIME. When Red Hat get round to releasing a distribution with a 
2.4 kernel, someone bugzilla the fact that it doesn't support the 
DiskOnChip :). 

Better still, someone approach Cygnus^WRed Hat with a contract for
supporting it. Till then, I'm trying to fix it up in my spare time. I'm not
going to be able to pay much attention to this for about a month at the
soonest. Let me know if you want to help - specs are available if you're
serious.


--
dwmw2




To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org