Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263590AbTEWCRK (ORCPT ); Thu, 22 May 2003 22:17:10 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263591AbTEWCRK (ORCPT ); Thu, 22 May 2003 22:17:10 -0400 Received: from mail148.mail.bellsouth.net ([205.152.58.108]:5224 "EHLO imf62bis.bellsouth.net") by vger.kernel.org with ESMTP id S263590AbTEWCRH (ORCPT ); Thu, 22 May 2003 22:17:07 -0400 From: "J.C. Wren" Reply-To: jcwren@jcwren.com To: "S. Effendi" Subject: Re: Problems with IDE CF in 2.5.69, 2.5.69-bk13 Date: Thu, 22 May 2003 22:30:13 -0400 User-Agent: KMail/1.5.2 References: <200305192051.20194.jcwren@jcwren.com> <200305221714.h4MHEni25606@dagobert.svc.sysgo.de> In-Reply-To: <200305221714.h4MHEni25606@dagobert.svc.sysgo.de> Cc: linux-kernel@vger.kernel.org MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200305222230.13587.jcwren@jcwren.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3271 Lines: 84 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: [] [] [] [] > > [] [] [] [] [] > > [] [] [] [] [] > > [] [] [] > > > > 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/ - 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/