* Still flaky (Re: Crashing with Abit KT7, 2.2.19+ide patches)
[not found] ` <Pine.LNX.4.10.10108280029480.19311-100000@coffee.psychology.mcmaster.ca>
@ 2001-08-30 22:39 ` Nicholas Lee
2001-08-31 0:01 ` Tim Moore
0 siblings, 1 reply; 4+ messages in thread
From: Nicholas Lee @ 2001-08-30 22:39 UTC (permalink / raw)
To: Mark Hahn; +Cc: linux-kernel
I guess I spoke to soon:
Aug 31 09:53:20 hoppa -- MARK --
Aug 31 10:03:15 hoppa kernel: hda: irq timeout: status=0xd0 { Busy }
Aug 31 10:03:28 hoppa kernel: ide0: reset: success
Aug 31 10:03:28 hoppa cups-lpd[1938]: Connection from unknown (192.168.xxx.xxx).
Also some logs on the console that didn't make it to /var/log/messages,
but dmesg got them:
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: timeout waiting for DMA
hda: ide_dma_timeout: Lets do it again!stat = 0xd0, dma_stat = 0x20
hda: set_drive_speed_status: status=0xd0 { Busy }
ide0: Drive 0 didn't accept speed setting. Oh, well.
hda: irq timeout: status=0x80 { Busy }
hda: DMA disabled
hda: ide_set_handler: handler not null; old=c018f5cc, new=c018f5cc
bug: kernel timer added twice at c018f476.
ide0: reset: success
hda: irq timeout: status=0xd0 { Busy }
ide0: reset: success
The last two lines being:
Aug 31 10:03:15 hoppa kernel: hda: irq timeout: status=0xd0 { Busy }
Aug 31 10:03:28 hoppa kernel: ide0: reset: success
All very similar to:
Aug 29 04:37:15 hoppa kernel: hda: timeout waiting for DMA
Aug 29 04:37:15 hoppa kernel: hda: ide_dma_timeout: Lets do it again!stat = 0xd0, dma_stat = 0x20
Aug 29 04:37:15 hoppa kernel: hda: irq timeout: status=0x80 { Busy }
Aug 29 04:37:15 hoppa kernel: hda: DMA disabled
Aug 29 04:37:15 hoppa kernel: hda: ide_set_handler: handler not null; old=c018f5cc, new=c018f5cc
Aug 29 04:37:15 hoppa kernel: bug: kernel timer added twice at c018f476.
Aug 29 04:37:18 hoppa kernel: ide0: reset: success
Which occur just before the cable was checked and replaced with a new one on:
Aug 29 08:13:21 hoppa syslogd 1.3-3#33.1: restart.
Aug 29 08:13:21 hoppa kernel: klogd 1.3-3#33.1, log source = /proc/kmsg started.
Note this occured when;
Aug 31 10:03:28 hoppa cups-lpd[1938]: Connection from unknown (192.168.xxx.xxx).
A incomming print job started, plus a samba job opening a file:
(smbstatus line)
Locked files:
Pid DenyMode R/W Oplock Name
--------------------------------------------------
....
1894 DENY_WRITE RDWR EXCLUSIVE+BATCH ....filename... Fri Aug 31 10:02:22 2001
Plus the ongoing IPSec + IP forwarding. Although 50% of the disk IO
on it before was moved on the 29th to another machine.
This is with a new cable, plugged end to end, well seated. 2.2.19 kernel+ide patches.
That event did turn off pretty much everything on the drive:
[nic@hoppa:~] sudo hdparm -v /dev/hda
/dev/hda:
multcount = 0 (off)
I/O support = 0 (default 16-bit)
unmaskirq = 0 (off)
using_dma = 0 (off)
keepsettings = 0 (off)
nowerr = 0 (off)
readonly = 0 (off)
readahead = 8 (on)
geometry = 2480/255/63, sectors = 39851760, start = 0
Should I be justified in thinking that the either the VIA or Seagate stuff is
causing this pain. Or is it someone doing voodoo magic? Of course the
new cable I received might be crap as well.
It seems to be that the system isn't handling disk and network IO DMA
very well. Could it be related to the tulip driver as well?
tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov
eth1: Digital DS21143 Tulip rev 65 at 0xd000, 00:80:C8:CF:B6:D1, IRQ 5.
....
Nicholas
^ permalink raw reply [flat|nested] 4+ messages in thread