On Tue, 23 Nov 2004 11:19:11 -0500, linux r <linuxr@xxxxxxxxx> wrote:
> On Tue, 23 Nov 2004 11:01:55 -0500, Paul Tomblin <ptomblin@xxxxxxxxx> wrote:
> > A quick show of hands here:
> > - Do you run Fedora Core 3 with multiple ATA-66 or ATA-100 drives?
> > - If so, how are they jumpered and cabled?
> > - Can you do large fetches and writes to the second drive without
> > getting DMA errors?
> Why don't you post your partition layout as well as the specific
> verbiage of the errors so we can all have a look.
The most common error is
hdc: dma_timer_expiry: dma status == 0x21
althoguh sometimes I see
Nov 13 23:15:12 allhats kernel: hdc: dma_timer_expiry: dma status == 0x61
Nov 13 23:15:22 allhats kernel: hdc: DMA timeout error
Nov 13 23:15:22 allhats kernel: hdc: dma timeout error: status=0xd0 { Busy }
Nov 13 23:15:22 allhats kernel:
Nov 13 23:15:22 allhats kernel: ide: failed opcode was: unknown
Nov 13 23:15:22 allhats kernel: hdc: DMA disabled
Nov 13 23:15:22 allhats kernel: hdd: DMA disabled
Nov 13 23:15:22 allhats kernel: ide1: reset: success
Nov 13 23:15:32 allhats kernel: hdc: lost interrupt
Nov 13 23:16:12 allhats last message repeated 4 times
Nov 13 23:17:22 allhats last message repeated 7 times
Nov 13 23:18:12 allhats last message repeated 5 times
Nov 13 23:18:18 allhats kernel: hdc: status error: status=0x58 { DriveReady Seek
Complete DataRequest }
Nov 13 23:18:18 allhats kernel:
Nov 13 23:18:18 allhats kernel: ide: failed opcode was: unknown
Nov 13 23:18:18 allhats kernel: hdc: drive not ready for command
Nov 13 23:18:18 allhats kernel: hdd: status timeout: status=0xd0 { Busy }
Nov 13 23:18:18 allhats kernel: hdd: status timeout: error=0xd0LastFailedSense 0
x0d
Nov 13 23:18:18 allhats kernel: hdd: drive not ready for command
Nov 13 23:18:48 allhats kernel: hdd: ATAPI reset timed-out, status=0xd0
Nov 13 23:18:48 allhats kernel: ide1: reset: success
Nov 13 23:19:13 allhats kernel: hdc: dma_timer_expiry: dma status == 0x21
Nov 13 23:19:23 allhats kernel: hdc: DMA timeout error
Nov 13 23:19:23 allhats kernel: hdc: dma timeout error: status=0xd0 { Busy }
Nov 13 23:19:23 allhats kernel:
Nov 13 23:19:23 allhats kernel: ide: failed opcode was: unknown
Nov 13 23:19:23 allhats kernel: hdc: DMA disabled
Nov 13 23:19:23 allhats kernel: ide1: reset: success
Nov 13 23:19:48 allhats kernel: hdc: dma_timer_expiry: dma status == 0x21
Nov 13 23:19:58 allhats kernel: hdc: DMA timeout error
Nov 13 23:19:58 allhats kernel: hdc: dma timeout error: status=0xd0 { Busy }
>
> >>the 2.6 kernel seems unable to deal with it.
> Again can you be more specific with regards to the error messages?
>
> Also why don't you see what the latest Knoppix does with it, (3.6)
> that should help for comparison of kernels anyway.
I boot in straight Knoppix, which boots a 2.4 kernel, and I can mount
the partition and do the following command
find /mnt/hdb4 -type f -print
with no problems. I boot from the same CD using the "knoppix26" boot
argument to get a 2.6 kernel, mount the drive as before, and this time
the find command gets about 30% of the way through the file listing
and hangs.
--
"To announce that there must be no criticism of the president, or that we
are to stand by the president, right or wrong, is not only unpatriotic and
servile, but is morally treasonable to the American public." -- Teddy Roosevelt
