[Crash-utility] Why won't crash read 2.6.19.2 live system?

Marc Milgram mmilgram at egenera.com
Tue Jan 16 21:39:09 UTC 2007


Never mind... It probably had to do with the options I built the kernel
with.  With different configuration options, I can read memory.

-Marc

On Tue, 2007-01-16 at 16:32 -0500, Marc Milgram wrote:
> I am stuck with trying to read access 2.6.19.2 when crash 4.0-3.17
> starts.
> 
> With debug turned on, I get:
> 
> ...
> WARNING: cannot read linux_banner string
> /proc/version:
> Linux version 2.6.19.2MM2 (mmilgram at scipo) (gcc version 3.4.5 20051201
> (Red Hat 3.4.5-2)) #1 SMP Tue Jan 16 10:58:09 EST 2007
> linux_banner:
> 
> crash: kern/vmlinux and /dev/mem do not match!
> 
> Usage:
>   crash [-h [opt]][-v][-s][-i file][-d num] [-S] [mapfile] [namelist]
> [dumpfile]
> 
> Enter "crash -h" for details.
> 
> 
> If I use the same copy of vmlinux and /dev/mem with gdb, I can read
> linux_banner:
> 
> (gdb) p linux_banner
> $5 = "Linux version 2.6.19.2MM2 (mmilgram at scipo) (gcc version 3.4.5
> 20051201 (Red Hat 3.4.5-2)) #1 SMP Tue Jan 16 10:58:09 EST 2007\n"
> 
> I ran crash in gdb and found that read_dev_mem reads 1500 bytes of data
> from /dev/mem, but all the bytes are 0.
> 
> Am I doing something wrong?
> 
> Thanks in advance,
> Marc
> 
> 
> --
> Crash-utility mailing list
> Crash-utility at redhat.com
> https://www.redhat.com/mailman/listinfo/crash-utility




More information about the Crash-utility mailing list