lkml.org 
[lkml]   [2003]   [Aug]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
Subject2.6.0-test3-mm2 -- IDE PDC20269 + Maxtor 92048D8
This is off-topic I suppose, since this doesn't seem to be a kernel 
issue...I'm hoping someone can tell me more about how to diagnose the
cause of the problem and/or the probably sequence of commands that lead
up to this.

With this combination of of the Maxtor 92048D8 and the PDC20269, when I
enable dma with "hdparm -d1 /dev/hdi", I'm getting the error as listed
below in my log (plus a nice delay while it times out and then resets
the interface). Usually the first reset does the trick, but sometimes
it has to reset twice. I have two PDC20269 cards in my computer, and I
get this behavior regardless of which card the drive is attached to or
to which channel it is attached. I've tried several cables as well,
currently it is on an 80 conductor cable (though I've tried other "known
good" cables).

The cards are actually Maxtor Ultra133TX2 with the same BIOS versions
(and the only one available from Maxtor). I've tried every DMA mode it
supports, and as soon as I write to the drive in DMA, it will timeout,
reset the interface and disable DMA. After that, it is fine, but
because it is using PIO, the performance is pretty sad. I'm having the
same trouble in WinXP, so I know it's not a Linux issue. However, what
I'd like to know is what would be causing this problem? Just to head
off defective hardware (well, as far as "the drive is going bad"
responses), not too long ago the drive was replaced by Maxtor with the
same model and firmware version which was experiencing the same
problem. The other drive was not "defective" besides this problem with
interacting with the PCD20269. It did work "fine" in UDMA/ATA-33 with
my VIA MVP3 (except for that nasty MVP3 bug that corrupts the data).

I've tried all the different hdparm options for {-m, -c, -u} which had
no effect on the problem.

Has anyone else heard of this problem? Any idea if it is the card or
the drive?

Thanks,

Wes


*****hdparm -i output:
rybBIT:/home/sprchkn # hdparm -i /dev/hdi

/dev/hdi:
HDIO_GETGEO_BIG failed: Invalid argument

Model=Maxtor 92048D8, FwRev=NAN5271A, SerialNo=W8H4D3TA
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=54
BuffType=DualPortCache, BuffSize=1024kB, MaxMultSect=16, MultSect=16
CurCHS=16383/16/63, CurSects=-66060037, LBA=yes, LBAsects=40000464
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2 udma0 udma1 *udma2
AdvancedPM=no
Drive Supports : ATA/ATAPI-4 T13 1153D revision 17 : ATA-1 ATA-2 ATA-3
ATA-4

*****log output when DMA enabled and large transfer to drive (> 1MB):

Aug 19 18:13:59 rybBIT kernel: hdi: dma_timer_expiry: dma status == 0x21
Aug 19 18:14:09 rybBIT kernel: hdi: DMA timeout error
Aug 19 18:14:09 rybBIT kernel: hdi: dma timeout error: status=0x58 {
DriveReady SeekComplete DataRequest }
Aug 19 18:14:09 rybBIT kernel:
Aug 19 18:14:09 rybBIT kernel: hdi: status timeout: status=0xd0 { Busy }
Aug 19 18:14:09 rybBIT kernel:
Aug 19 18:14:09 rybBIT kernel: PDC202XX: Primary channel reset.
Aug 19 18:14:09 rybBIT kernel: hdi: drive not ready for command
Aug 19 18:14:10 rybBIT kernel: ide4: reset: success
Aug 19 18:14:30 rybBIT kernel: hdi: dma_timer_expiry: dma status == 0x21
Aug 19 18:14:40 rybBIT kernel: hdi: DMA timeout error
Aug 19 18:14:40 rybBIT kernel: hdi: dma timeout error: status=0x58 {
DriveReady SeekComplete DataRequest }
Aug 19 18:14:40 rybBIT kernel:
Aug 19 18:14:40 rybBIT kernel: hdi: status timeout: status=0xd0 { Busy }
Aug 19 18:14:40 rybBIT kernel:
Aug 19 18:14:40 rybBIT kernel: PDC202XX: Primary channel reset.
Aug 19 18:14:40 rybBIT kernel: hdi: drive not ready for command
Aug 19 18:14:40 rybBIT kernel: ide4: reset: success
Aug 19 18:15:00 rybBIT kernel: hdi: dma_timer_expiry: dma status == 0x21
Aug 19 18:15:10 rybBIT kernel: hdi: DMA timeout error
Aug 19 18:15:10 rybBIT kernel: hdi: dma timeout error: status=0x58 {
DriveReady SeekComplete DataRequest }
Aug 19 18:15:10 rybBIT kernel:
Aug 19 18:15:10 rybBIT kernel: hdi: status timeout: status=0xd0 { Busy }
Aug 19 18:15:10 rybBIT kernel:
Aug 19 18:15:10 rybBIT kernel: PDC202XX: Primary channel reset.
Aug 19 18:15:10 rybBIT kernel: hdi: drive not ready for command
Aug 19 18:15:10 rybBIT kernel: ide4: reset: success
Aug 19 18:15:30 rybBIT kernel: hdi: dma_timer_expiry: dma status == 0x21
Aug 19 18:15:40 rybBIT kernel: hdi: DMA timeout error
Aug 19 18:15:40 rybBIT kernel: hdi: dma timeout error: status=0x58 {
DriveReady SeekComplete DataRequest }
Aug 19 18:15:40 rybBIT kernel:
Aug 19 18:15:40 rybBIT kernel: hdi: status timeout: status=0xd0 { Busy }
Aug 19 18:15:40 rybBIT kernel:
Aug 19 18:15:40 rybBIT kernel: PDC202XX: Primary channel reset.
Aug 19 18:15:40 rybBIT kernel: hdi: drive not ready for command
Aug 19 18:15:40 rybBIT kernel: ide4: reset: success
Aug 19 18:35:48 rybBIT kernel: hdg: drive_cmd: status=0x01 { Error }
Aug 19 18:35:48 rybBIT kernel: hdg: drive_cmd: error=0x04Aborted Command
Aug 19 18:58:01 rybBIT kernel: hdi: dma_timer_expiry: dma status == 0x21
Aug 19 18:58:11 rybBIT kernel: hdi: DMA timeout error
Aug 19 18:58:11 rybBIT kernel: hdi: dma timeout error: status=0x58 {
DriveReady SeekComplete DataRequest }
Aug 19 18:58:11 rybBIT kernel:
Aug 19 18:58:11 rybBIT kernel: hdi: status timeout: status=0xd0 { Busy }
Aug 19 18:58:11 rybBIT kernel:
Aug 19 18:58:11 rybBIT kernel: PDC202XX: Primary channel reset.
Aug 19 18:58:11 rybBIT kernel: hdi: drive not ready for command
Aug 19 18:58:11 rybBIT kernel: ide4: reset: success
Aug 19 19:05:42 rybBIT kernel: hdi: dma_timer_expiry: dma status == 0x21
Aug 19 19:05:52 rybBIT kernel: hdi: DMA timeout error
Aug 19 19:05:52 rybBIT kernel: hdi: dma timeout error: status=0x58 {
DriveReady SeekComplete DataRequest }
Aug 19 19:05:52 rybBIT kernel:
Aug 19 19:05:52 rybBIT kernel: hdi: status timeout: status=0xd0 { Busy }
Aug 19 19:05:52 rybBIT kernel:
Aug 19 19:05:52 rybBIT kernel: PDC202XX: Primary channel reset.
Aug 19 19:05:52 rybBIT kernel: hdi: drive not ready for command
Aug 19 19:05:52 rybBIT kernel: ide4: reset: success
Aug 19 19:12:32 rybBIT kernel: hdi: dma_timer_expiry: dma status == 0x21
Aug 19 19:12:42 rybBIT kernel: hdi: DMA timeout error
Aug 19 19:12:42 rybBIT kernel: hdi: dma timeout error: status=0x58 {
DriveReady SeekComplete DataRequest }
Aug 19 19:12:42 rybBIT kernel:
Aug 19 19:12:42 rybBIT kernel: hdi: status timeout: status=0xd0 { Busy }
Aug 19 19:12:42 rybBIT kernel:
Aug 19 19:12:42 rybBIT kernel: PDC202XX: Primary channel reset.
Aug 19 19:12:42 rybBIT kernel: hdi: drive not ready for command
Aug 19 19:12:42 rybBIT kernel: ide4: reset: success
Aug 19 19:14:33 rybBIT kernel: hdi: dma_timer_expiry: dma status == 0x21
Aug 19 19:14:43 rybBIT kernel: hdi: DMA timeout error
Aug 19 19:14:43 rybBIT kernel: hdi: dma timeout error: status=0x58 {
DriveReady SeekComplete DataRequest }
Aug 19 19:14:43 rybBIT kernel:
Aug 19 19:14:43 rybBIT kernel: hdi: status timeout: status=0xd0 { Busy }
Aug 19 19:14:43 rybBIT kernel:
Aug 19 19:14:43 rybBIT kernel: PDC202XX: Primary channel reset.
Aug 19 19:14:43 rybBIT kernel: hdi: drive not ready for command
Aug 19 19:14:45 rybBIT kernel: ide4: reset: success





-
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/

\
 
 \ /
  Last update: 2005-03-22 13:47    [W:0.054 / U:5.160 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site