From owner-freebsd-i386@FreeBSD.ORG Sat Jul 10 21:20:30 2004 Return-Path: Delivered-To: freebsd-i386@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ACA6816A4CE for ; Sat, 10 Jul 2004 21:20:30 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A97143D39 for ; Sat, 10 Jul 2004 21:20:30 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id i6ALKUbU002453 for ; Sat, 10 Jul 2004 21:20:30 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i6ALKU5H002452; Sat, 10 Jul 2004 21:20:30 GMT (envelope-from gnats) Resent-Date: Sat, 10 Jul 2004 21:20:30 GMT Resent-Message-Id: <200407102120.i6ALKU5H002452@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-i386@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, dino Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 53EDA16A4CE for ; Sat, 10 Jul 2004 21:17:46 +0000 (GMT) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CD1843D2D for ; Sat, 10 Jul 2004 21:17:46 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.12.11/8.12.11) with ESMTP id i6ALHksV019716 for ; Sat, 10 Jul 2004 21:17:46 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.12.11/8.12.11/Submit) id i6ALHker019714; Sat, 10 Jul 2004 21:17:46 GMT (envelope-from nobody) Message-Id: <200407102117.i6ALHker019714@www.freebsd.org> Date: Sat, 10 Jul 2004 21:17:46 GMT From: dino To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Subject: i386/68899: Problems reading and writing DVD-RAM discs X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jul 2004 21:20:30 -0000 >Number: 68899 >Category: i386 >Synopsis: Problems reading and writing DVD-RAM discs >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-i386 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Jul 10 21:20:30 GMT 2004 >Closed-Date: >Last-Modified: >Originator: dino >Release: 5.2.1 >Organization: Balston Research LLC >Environment: FreeBSD medea.digitalescorts.net 5.2.1-RELEASE FreeBSD 5.2.1-RELEASE #7: Sat Jul 10 12:41:34 EDT 2004 root@medea.digitalescorts.net:/usr/obj/usr/src/sys/MEDEA i386 >Description: Let me start by stating that i have ATAPICAM compiled into the kernel. Now, I am able to 'mount_udf /dev/acd0 /mnt'. However, if the dvd-ram media is formated w/ UDF2 and I attempt to 'cat' or 'cp' a file ('ls' seems to work okay) the error message 'cannot allocate memory' is returned. If the dvd-ram is formatted w/ UDF1.5 I am able to cat/cp MOST files. Unfortunately, trying to cp/cat certain files (maybe 'cause they are large?) results in the entire system crashing/rebooting automagically (ugh!). In addition, the disc gets corrupted (I tried copying a file from a directory on the DVD-RAM and after the crash/reboot I was no longer able to even ls the directory that the file was contained in, some kind of 'input/output error'). >How-To-Repeat: Well, you may or may not need specific hardware (MATSHITA DVD-RAM SW-9571 A111). Insert a dvd-ram disc that is formated UDF2, mount_udf it, then try 'cat file_on_dvd_ram'; the message displayed is 'cannot allocate memory'. Also, insert a dvd-ram disc that is formatted UDF1.5, mount_udf it, then try 'cp large_file_on_dvd_ram some_dir_on_hd' with various large files; eventually the system should crash and reboot, your dvd-ram will be corrupted. >Fix: dunno >Release-Note: >Audit-Trail: >Unformatted: