On Thu, Nov 11, 2010 at 5:56 AM, Kumar Gala ga...@kernel.crashing.org wrote:
Is there any reason we shouldn't set DMA_BIT_MASK(64) since the DMA block
programming model allows the address to be 64-bits?
Can you explain that? The DMA registers only have room for 36 bits
for the physical
Create the ibm,oops-log NVRAM partition, and capture the end of the printk
buffer in it when there's an oops or panic. If we can't create the
ibm,oops-log partition, capture the oops/panic report in ibm,rtas-log.
Signed-off-by: Jim Keniston jkeni...@us.ibm.com
---
This patch series enables p Series systems to capture oops and panic
reports from the printk buffer into NVRAM, where they can be examined
after reboot using the nvram command.
Patches 1-2 implement the basic feature, and patch 4 adds compression,
so we can capture more of the printk buffer.
Instead of always creating a huge (268K) deflate_workspace with the
maximum compression parameters (windowBits=15, memLevel=8), allow the
caller to obtain a smaller workspace (24K in our case) by specifying
smaller parameter values -- via zlib_deflate_workspacesize2(). In our
case, a small
On Sat, 2010-11-13 at 20:15 -0800, Jim Keniston wrote:
This patch series enables p Series systems to capture oops and panic
reports from the printk buffer into NVRAM, where they can be examined
after reboot using the nvram command.
Here's a patch to the nvram command to add --unzip and
