From: "Dwayne Rightler" <drightler@technicalogic.com>
To: "Piszcz, Justin Michael" <justin.piszcz@mitretek.org>,
<linux-kernel@vger.kernel.org>
Cc: "Dhruv Matani" <dhruvbird@gmx.net>
Subject: Re: DriveReady SeekComplete Error...
Date: Wed, 14 Jul 2004 15:10:11 -0500 [thread overview]
Message-ID: <011601c469de$9456f700$010a300a@drightler2k> (raw)
In-Reply-To: 2E314DE03538984BA5634F12115B3A4E62E88D@email1.mitretek.org
[-- Attachment #1: Type: text/plain, Size: 7297 bytes --]
demigod:/proc/ide/hda# cat model
SAMSUNG SV2044D
lspci -vvv output is attached. /dev/hda is attached to the VIA chipset. I
have another hard drive /dev/hdb and a cdrom drive /dev/hdc connected to
that chipset as well and they can do DMA transfers.
The Promise controller has 2 hard drives hooked to it which can also do DMA
transfers.
Thanks,
Dwayne
----- Original Message -----
From: "Piszcz, Justin Michael" <justin.piszcz@mitretek.org>
To: "Dwayne Rightler" <drightler@technicalogic.com>;
<linux-kernel@vger.kernel.org>
Cc: "Dhruv Matani" <dhruvbird@gmx.net>
Sent: Tuesday, July 13, 2004 12:23 PM
Subject: RE: DriveReady SeekComplete Error...
> Hrmm, does anyone else have that same drive or chipset you use, do they
> also experience the problem?
>
> What is the exact model of the drive and what chipset do you use?
>
> cd /proc/ide/hda ; cat model
>
> lspci -vvv # as root
>
> -----Original Message-----
> From: Dwayne Rightler [mailto:drightler@technicalogic.com]
> Sent: Tuesday, July 13, 2004 11:58 AM
> To: Piszcz, Justin Michael; linux-kernel@vger.kernel.org
> Cc: Dhruv Matani
> Subject: Re: DriveReady SeekComplete Error...
>
> The CONFIG_IDEDISK_MULTI_MODE setting makes no difference as seen below:
>
> demigod:~# uname -a
> Linux demigod 2.6.7-kexec #2 Tue Jul 13 08:31:56 CDT 2004 i686 GNU/Linux
>
> demigod:~# zgrep CONFIG_IDEDISK_MULTI_MODE /proc/config.gz
> CONFIG_IDEDISK_MULTI_MODE=y
>
> demigod:~# dmesg | grep ^hda
> hda: SAMSUNG SV2044D, ATA DISK drive
> hda: max request size: 128KiB
> hda: 39862368 sectors (20409 MB) w/472KiB Cache, CHS=39546/16/63
> hda: DMA disabled
> hda: dma_timer_expiry: dma status == 0x61
> hda: DMA timeout error
> hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> DataRequest }
> hda: dma_timer_expiry: dma status == 0x61
> hda: DMA timeout error
> hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> DataRequest }
> hda: dma_timer_expiry: dma status == 0x61
> hda: DMA timeout error
> hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> DataRequest }
> hda: DMA disabled
>
> ##########################################
>
> demigod:~# uname -a
> Linux demigod 2.6.7-kexec #1 Mon Jul 5 11:30:36 CDT 2004 i686 GNU/Linux
>
> demigod:~# zgrep CONFIG_IDEDISK_MULTI_MODE /proc/config.gz
> # CONFIG_IDEDISK_MULTI_MODE is not set
>
> demigod:~# dmesg | grep ^hda
> hda: SAMSUNG SV2044D, ATA DISK drive
> hda: max request size: 128KiB
> hda: 39862368 sectors (20409 MB) w/472KiB Cache, CHS=39546/16/63
> hda: DMA disabled
> hda: dma_timer_expiry: dma status == 0x61
> hda: DMA timeout error
> hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> DataRequest }
> hda: dma_timer_expiry: dma status == 0x61
> hda: DMA timeout error
> hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> DataRequest }
> hda: DMA disabled
> hda: dma_timer_expiry: dma status == 0x41
> hda: DMA timeout error
> hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> DataRequest }
> hda: dma_timer_expiry: dma status == 0x61
> hda: DMA timeout error
> hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> DataRequest }
> ----- Original Message -----
> From: "Piszcz, Justin Michael" <justin.piszcz@mitretek.org>
> To: "Dwayne Rightler" <drightler@technicalogic.com>;
> <linux-kernel@vger.kernel.org>
> Cc: "Dhruv Matani" <dhruvbird@gmx.net>
> Sent: Tuesday, July 13, 2004 7:44 AM
> Subject: RE: DriveReady SeekComplete Error...
>
>
> > <*> Include IDE/ATA-2 DISK support
> > [*] Use multi-mode by default
> >
> > Have you tried recompiling the kernel and checking off the second
> option
> > show above?
> >
> > CONFIG_IDEDISK_MULTI_MODE
> > If you get this error, try to say Y here:
> > hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
> > hda: set_multmode: error=0x04 { DriveStatusError }
> > If in doubt, say N.
> >
> >
> > -----Original Message-----
> > From: linux-kernel-owner@vger.kernel.org
> > [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Dwayne
> Rightler
> > Sent: Tuesday, July 13, 2004 8:33 AM
> > To: linux-kernel@vger.kernel.org
> > Cc: Dhruv Matani
> > Subject: Re: DriveReady SeekComplete Error...
> >
> > I have a similar problem with a Samsung hard drive. Model SV2044D.
> The
> > output of 'hdparm -i' below indicates it supports several multiword
> and
> > ultra DMA modes but if i run the drive in anything other than PIO mode
> > it
> > gets DMA timeouts and SeekComplete Errors. This has been on every
> > kernel I
> > can recall in the 2.4 and 2.6 series.
> >
> > demigod:~# hdparm -i /dev/hda
> >
> > /dev/hda:
> >
> > Model=SAMSUNG SV2044D, FwRev=MM200-53, SerialNo=0228J1FN905733
> > Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
> > RawCHS=16383/16/63, TrkSize=34902, SectSize=554, ECCbytes=4
> > BuffType=DualPortCache, BuffSize=472kB, MaxMultSect=16, MultSect=16
> > CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=39862368
> > IORDY=yes, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
> > PIO modes: pio0 pio1 pio2 pio3 pio4
> > DMA modes: mdma0 mdma1 mdma2
> > UDMA modes: udma0 udma1 udma2 udma3 *udma4
> > AdvancedPM=no WriteCache=enabled
> > Drive conforms to: ATA/ATAPI-4 T13 1153D revision 17: 1 2 3 4
> >
> > * signifies the current active mode
> >
> >
> >
> > ----- Original Message -----
> > From: "Dhruv Matani" <dhruvbird@gmx.net>
> > To: <linux-kernel@vger.kernel.org>
> > Sent: Tuesday, July 13, 2004 7:30 AM
> > Subject: DriveReady SeekComplete Error...
> >
> >
> > > Hi,
> > > I've been getting this error for my brand new (2 months old) Samsung
> > > HDD. The model Number is: SV0411N, and it is a 40GB disk. I'm using
> > the
> > > kernel version 2.4.20-8 provided by RedHat. When I used
> RH-7.2(before
> > > upgrading to RH-9), the same HDD worked fine. Also, when I
> > re-installed
> > > RH-7.2, it worked fine?
> > >
> > > Any suggestions?
> > >
> > > Please cc me the reply, sine I'm not subscribed.
> > > Thanks ;-)
> > >
> > > --
> > > -Dhruv Matani.
> > > http://www.geocities.com/dhruvbird/
> > >
> > > As a rule, man is a fool. When it's hot, he wants it cold.
> > > When it's cold he wants it hot. He always wants what is not.
> > > -Anon.
> > >
> > >
> > > -
> > > 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/
> > -
> > 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/
>
[-- Attachment #2: lspci-output.gz --]
[-- Type: application/x-gzip, Size: 1821 bytes --]
next prev parent reply other threads:[~2004-07-14 20:07 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-13 17:23 DriveReady SeekComplete Error Piszcz, Justin Michael
2004-07-14 20:10 ` Dwayne Rightler [this message]
2004-07-15 4:08 ` Dhruv Matani
2004-07-26 14:32 ` Dhruv Matani
2004-07-26 14:51 ` Dwayne Rightler
2004-08-20 3:22 ` Dhruv Matani
-- strict thread matches above, loose matches on Subject: below --
2004-07-13 12:44 Piszcz, Justin Michael
2004-07-13 15:57 ` Dwayne Rightler
2004-07-13 12:30 Dhruv Matani
2004-07-13 12:32 ` Dwayne Rightler
[not found] ` <40F3D4AC.9050407@gardenali.biz>
2004-07-13 14:27 ` Dhruv Matani
2004-07-13 14:29 ` Dhruv Matani
2004-07-13 14:47 ` Dhruv Matani
2004-07-13 15:01 ` Bartlomiej Zolnierkiewicz
2004-06-04 10:15 mattia
2004-06-04 10:22 ` Jens Axboe
2004-06-04 11:44 ` Bartlomiej Zolnierkiewicz
2004-06-04 11:56 ` Jens Axboe
2004-06-04 12:15 ` Bartlomiej Zolnierkiewicz
2004-06-04 12:17 ` Jens Axboe
2004-06-04 12:40 ` Bartlomiej Zolnierkiewicz
2004-06-04 21:55 ` Ed Tomlinson
2004-06-04 19:58 ` Eric D. Mudama
2004-06-05 13:48 ` mattia
2004-06-04 7:54 Rick Jansen
2004-06-04 9:02 ` Daniel Egger
2004-06-04 9:38 ` John Bradford
2004-06-04 9:43 ` John Bradford
2004-06-04 9:54 ` Rick Jansen
2004-06-04 9:59 ` Jens Axboe
2004-06-04 10:02 ` Rick Jansen
2004-06-04 10:08 ` Jens Axboe
2004-06-04 13:02 ` Andy Hawkins
2004-06-04 13:41 ` Daniel Egger
2004-06-04 13:53 ` Rick Jansen
2004-06-04 14:05 ` John Bradford
2004-06-04 14:18 ` Rick Jansen
2004-06-04 19:32 ` Bruce Allen
2004-06-04 14:15 ` Daniel Egger
2004-06-04 14:09 ` John Bradford
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='011601c469de$9456f700$010a300a@drightler2k' \
--to=drightler@technicalogic.com \
--cc=dhruvbird@gmx.net \
--cc=justin.piszcz@mitretek.org \
--cc=linux-kernel@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