I noticed these in the log just before the point my machine locked hard up
hard. (It's a BP6 so the hangs are expected).
Jun 8 22:49:47 babbage kernel: hdc: timeout waiting for DMA
Jun 8 22:49:47 babbage kernel: ide_dmaproc: chipset supported
ide_dma_timeout func only: 12
Jun 8 22:49:47 babbage kernel: hdc: irq timeout: status=0xd0 { Busy }
Jun 8 22:49:48 babbage kernel: ide1: reset: success
This is not the first time I saw errors -- in fact this has appeared
almost always when I've used hdc (which I don't do that often):
Jun 8 23:06:33 babbage kernel: hdc: irq timeout: status=0xd0 { Busy }
Jun 8 23:06:33 babbage kernel: ide1: reset: success
Jun 8 23:06:35 babbage kernel: hdc: set_geometry_intr: status=0x58 {
DriveReady Seek Complete DataRequest }
Jun 8 23:06:35 babbage kernel: hdc: status error: status=0x58 {
DriveReady Seek Complete DataRequest }
Jun 8 23:06:35 babbage kernel: hdc: drive not ready for command
Jun 8 23:06:35 babbage kernel: hdc: status error: status=0x58 {
DriveReady Seek Complete DataRequest }
Jun 8 23:06:35 babbage kernel: hdc: drive not ready for command
Jun 8 23:06:35 babbage kernel: hdc: status error: status=0x58 {
DriveReady Seek Complete DataRequest }
Jun 8 23:06:35 babbage kernel: hdc: drive not ready for command
Jun 8 23:06:35 babbage kernel: ide1: reset: success
Usually, it seemed to be harmless, after a little delay it works again. I
just begun suspect that might have something to do with the lockup. I
dropped all the dma stuff off for hdc, but the errors still appear. After
some reboots and hdparm -tT's it seems that hdparm -tT /dev/hdc is quite
likely to cause the errors and lockups (the machine locked up three times
when doing hdparm -tT /dev/hcd). Other drives work well.
hdc is on (of course) IDE1 (PIIX, not HPT366), and hdparm says:
root@babbage:/home/vherva>hdparm -i /dev/hdc
/dev/hdc:
Model=ST36451A, FwRev=840394, SerialNo=JG332185
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
RawCHS=13328/15/63, TrkSize=36540, SectSize=580, ECCbytes=4
BuffType=DualPortCache, BuffSize=448kB, MaxMultSect=16, MultSect=off
CurCHS=13328/15/63, CurSects=789577920, LBA=yes, LBAsects=12594960
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 udma0 udma1 *udma2
root@babbage:/home/vherva>hdparm /dev/hdc
/dev/hdc:
multcount = 0 (off)
I/O support = 0 (default 16-bit)
unmaskirq = 0 (off)
using_dma = 0 (off)
keepsettings = 1 (on)
nowerr = 0 (off)
readonly = 0 (off)
readahead = 8 (on)
geometry = 784/255/63, sectors = 12594960, start = 0
In the same bus, there is a CDRW:
root@babbage:/home/vherva>hdparm /dev/hdd
/dev/hdd:
HDIO_GET_MULTCOUNT failed: Input/output error
I/O support = 0 (default 16-bit)
unmaskirq = 0 (off)
using_dma = 0 (off)
keepsettings = 0 (off)
HDIO_GET_NOWERR failed: Input/output error
readonly = 0 (off)
BLKRAGET failed: Input/output error
HDIO_GETGEO failed: Invalid argument
root@babbage:/home/vherva>hdparm -i /dev/hdd
/dev/hdd:
Model=CR-4804TE, FwRev=2.4C, SerialNo=
Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic }
RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
BuffType=DualPort, BuffSize=0kB, MaxMultSect=0
(maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
IORDY=on/off, tPIO={min:240,w/IORDY:180}, tDMA={min:180,rec:180}
PIO modes: pio0 pio1 pio2 pio3
DMA modes: sdma0 sdma1 mdma0 *mdma1
BTW, when doing hdparm -i /dev/hdd I also got
Jun 8 23:08:58 babbage kernel: hdd: drive_cmd: status=0x41 { DriveReady Error }
Jun 8 23:08:58 babbage kernel: hdd: drive_cmd: error=0x04
The IBMs on hda and hde (HPT366) work just flawlessly.
Kernel version 2.2.16pre5 + Hedricks IDE patch. I've been getting these
errors at least since 2.2.13.
I had the drive on a P166 some time ago, but I had no trouble with it.
-- v --
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Jun 15 2000 - 21:00:18 EST