From owner-freebsd-ppc@FreeBSD.ORG Mon Mar 2 01:17:36 2015 Return-Path: Delivered-To: freebsd-ppc@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 D72C0438 for ; Mon, 2 Mar 2015 01:17:36 +0000 (UTC) Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) (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 A0422FAC for ; Mon, 2 Mar 2015 01:17:36 +0000 (UTC) Received: by padfb1 with SMTP id fb1so455253pad.7 for ; Sun, 01 Mar 2015 17:17:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=2D0WZwNljfmfuqYhTIEeY7Mj0b3eE8sz0oGFf0FXwjE=; b=pOuPn4vr3YJhHsn1r/CsNLtamEfI6g9FMvJNKEomtWKktN/KXNnMSnPeF5uzQqEG/N LDWZ+PRRcihWUejkcwt0kmaOih333jU4SpnsmgP/H8mRCu3vh8DiwWWt+tccmLKZb7Ab WjSkTVgoViVVbI6nULmukzVF+jM1BwHK/5IGKnsNyqsEW4Aa38gX/D9t23S8tqdKeEry c3sAKA1mIm/L3/Fq5aOi7NS99QkQetIStOVqp3J98JXcUyMHGUWa6M2r52BlON9H//h3 6DI49TSw/LlqO66Nil2YrbHt7GykkVPHL2Ht81/4+xR6fnr03N/22iQKI2XPyMRn2EXG sH0w== X-Received: by 10.68.189.229 with SMTP id gl5mr42415024pbc.109.1425259056051; Sun, 01 Mar 2015 17:17:36 -0800 (PST) Received: from [192.168.1.69] (107-222-186-3.lightspeed.sntcca.sbcglobal.net. [107.222.186.3]) by mx.google.com with ESMTPSA id fz7sm10109161pbd.60.2015.03.01.17.17.34 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 01 Mar 2015 17:17:34 -0800 (PST) Message-ID: <54F3BA2D.8060701@gmail.com> Date: Sun, 01 Mar 2015 17:17:33 -0800 From: Justin Hibbits User-Agent: Mozilla/5.0 (X11; FreeBSD powerpc; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: freebsd-ppc@freebsd.org Subject: Re: cb_dumpdata vs. PowerMac G5's (or at least my SSD context): add involvement of dumpinfo's maxiosize value? References: <84EBF11A-FB29-440B-BA0F-9FA94F1501AD@dsl-only.net> In-Reply-To: <84EBF11A-FB29-440B-BA0F-9FA94F1501AD@dsl-only.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Mar 2015 01:17:36 -0000 On 03/01/15 04:14, Mark Millard wrote: > Context: 10.1-STABLE powerpc64 for PowerMac G5 > > I'm unable to get panic dumps because the DMA size is rejected, 64K being too big. I'd like to get things to the point where panic dumps are possible for that context. This was working in the original powerpc64 dump code. Look at r257941, which was the original code that I committed. I guess the DMA size clamping didn't get migrated to the new dump code. - Justin