From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 17 16:43:42 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A07EB16A422 for ; Fri, 17 Feb 2006 16:43:42 +0000 (GMT) (envelope-from freebsd-amd64@datafarm.de) Received: from mr0.continum.net (mr0.continum.net [80.72.128.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63B5E43DBB for ; Fri, 17 Feb 2006 16:43:25 +0000 (GMT) (envelope-from freebsd-amd64@datafarm.de) Received: from tecgate.frbh.continum.net ([80.72.130.254] helo=[192.168.100.70]) by mr0.continum.net with asmtp (Exim 4.30) id 1FA8hY-000G5G-UT for freebsd-amd64@freebsd.org; Fri, 17 Feb 2006 17:43:24 +0100 Message-ID: <43F5FEC5.40809@datafarm.de> Date: Fri, 17 Feb 2006 17:50:13 +0100 From: "V. T. Mueller" User-Agent: Mozilla Thunderbird 0.9 (X11/20041124) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: reproducible panic - 6.0-STABLE-SNAP011 - vm_fault: fault on nofault entry X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Feb 2006 16:43:42 -0000 Hello, I was searching the list archives, but could not find anything that looked really related. So here is my problem: We need to move several services from 5.4 i386 to amd64 and thought 6.0 would work. All tests so far ended in panics or kernel traps, though. Our test hardware is a Supermicro H8D8A http://www.supermicro.com/Aplus/motherboard/Opteron/8131/H8DA8.cfm with two single-core Opteron 246, eight GB of RAM and one ICP-Vortex GDT8500RZ zero-channel RAID controller (iir). Board and controller firmware are up-to-date; hardware was fully tested and proven error-free. Booting from 6.0-RELEASE-amd64-bootonly.iso results in kernel trap 12 depending on ACPI on/off. When not dying of sync with the mentioned kernel trap 12, it panics the same way as describe below. Booting from 6.0-STABLE-SNAP011-bootonly.iso first works, but panics at "writing partition information to disk da0" with: panic: vm_fault: fault on nofault entry, addr: ffffffffb19fb000 This is happening independantly from parameters like swap size and/or the patition scheme attempted. Disabling ACPI does not alter this behaviour, too. Besides, 6.1-BETA1 is the same (7.0-CURRENT dies early during bootup). Has anyone seen s/th like this before? Any hints where the root of this evil might be located? Is there anything I can do to help tracking the problem down to its cause? TIA, vt