From: "J.C. Wren" <jcwren@jcwren.com>
To: "S. Effendi" <sef@sysgo.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problems with IDE CF in 2.5.69, 2.5.69-bk13
Date: Thu, 22 May 2003 22:30:13 -0400 [thread overview]
Message-ID: <200305222230.13587.jcwren@jcwren.com> (raw)
In-Reply-To: <200305221714.h4MHEni25606@dagobert.svc.sysgo.de>
Soewono,
Excellent, and thank you very much. That fixed the ludicrous delay and such
while coming up. I still get the kobject_register error, however.
--John
On Thursday 22 May 2003 13:14 pm, you wrote:
> Hi J.C.
>
> give this a try.
>
> best regards
> Soewono
>
> J.C. Wren wrote:
> > Today I ported 2.5.69 to my embedded 386EX system, and am encountering
> > problems with the IDE handling of compact flash cards (Sandisk, Kingston,
> > and
> > a suspected Toshiba controller based card). kobject_register is failing
> > with a -17 (EEXISTS) when registering the hda device:
> >
> > ide: Assuming 50MHz system bus speed for PIO modes; override with
> > idebus=xx hda: SunDisk SDCFB-48, CFA DISK drive
> > ide0 at 0x1f0-0x1f7,0x3f6 on irq 9
> > hda: max request size: 128KiB
> > hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
> > hda: task_no_data_intr: error=0x04 { DriveStatusError }
> > hda: 93952 sectors (48 MB) w/1KiB Cache, CHS=734/4/32
> > hda: hda1
> > hda: hda1
> > kobject_register failed for hda1 (-17)
> > Call Trace: [<c01631bf>] [<c0155308>] [<c017007b>] [<c0163a37>]
> > [<c0170060>] [<c0177eb6>] [<c0177e64>] [<c0177e6c>] [<c018afd4>]
> > [<c0187602>] [<c01883ea>] [<c018aff2>] [<c0200611>] [<c0105024>]
> > [<c0105040>] [<c0105024>] [<c0106dbd>]
> >
> > The .config looks like:
> >
> > CONFIG_IDE=y
> > CONFIG_BLK_DEV_IDE=y
> > # CONFIG_BLK_DEV_HD_IDE is not set
> > # CONFIG_BLK_DEV_HD is not set
> > CONFIG_BLK_DEV_IDEDISK=y
> > CONFIG_IDEDISK_MULTI_MODE=y
> > # CONFIG_IDEDISK_STROKE is not set
> > # CONFIG_BLK_DEV_IDECD is not set
> > # CONFIG_BLK_DEV_IDEFLOPPY is not set
> > # CONFIG_IDE_TASK_IOCTL is not set
> > # CONFIG_BLK_DEV_CMD640 is not set
> >
> > The CF card is connected directly to the bus through a couple of latches
> > (i.e., not using a CMD640 or PCI chipset or anything). There is no DMA.
> > The hardware is fully functional, as I've been using the 2.2.12 kernel
> > driver for a couple of years (although I've always gotten the status=0x51
> > that IDEDISK_MULTI_MODE is suggested for).
> >
> > The Sandisk and Kingston come up pretty quickly. The third card, which
> > apparently has no embedded ID, hangs the system about 60 seconds, before
> > continuing with the same error. I've tried hda=slow, and all the
> > permutation I can think of that would make any sense.
> >
> > I saw a few reports but no resolution against the 2.4.60-ac kernels.
> > I've also applied the bk13 patches against 2.5.69 in hopes that there
> > might be some resolution there.
> >
> > I'm prefectly willing to give anything anyone suggests a try. Are there
> > any additional debugging options I can/should turn on that would help
> > anyone debug this issue?
> >
> > --John
> >
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel"
> > in the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2003-05-23 2:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-20 0:51 J.C. Wren
[not found] ` <200305221714.h4MHEni25606@dagobert.svc.sysgo.de>
2003-05-23 2:30 ` J.C. Wren [this message]
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=200305222230.13587.jcwren@jcwren.com \
--to=jcwren@jcwren.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sef@sysgo.de \
/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
all inboxes | Powered by JetHome®