From owner-freebsd-multimedia Sun Sep 23 23:46:22 2001 Delivered-To: freebsd-multimedia@freebsd.org Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114]) by hub.freebsd.org (Postfix) with ESMTP id E657A37B40C for ; Sun, 23 Sep 2001 23:46:17 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.11.3/8.11.3) id f8O6kEY86383; Mon, 24 Sep 2001 08:46:14 +0200 (CEST) (envelope-from sos) From: Søren Schmidt Message-Id: <200109240646.f8O6kEY86383@freebsd.dk> Subject: Re: Trouble with DVD Movies In-Reply-To: <3BAE842D.DC465D7D@sm.socccd.cc.ca.us> "from Farooq Mela at Sep 23, 2001 05:54:05 pm" To: Farooq Mela Date: Mon, 24 Sep 2001 08:46:14 +0200 (CEST) Cc: FreeBSD-Multimedia@FreeBSD.ORG Reply-To: sos@freebsd.dk X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org It seems Farooq Mela wrote: > "Søren Schmidt" wrote: > > and disc proberly. You need "something" to do the CSS dance > > with the drive and the media, such code should exist I'm told.... > > OK, I got that figured out. However, I still get fatal kernel traps > when reading some of the .vobs :-( > > (Hand copied because I don't have a serial line to my box) > > ata1-slave: too many segments in DMA table Thats because the ATA driver is called with bogus parameters, most likely from the fs code because it has gotten bad data from a failed DMA read that returned corrupted data. > However it has DMA enabled from /etc/sysctl.conf and hw.atamodes. The > fatal kernel trap takes place as soon as the css-cat (just reads file > off dvd, css descrambles) program gets to the last parts of the .vob > file. I also tried using PIO, it also resulted in a page fault in > kernel, but it just took a lot longer :-) (don't have the panic info > from that one sorry). The interesting thing is that this only happens > from reading the fourth .vob file (each is almost 1GB). I am not sure, > does the 0x3a mean it is trying to access virtual memory at 0x3a in > the kernel? Your drive/controller combination apparently doesn't support ATAPI DMA, thats unfortunately true for ALOT of ATAPI devices and controllers. It should not fail when using PIO mode, but we need more info to tell whats going on (dmesg, panic mesg, and possibly a stack trace) I just checked on both -stable and -current here, and it does work. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message