From owner-freebsd-current Fri Dec 6 13:35:48 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5992E37B401 for ; Fri, 6 Dec 2002 13:35:47 -0800 (PST) Received: from ns3.safety.net (ns3.safety.net [216.40.201.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED90A43EC2 for ; Fri, 6 Dec 2002 13:35:46 -0800 (PST) (envelope-from cbiffle@safety.net) Received: from localhost (rs.rackshack.net.safety.net [216.40.201.32]) by ns3.safety.net (8.10.2/8.10.2) with ESMTP id gB6LZkO27491 for ; Fri, 6 Dec 2002 14:35:46 -0700 From: "Cliff L. Biffle" To: freebsd-current@freebsd.org Subject: ATACD issues slowly coming back... Date: Fri, 6 Dec 2002 14:35:45 -0700 User-Agent: KMail/1.5 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200212061435.45583.cbiffle@safety.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I mentioned earlier on the list that the ATA issues I'd been having with 4.7 had disappeared since installing 5.0. They're still much less frequent -- i.e. I can burn CDs now -- but I just got one of the old messages and wanted to submit it for your perusal. cliff50 kernel: acd0: READ_BIG - MEDIUM ERROR asc=0x11 ascq=0x00 error=0x00 I'm not well versed on the ATA command set, but that looks like a command to the drive failing to execute. Is this likely to be the drive, the controller, both, or is it impossible to tell from the data set? This is on the aforementioned potentially-buggy Apollo KT133 chipset, but it's never reported these errors on my hard disk (knock on wood), only the CD drive. They -are- on separate channels. I'll see what information I can collect here, but suggestions on where to look are appreciated. -Cliff L. Biffle To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message