From owner-freebsd-current@FreeBSD.ORG Mon Jul 12 05:12:45 2004 Return-Path: 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 00AA416A4CE for ; Mon, 12 Jul 2004 05:12:45 +0000 (GMT) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id B7AD943D39 for ; Mon, 12 Jul 2004 05:12:44 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP (SSL) id IBA74465; Sun, 11 Jul 2004 22:12:44 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 20B625D08; Sun, 11 Jul 2004 22:12:44 -0700 (PDT) To: Justin Hibbits In-reply-to: Your message of "Sat, 10 Jul 2004 20:05:15 EDT." Date: Sun, 11 Jul 2004 22:12:44 -0700 From: "Kevin Oberman" Message-Id: <20040712051244.20B625D08@ptavv.es.net> cc: freebsd-current@freebsd.org Subject: Re: DVD/CD reading issues with -CURRENT from 2004-06-27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jul 2004 05:12:45 -0000 > From: Justin Hibbits > Date: Sat, 10 Jul 2004 20:05:15 -0400 > Sender: owner-freebsd-current@freebsd.org > > Hi, > > I updated to -CURRENT a couple weeks ago, for various reasons, from > 5.2.1, but now DVD and CD reading is flaking out. When trying to play > DVDs with mplayer, they stop after a random amount of time, probably > after reading a complete buffer. With 'dd', trying to create iso > images of CDs, it stops after a random amount of data is copied. > Attached is the backtrace of a 'dd' run. > > Specs of the system: > > 5.2-CURRENT as of 2004-06-27 > Athlon XP 1800+ > ASUS A7V266-E/A motherboard (VIA KT-266 chipset) > > The 2 drives I tested are: > iomega Zip-CD CD-RW drive (acd0) > Toshiba DVD-ROM (acd1) > > Any more info required, just ask. > > Additional, I'm not on the list, so if you could CC me, that'd be > great, otherwise, I'll just check the archives. I reported this a couple of weeks ago. I had not used the drive heavily for a while, so I don't know exactly when the problem started. I have discovered that accessing the drive again (another mplayer) will release the drive. I suspect that an interrupt may be getting lost, but I'm far from sure. Next time it freezes, try using another program to tickle the drive and see if it frees up. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634