From owner-freebsd-stable Fri Dec 28 7:43:22 2001 Delivered-To: freebsd-stable@freebsd.org Received: from D00015.dialonly.kemerovo.su (www2.svzserv.kemerovo.su [213.184.65.86]) by hub.freebsd.org (Postfix) with ESMTP id 90DFD37B422; Fri, 28 Dec 2001 07:43:09 -0800 (PST) Received: (from eugen@localhost) by D00015.dialonly.kemerovo.su (8.11.6/8.11.4) id fBS2mRS00254; Fri, 28 Dec 2001 09:48:28 +0700 (KRAT) (envelope-from eugen) Date: Fri, 28 Dec 2001 09:48:27 +0700 From: Eugene Grosbein To: qa@freebsd.org Cc: stable@freebsd.org Subject: 4.5-PRERELEASE (25 Dec) and IBM IC35L040AVER07-0 Message-ID: <20011228094827.A210@grosbein.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi! I'm testing my new hard drive IBM IC35L040AVER07-0 40 Gb with 4.5-PRESELEASE copying 700M movie file from SONY CD-RW CRX140E. My motherboard is Iwill BD100Plus 440BX (ATA 33). ad2: 39266MB [79780/16/63] at ata1-master tagged UDMA33 acd1: CD-RW at ata1-slave using UDMA33 I mount CD-RW (iso9660 filesystem) and copy file using Midnight Commander. In the middle of copying I get these messages written to console: ad2: READ command timeout tag=0 serv=0 - resetting ad2: invalidating queued requests ata1: resetting devices .. ad2: invalidating queued requests done ad2: no request for this tag=0?? ad2: invalidating queued requests ad2: READ command timeout tag=0 serv=0 - resetting ad2: invalidating queued requests ata1: resetting devices .. ad2: invalidating queued requests done ad2: no request for this tag=0?? ad2: invalidating queued requests ad2: READ command timeout tag=0 serv=0 - resetting ad2: invalidating queued requests ata1: resetting devices .. ad2: invalidating queued requests done ad2: no request for this tag=0?? ad2: invalidating queued requests ad2: READ command timeout tag=0 serv=0 - resetting ad2: invalidating queued requests ad2: trying fallback to PIO mode ata1: resetting devices .. ad2: invalidating queued requests After fallback to PIO mode system spends 88% of my Celeron-450 for iterrupts. One question: need this be fixed, and if so, how? Eugene Grosbein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message