Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263343AbTKFEOy (ORCPT ); Wed, 5 Nov 2003 23:14:54 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263345AbTKFEOy (ORCPT ); Wed, 5 Nov 2003 23:14:54 -0500 Received: from astound-64-85-224-253.ca.astound.net ([64.85.224.253]:8198 "EHLO master.linux-ide.org") by vger.kernel.org with ESMTP id S263343AbTKFEOt (ORCPT ); Wed, 5 Nov 2003 23:14:49 -0500 Date: Wed, 5 Nov 2003 20:13:27 -0800 (PST) From: Andre Hedrick To: "Robert L. Harris" cc: Steven Adams , linux-kernel@vger.kernel.org Subject: Re: no DRQ after issuing WRITE In-Reply-To: <20031106032133.GD19875@rdlg.net> Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3432 Lines: 98 I do not have time to pause and trace/fix the mess. However if you both can kindly finger the last kernel when you did not have this error, it will help constrain the pain. Cheers, Andre Hedrick LAD Storage Consulting Group On Wed, 5 Nov 2003, Robert L. Harris wrote: > > > No answer for you but I've gotten this message also and was hoping > someone would know what/why... > > > Thus spake Steven Adams (steve@drifthost.com): > > > anyone? > > ----- Original Message ----- > > From: > > To: > > Sent: Wednesday, November 05, 2003 2:05 PM > > Subject: hda: no DRQ after issuing WRITE > > > > > > > Hey guys, > > > > > > i keep getting things like this in my dmesg > > > > > > ============================================ > > > hda: status timeout: status=0xd0 { Busy } > > > > > > hda: no DRQ after issuing WRITE > > > ide0: reset: success > > > hda: status timeout: status=0xd0 { Busy } > > > > > > hda: no DRQ after issuing WRITE > > > ide0: reset: success > > > ============================================= > > > > > > From hdparm > > > ============================================ > > > /dev/hda: > > > > > > Model=IC35L080AVVA07-0, FwRev=VA4OA52A, SerialNo=VNC402A4CBRJLA > > > Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs } > > > RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=52 > > > BuffType=DualPortCache, BuffSize=1863kB, MaxMultSect=16, MultSect=off > > > CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=160836480 > > > IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120} > > > PIO modes: pio0 pio1 pio2 pio3 pio4 > > > DMA modes: mdma0 mdma1 mdma2 > > > UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5 > > > AdvancedPM=yes: disabled (255) WriteCache=enabled > > > Drive conforms to: ATA/ATAPI-5 T13 1321D revision 1: 2 3 4 5 > > > ================================================= > > > > > > Ive searched high and low to try find out what this means, all ive found > > > it people keep saying its all different kinds of things.. > > > > > > I was wondering if this means my hdd is drying or is ti a setting? > > > > > > Thanks guys, > > > Steve > > > > > > > > > - > > > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > > > the body of a message to majordomo@vger.kernel.org > > > More majordomo info at http://vger.kernel.org/majordomo-info.html > > > 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.kernel.org > > More majordomo info at http://vger.kernel.org/majordomo-info.html > > Please read the FAQ at http://www.tux.org/lkml/ > > :wq! > --------------------------------------------------------------------------- > Robert L. Harris | GPG Key ID: E344DA3B > @ x-hkp://pgp.mit.edu > DISCLAIMER: > These are MY OPINIONS ALONE. I speak for no-one else. > > Life is not a destination, it's a journey. > Microsoft produces 15 car pileups on the highway. > Don't stop traffic to stand and gawk at the tragedy. > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/