Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 01 Mar 2015 17:17:33 -0800
From:      Justin Hibbits <chmeeedalf@gmail.com>
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?
Message-ID:  <54F3BA2D.8060701@gmail.com>
In-Reply-To: <84EBF11A-FB29-440B-BA0F-9FA94F1501AD@dsl-only.net>
References:  <84EBF11A-FB29-440B-BA0F-9FA94F1501AD@dsl-only.net>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54F3BA2D.8060701>