----- "Adrien Kunysz" <adk@xxxxxxxxxx> wrote: > Dave Anderson wrote: > > I'm guessing that the memory containing virtual address 0x1020009d024 > > (physical 0x20009d024) is not there for some reason. > > # crash > [...] > crash> !tty > /dev/pts/0 > crash> set console /dev/pts/0 > debug console [11227]: /dev/pts/0 > console: /dev/pts/0 > crash> extend snap-rhel4-x86_64/snap.so > ./snap-rhel4-x86_64/snap.so: shared object loaded > crash> snap mycore > 00000000-00099bff : System RAM > 00100000-f7feffff : System RAM > ram_segments[0]: 0000000000000000 0000000000099000 [00000000-00099bff] > ram_segments[1]: 0000000000100000 00000000f7ff0000 [00100000-f7feffff] > mycore: [100%] > -rw-r--r-- 1 root root 4160684848 Sep 3 10:23 mycore > crash> quit > crash 5057 0 - Live 0xffffffffa0220000 > # crash /usr/lib/debug/lib/modules/2.6.9-89.ELsmp/vmlinux mycore > [...] > crash: read error: kernel virtual address: 1020009d024 type: > "tss_struct ist array" > > Not sure how to read this. When the vmcore is created by "snap", it first looks at /proc/iomem for the regions of physical memory that are dumpable. Therefore it rejected any physical address above f7feffff, which is the problem at hand. Just for sanity's sake, what does "cat /proc/iomem" show? Dave -- Crash-utility mailing list Crash-utility@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/crash-utility
