From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 13 19:50:29 2015 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 46D4F49B; Fri, 13 Mar 2015 19:50:29 +0000 (UTC) Received: from mo6-p00-ob.smtp.rzone.de (mo6-p00-ob.smtp.rzone.de [IPv6:2a01:238:20a:202:5300::1]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.smtp.rzone.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 53D82C88; Fri, 13 Mar 2015 19:50:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1426276199; l=1800; s=domk; d=fuckner.net; h=Content-Type:MIME-Version:Subject:References:In-Reply-To:Cc:To: Reply-To:From:Date; bh=+QESKfdCq53CUeOeDqhDSu4iRopDU4kO6KlQyYNHn3k=; b=od9Q/jYyUja3Ylnvu4R1P0h3EGSv/Ate/q11Pzp/liBEHB6Bot1o+vmHS0penWrlcC8 MuuhdUXRGChNzmLO1e4bBwhVWt1b36GCIcGITSPrGjkxlHjBmoexHvwvq93igiP5UOQ+J le0GOC816lw+32hfOQRog/Q+HyMaHqcoUQQ= X-RZG-AUTH: :IWUHfUGtd9+6EujMWHx57N4dWae4bmTEGbkn8hussqFHiy/c+oYVPeezIVIZYA== X-RZG-CLASS-ID: mo00 Received: from ptangptang.store (com4.strato.de [81.169.145.237]) by smtp-ox.front (RZmta 37.4 AUTH) with ESMTPSA id n0379ar2DJni8rE (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate); Fri, 13 Mar 2015 20:49:44 +0100 (CET) Date: Fri, 13 Mar 2015 20:49:44 +0100 (CET) From: Michael Fuckner Reply-To: Michael Fuckner To: Adrian Chadd Message-ID: <101866634.392324.1426276184167.JavaMail.open-xchange@ptangptang.store> In-Reply-To: References: <550046F7.1050205@fuckner.net> <550093DD.5040603@freebsd.org> <55015D3B.6030605@fuckner.net> <5501DD57.7030305@freebsd.org> <5503234A.4060103@fuckner.net> Subject: Re: Server with 3TB Crashing at boot MIME-Version: 1.0 X-Priority: 3 Importance: Medium X-Mailer: Open-Xchange Mailer v7.6.0-Rev36 X-Originating-Client: com.openexchange.ox.gui.dhtml Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-hackers@freebsd.org" , Oliver Pinter , freebsd-hardware@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Mar 2015 19:50:29 -0000 > Adrian Chadd hat am 13. M=C3=A4rz 2015 um 19:02 gesc= hrieben: =20 Hi! > boot_verbose=3DYES looks to be right. root@s4l:~ # grep verbose /boot/defaults/loader.conf verbose_loading=3D"NO" # Set to YES for verbose loader output OK, this confused me :-( > So hm, just to be clear - it boots fine if you don't load zfs/nvme/nvd? yes, probably zfs, but why does loading nvme also come up with other device= s like mpr? From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 13 19:54:18 2015 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7CA7F65C for ; Fri, 13 Mar 2015 19:54:18 +0000 (UTC) Received: from mail-wi0-f169.google.com (mail-wi0-f169.google.com [209.85.212.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 08F34D5E for ; Fri, 13 Mar 2015 19:54:17 +0000 (UTC) Received: by wivr20 with SMTP id r20so8948668wiv.5 for ; Fri, 13 Mar 2015 12:54:10 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type; bh=bj46Cadu9fslOYOzqJDmN4VBpa8XDkM8azjzoQQYOLg=; b=PdCqUgpsoQTA1vPNPCrCghTppynlfSkeWTfs6re772G59VXT5RUMAKmdLWMIp5u+Jh zQpGZyl24YQTeImBwuV9Pn7Y11lIfRRbW+KkCOcBhTbOUSemnW3K12n7BK0WxnzwgoPC 9np1x7z6lignKMnvyGNBoxqcMk3gens9AL0NBTgHdotqH6dhLfuZRwj2EMDCDoLMg0WO zdmvqbY/TJnm9KExE32WaWjdfJp89TMiGRQ3RpyowKQYcwRGDMirNlcRSqqeYppNZQHS F2/yKkH8Xl9LJbxT8JoWMPLcGAM1JcYJvsPjRvUZlRjzKuzs0QHrItofiGi9gggm0zyH TpgQ== X-Gm-Message-State: ALoCoQlkSMj52ZZgmvIeIhHCTgFr5k0ifSUhSK6rg16YhHyKbdCSeT6DU7W9J7nwoTNJoyM+whLA X-Received: by 10.180.8.98 with SMTP id q2mr39594875wia.80.1426276450394; Fri, 13 Mar 2015 12:54:10 -0700 (PDT) Received: from [10.10.1.68] (82-69-141-170.dsl.in-addr.zen.co.uk. [82.69.141.170]) by mx.google.com with ESMTPSA id l4sm4144664wiw.6.2015.03.13.12.54.08 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 13 Mar 2015 12:54:08 -0700 (PDT) Message-ID: <5503405E.6050805@multiplay.co.uk> Date: Fri, 13 Mar 2015 19:54:06 +0000 From: Steven Hartland User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Ryan Stone Subject: Re: Server with 3TB Crashing at boot References: <550046F7.1050205@fuckner.net> <550093DD.5040603@freebsd.org> <55015D3B.6030605@fuckner.net> <5501DD57.7030305@freebsd.org> <5503234A.4060103@fuckner.net> <55032C1B.5030004@multiplay.co.uk> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Mar 2015 19:54:18 -0000 On 13/03/2015 19:40, Ryan Stone wrote: > On Fri, Mar 13, 2015 at 2:27 PM, Steven Hartland > > wrote: > > Looks like that's panicing when allocating the zfs dbuf hash > table, which by my calculation should be requesting 8GB for a 4TB > physmem? > > > Interesting observation. Michael, can you try booting with this patch > applied? There is a bug in the kernel when we attempt to malloc() > more than 4GB. > > https://people.freebsd.org/~rstone/patches/vm_64bit_malloc.diff > > Nice catch Ryan, don't you just love integer overflows ;-) Regards Steve