> Hi,
> I found the juicy bits below in my kernel log yesterday: I'm not
> sure whether they represent a hardware or software problem.
Hardware.
> The system in question is a Cyrix PR166+, with 80MB Ram, 3
> harddisks, running a fairly standard debian hamm.
> As far as I can tell, I was recording wav files using gramofile 1.4,
> and tkmixer. The soundcard in question is a standard soundblaster
> 16, and it's the only pnp device in the machine.
> hdb is my windows and swap device. Haven't checked but I don't
> think I needed to go into swap at that moment.
> Any suggestions as to what I'm looking at here ? A disk about to go
> boom ? Or is this normal ?
Not quite and could be harmful or harmless. What this means: IDE Linux driver
ask your hdd to write something on disk. Disk did not resport so driver
disabled DMA and resetted your HDD. Sometimes this is harmless message
in log, sometimes this means that your HDD (or your IDE chipset) does not
support DMA properly. Usually it DOES NOT mean that drive is about to go boom...
> Thanks for any help.
> TimT.
> kern.log:
> Jan 18 18:28:28 dibbler kernel: hda: status timeout: status=0xd0 { Busy }
> Jan 18 18:28:28 dibbler kernel: hdb: disabled DMA
> Jan 18 18:28:28 dibbler kernel: hda: no DRQ after issuing WRITE
> Jan 18 18:28:28 dibbler kernel: ide0: reset: success
> Jan 18 18:28:54 dibbler kernel: Sound: Recording overrun
> Jan 18 18:39:56 dibbler kernel: hda: status timeout: status=0xd0 { Busy }
> Jan 18 18:39:56 dibbler kernel: hda: no DRQ after issuing WRITE
> Jan 18 18:39:56 dibbler kernel: ide0: reset: success
> Jan 18 18:42:52 dibbler kernel: hda: status timeout: status=0xd0 { Busy }
> Jan 18 18:42:52 dibbler kernel: hda: no DRQ after issuing WRITE
> Jan 18 18:42:52 dibbler kernel: ide0: reset: success
> Jan 18 18:44:28 dibbler kernel: hda: status timeout: status=0xd0 { Busy }
> Jan 18 18:44:28 dibbler kernel: hda: no DRQ after issuing WRITE
> Jan 18 18:44:28 dibbler kernel: ide0: reset: success
> Jan 18 19:56:41 dibbler kernel: Warning: dev (03:02) tty->count(1) != #fd's(2) in do_tty_hangup
> Jan 18 20:12:32 dibbler kernel: hda: status timeout: status=0xd0 { Busy }
> Jan 18 20:12:32 dibbler kernel: hda: no DRQ after issuing WRITE
> Jan 18 20:12:32 dibbler kernel: ide0: reset: success
> Jan 18 20:14:22 dibbler kernel: hda: status timeout: status=0xd0 { Busy }
> Jan 18 20:14:22 dibbler kernel: hda: no DRQ after issuing WRITE
> Jan 18 20:14:22 dibbler kernel: ide0: reset: success
> Jan 18 20:45:13 dibbler kernel: Warning: dev (03:03) tty->count(1) != #fd's(2) in do_tty_hangup
> Jan 18 20:54:09 dibbler kernel: hda: status timeout: status=0xd0 { Busy }
> Jan 18 20:54:09 dibbler kernel: hda: no DRQ after issuing WRITE
> Jan 18 20:54:09 dibbler kernel: ide0: reset: success
> Possibly useful bits from dmesg:
> Sound initialization started
> <Sound Blaster 16 (4.13)> at 0x220 irq 5 dma 1,5
> <Sound Blaster 16> at 0x330 irq 5
> <Yamaha OPL3 FM> at 0x388
> Sound initialization complete
> ide: i82371 PIIX (Triton) on PCI bus 0 function 57
> ide0: BM-DMA at 0xf000-0xf007
> ide1: BM-DMA at 0xf008-0xf00f
> hda: Conner Peripherals 1275MB - CFS1275A, 1219MB w/64kB Cache, CHS=2477/16/63
> hdb: Maxtor 7546 AT, 522MB w/256kB Cache, CHS=1060/16/63, DMA
> hdc: QUANTUM BIGFOOT_CY6480A, 6204MB w/67kB Cache, CHS=13446/15/63
> hdd: PHILIPS CDD3610 CD-R/RW, ATAPI CDROM drive - enabling SCSI emulation
> ATAPI overlap supported: No
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> ide1 at 0x170-0x177,0x376 on irq 15
> ----------------------------------------------------------------------------
> tim.timmerman@asml.nl Tel: (Int+031)-(0)40-2303613
> timt@dibbler.iaehv.nl Voodoo Programmer/Keeper of the Rubber Chicken
> Diplomacy: saying "Nice doggy" until you can find a rock.
> ----------------------------------------------------------------------------
> -
> 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/
-
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/