Hi,
Whenever I write a substantial amount of data (200mb) to
disk, I get these messages. The disks lock for about 10
seconds and then come back for about 10 seconds again.
This continues until the data is successfully written.
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hde: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
hde: DMA disabled
hde: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hde: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
hde: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hde: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
hde: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hde: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
Does anyone happen to know what I can do to fix this? It
happens on Linux 2.4.2 as well. It's an HPT370 controler
on-board. Here is the relevant information.
HPT370: IDE controller on PCI bus 00 dev 70
HPT370: chipset revision 3
HPT370: not 100% native mode: will probe irqs later
ide2: BM-DMA at 0xec00-0xec07, BIOS settings: hde:DMA,
hdf:pio
ide3: BM-DMA at 0xec08-0xec0f, BIOS settings: hdg:DMA,
hdh:pio
hde: Maxtor 92720U8, ATA DISK drive
hdg: Maxtor 96147U8, ATA DISK drive
ide2 at 0xdc00-0xdc07,0xe002 on irq 10
ide3 at 0xe400-0xe407,0xe802 on irq 10
hde: Maxtor 92720U8, 25965MB w/2048kB Cache,
CHS=52755/16/63, UDMA(66)
hdg: Maxtor 96147U8, 58623MB w/2048kB Cache,
CHS=119108/16/63, UDMA(66)
continuum:~# cat /proc/ide/hpt366
HPT370 Chipset.
--------------- Primary Channel ---------------- Secondary
Channel -------------
enabled enabled
--------------- drive0 --------- drive1 -------- drive0
---------- drive1 ------
DMA enabled: yes no yes
no
UDMA
DMA
PIO
continuum:~# cat /proc/ide/hde/settings
name value min max
mode
---- ----- --- ---
----
bios_cyl 52755 0
65535 rw
bios_head 16 0 255
rw
bios_sect 63 0 63
rw
breada_readahead 4 0 127
rw
bswap 0 0 1
r
current_speed 68 0 69
rw
file_readahead 124 0
2097151 rw
ide_scsi 0 0 1
rw
init_speed 68 0 69
rw
io_32bit 1 0 3
rw
keepsettings 1 0 1
rw
lun 0 0 7
rw
max_kb_per_request 64 1 127
rw
multcount 8 0 8
rw
nice1 1 0 1
rw
nowerr 0 0 1
rw
number 0 0 3
rw
pio_mode write-only 0 255
w
slow 0 0 1
rw
unmaskirq 1 0 1
rw
using_dma 1 0 1
rw
--
Shane Wegner: [email protected]
http://www.cm.nu/~shane/
PGP: 1024D/FFE3035D
A0ED DAC4 77EC D674 5487
5B5C 4F89 9A4E FFE3 035D
Shane Wegner wrote:
>
> Hi,
>
> Whenever I write a substantial amount of data (200mb) to
> disk, I get these messages. The disks lock for about 10
> seconds and then come back for about 10 seconds again.
> This continues until the data is successfully written.
>
> ide_dmaproc: chipset supported ide_dma_timeout func only: 14
> hde: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
> hde: DMA disabled
It looks like you have set your drive for a dma mode it doesn't support.
HTH
Mike
No this error is not by the wrong DMA settings. If you have a drive in dma
mode 5 and the controller does not support it, the kernel will give you a
proper error saying that this dma mode is not supported by the
controller. This is most likly something with the kernel. I'd try
upgrading to the latest 2.4.2-ac?? series.
Let me know if I'm mistaken about this one guys...
Jasmeet
At 06:14 PM 3/5/2001 -0800, Mike Fedyk wrote:
>Shane Wegner wrote:
> >
> > Hi,
> >
> > Whenever I write a substantial amount of data (200mb) to
> > disk, I get these messages. The disks lock for about 10
> > seconds and then come back for about 10 seconds again.
> > This continues until the data is successfully written.
> >
> > ide_dmaproc: chipset supported ide_dma_timeout func only: 14
> > hde: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
> > hde: DMA disabled
>It looks like you have set your drive for a dma mode it doesn't support.
>
>HTH
>
>Mike
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to [email protected]
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
- - -
Jasmeet Sidhu
Unix Systems Administrator
ArrayComm, Inc.
[email protected]
http://www.arraycomm.com