From owner-freebsd-current@FreeBSD.ORG Tue Aug 26 14:32:00 2003 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 09AB816A4BF for ; Tue, 26 Aug 2003 14:32:00 -0700 (PDT) Received: from Stalker.alfacom.net (Stalker.Alfacom.net [193.108.124.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC83443FDF for ; Tue, 26 Aug 2003 14:31:56 -0700 (PDT) (envelope-from vkushnir@Alfacom.net) Received: from kushnir1.kiev.ua (124-141.dialup.Alfacom.net [193.108.124.141]) by Stalker.alfacom.net (8.12.8/8.12.8) with ESMTP id h7QLVpKZ010206 for ; Wed, 27 Aug 2003 00:31:52 +0300 (EEST) Received: from kushnir1.kiev.ua (kushnir1.kiev.ua [10.0.0.1]) by kushnir1.kiev.ua (8.12.9/8.12.9) with ESMTP id h7QLVnaC001772 for ; Wed, 27 Aug 2003 00:31:49 +0300 (EEST) (envelope-from vkushnir@Alfacom.net) Date: Wed, 27 Aug 2003 00:31:49 +0300 (EEST) From: Vladimir Kushnir X-X-Sender: vkushnir@kushnir1.kiev.ua To: "freebsd-current@FreeBSD.ORG" In-Reply-To: <1061921315.626.16.camel@twister> Message-ID: <20030827002246.F904@kushnir1.kiev.ua> References: <1061921315.626.16.camel@twister> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: cdrecord causes panic 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: Tue, 26 Aug 2003 21:32:00 -0000 Moreover, it does seem to panic only on write attempts before even printing its usual "Starting to write..." prompt. On other operations (reading info, blanking etc) everything goes all right, at least here (IDE burner, _NEC CD-RW NR-9100A 2.12 with ATAPICAM). Oh yes, and writing with burncd or cdrdao also works without panic. On Tue, 26 Aug 2003, [ISO-8859-1] ?yvind Rakv?g wrote: > When trying to burn with -current from 11 August or later I get a panic. > panic: vm_fault_copy_wired: page missing > This happens with both ULE and 4BSD schedulers. > > I'm using the sym driver on a Tekram 390u3d, LSI 53C1010-33 chip > CD Writer is a Plextor 4/2/20 > > I can see several vm_* files was updated at the time burning broke, so > it's probably related to that. >