From owner-freebsd-current@FreeBSD.ORG Thu Oct 13 21:46:13 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 217A016A41F for ; Thu, 13 Oct 2005 21:46:13 +0000 (GMT) (envelope-from Paul.Dekkers@surfnet.nl) Received: from dorsvlegel.surfnet.nl (dorsvlegel.surfnet.nl [192.87.108.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 813D843D49 for ; Thu, 13 Oct 2005 21:46:11 +0000 (GMT) (envelope-from Paul.Dekkers@surfnet.nl) Received: from gromit.ipv6.chippie.org ([2001:610:508:2121:207:e9ff:fe8f:a375] helo=[IPv6:2001:610:508:2121:207:e9ff:fe8f:a375]) by dorsvlegel.surfnet.nl (Exim 4.54) with esmtps (TLSv1:AES256-SHA:256) id 1EQAtu-0003qj-WC; Thu, 13 Oct 2005 23:46:11 +0200 Message-ID: <434ED5A2.7090405@surfnet.nl> Date: Thu, 13 Oct 2005 23:46:10 +0200 From: Paul Dekkers User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Scott Long References: <20051013175249.804CB16A454@hub.freebsd.org> <434EB5E6.7020109@kelleycows.com> <434EBB4C.8030609@surfnet.nl> <434EC385.8020100@kelleycows.com> <434EC813.60409@samsco.org> In-Reply-To: <434EC813.60409@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SURFnet-Sender-check: 8ae21ef524b09d992f22af3c70f0e299 Cc: Christopher Kelley , freebsd-current@freebsd.org Subject: Re: FreeBSD 6.0-RC1 available X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 13 Oct 2005 21:46:13 -0000 Scott, Scott Long wrote: > Christopher Kelley wrote: > >> Paul Dekkers wrote: >> >>> Christopher Kelley wrote: >>> >>>> I am having a problem installing 6-RC1, that I am wondering if this >>>> will also fix. It starts to copy from the CD drive, then pretty >>>> quickly I get; >>>> >>>> panic: vm_fault: fault on nofault entry, addr: c641e000 >>>> Uptime: 1m44s >>>> Cannot dump. No dump device defined. >>>> Automatic reboot in 15 seconds - press a key on the console to >>>> abort. >>>> >>>> This is a straight install, I'm not running under VMWare (and I >>>> haven't actually a clue what QEMU is), but I don't know if this is >>>> something that might be related. The addr is different each time. >>>> >>>> This is my "beater" machine, an old P233/mmx with only 96megs, but >>>> I've successfully installed various 5.x versions, windows, etc on >>>> this machine. I've even in the past successfully cvsup'd from 5.4 >>>> to 6, just to see if it would work. >>> >>> FWIW, I just experienced the same with a straight install on a Dell >>> PE 1300, a PIII-500. >>> It was half way through copying the "bin" set. >>> >>> Paul >>> >>> BTW, Probably unrelated: I had to disable apic in order to boot (I'm >>> on the latest BIOS, A12) and ACPI disabled itself. >> >> Heh, ever get a new idea right after you press "enter" to send a >> message? I *DID* get it to work, by going into the BIOS and >> disabling UDMA access for both master and slave on the secondary IDE >> controller (the CDROM is on the secondary master, nothing on the >> secondary slave). I left the UDMA on for the primary IDE controller >> (where the hard drive is). >> >> So that's weird. Because I didn't have do that to install 5.x or >> Windows 98. I guess it won't affect anything, I don't think CDROMs >> are UDMA anyways. >> >> Christopher > > There is a candidate fix for all of these 'panic while copying files off > the CD' problems. I've tested it successfully under Qemu since it > happens most often there and in VMWare, but there is no reason why it > shouldn't also happen on real hardware. So, for those with some to > test, please go to ftp://ftp.freebs.org/pub/FreeBSD/snapshots and > download the ISO there and install it. Then let me know ASAP whether > it helps or not. It helps; the 13 October snapshot installs just fine. Paul P.S. Unlike Christopher I have no UDMA settings in the BIOS, and hw.ata.ata_dma=0 didn't do it for me, so this fix is certainly welcome :-)