----- "James Washer" <washer(a)trlp.com&gt; wrote: Hi Jim, Without the prior debug output I can't tell whether the the dumpfile an ELF kdump or a compressed kdump. But in either case, every read from the dumpfile is failing. When readmem() is called, it translates those virtual address values into their physical address, and the physical address is passed onto either read_kdump() or read_diskdump(). A READ_ERROR is being returned from whichever of those two functions were called. (1) read_kdump() passes the request to read_netdump(), which is where the READ_ERROR is generated. (2) read_diskdump() -- used for compressed kdump vmcores -- calls diskdump.c's cache_page(), which is where the READ_ERROR is generated. In the case of read_kdump()'s call to read_netdump(), a READ_ERROR is generated for two possible reasons: 1. if the physical address does not fit into any of the PT_LOAD segments declared in the ELF header. 2. if the physical address does fit into a PT_LOAD segment, but the actual read() system call fails. In the case of read_diskdump()'s call to cache_page(), a READ_ERROR is generated for four possible reasons: 1. if the read() system call of the page descriptor fails. 2. if the page descriptor's advertised size is greater than the header's block_size. 3. if the read() system call of the compressed page fails. 4. if the uncompress() of the page data fails. (but there's an error message associated with that, so that's not the problem in your case) So the first thing to determine is where the READ_ERROR is generated. Dave