From owner-freebsd-questions@FreeBSD.ORG Sun May 2 11:25:23 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 098C416A4CE for ; Sun, 2 May 2004 11:25:23 -0700 (PDT) Received: from lurch.noc.sgi.net (lurch.noc.sgi.net [208.40.181.204]) by mx1.FreeBSD.org (Postfix) with SMTP id 412EA43D48 for ; Sun, 2 May 2004 11:25:22 -0700 (PDT) (envelope-from streiner@stargate.net) Received: (qmail 26110 invoked by uid 100); 2 May 2004 18:22:12 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 2 May 2004 18:22:12 -0000 Date: Sun, 2 May 2004 14:22:12 -0400 (EDT) From: "Streiner, Justin" X-X-Sender: streiner@lurch To: freebsd-questions@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: READ_BIG errors continue, atapi-cd driver updates? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 May 2004 18:25:23 -0000 When copying data from a CD burned on my Windows machine, I see lots of errors like the ones at the end of this message continue to pop up in dmesg. I saw these on my old machine as well, but was surprised when I continued to see them on my new machine. I saw some references to similar errors in other freebsd mailing lists and there was mention of a patch to atapi-cd.c that worked well for some people, but the patch for atapi-cd.c doesn't seem to match up with the atapi-cd.c on my machine. Has this patch been integrated into the stock 5.2.1 distribution? More about the patch in question may be found at the URL below: www.atm.tut.fi/list-archive/freebsd-stable/msg02702.html This machine is running freebsd 5.2.1 - several parts have been portupgrade'd since the initial OS install. I have a lot of data to move onto this machine, most of it is currently stored on burned CDs, so I really need to find a solution to this problem. jms vm_fault: pager read error, pid 80512 (cp) vm_fault: pager read error, pid 80512 (cp) vm_fault: pager read error, pid 80512 (cp) acd1: FAILURE - READ_BIG status=51 sensekey=MEDIUM ERROR error=4 vm_fault: pager read error, pid 80527 (cp) acd1: FAILURE - READ_BIG status=51 sensekey=MEDIUM ERROR error=4 vm_fault: pager read error, pid 80527 (cp) vm_fault: pager read error, pid 80527 (cp) vm_fault: pager read error, pid 80527 (cp) acd1: FAILURE - READ_BIG status=51 sensekey=MEDIUM ERROR error=4 vm_fault: pager read error, pid 80527 (cp)