linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Scholz <steven.scholz@imc-berlin.de>
To: linux-ide@vger.kernel.org
Subject: Problems with 1GB SimpleTech CF Card
Date: Wed, 24 May 2006 12:34:27 +0200	[thread overview]
Message-ID: <447436B3.4090906@imc-berlin.de> (raw)

Hi all,

I get repeatable erros when accessing a 1GB SimpleTech CF Flash Card (SLCF1GBJ).

I tested on three different systems (i86, arm, ppc) with three different
kernel versions (2.6.13, 2.6.14, 2.4.20). On ARM and PPC I tested pcmcia
mode _and_ TrueATA mode. Other, smaller (!) CF Cards are working fine.

So here we go:

~ # hdparm -i /dev/hda
Model=STI Flash 7.0.0, FwRev=05/03/04, SerialNo=STI J107004201112846
 Config={ HardSect NotMFM Removeable DTR>10Mbs nonMagnetic }
 RawCHS=2006/16/63, TrkSize=0, SectSize=0, ECCbytes=4
 BuffType=unknown, BuffSize=0kB, MaxMultSect=1, MultSect=off
 CurCHS=2006/16/63, CurSects=2022048, LBA=yes, LBAsects=2022048
 IORDY=no, tPIO={min:120,w/IORDY:120}
 PIO modes:  pio0 pio1 pio2 pio3 pio4
 AdvancedPM=no WriteCache=enabled

When doing "mke2fs /dev/hda1" after 30 seconds I get

	hda: irq timeout: status=0xd0 { Busy }
	ide: failed opcode was: unknown
	ide0: reset: master: error (0x00?)

and then after a long time loads of

	end_request: I/O error, dev hda, sector 786495
	Buffer I/O error on device hda1, logical block 786432
	lost page write due to I/O error on hda1

messages.

Has anyone else seen this before? Is it related to the size of the CF card?
The smaller, working cards use
	CurCHS=980/8/32, CurSects=250880, LBA=yes, LBAsects=250880
	CurCHS=980/16/32, CurSects=501760, LBA=yes, LBAsects=501760

Thanks a million!

--
Steven


             reply	other threads:[~2006-05-24 10:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-24 10:34 Steven Scholz [this message]
2006-05-24 13:53 ` Problems with 1GB SimpleTech CF Card Mark Lord
2006-05-24 14:03   ` Steven Scholz
  -- strict thread matches above, loose matches on Subject: below --
2006-05-24 12:28 Raphael Bossek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=447436B3.4090906@imc-berlin.de \
    --to=steven.scholz@imc-berlin.de \
    --cc=linux-ide@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).