9:16 a.m.
----- "Adrien Kunysz" <adk(a)redhat.com> wrote:
Dear crash-utility list,
I played a bit with snap on RHEL 4 and besides the fact it doesn't build out of
the box (trivial Makefile compatibility problem), it seems it doesn't really
dump a full core properly (at least on the system I tested).
Since this is not really something that is supposed to be supported I am posting
this here rather than opening a Bugzilla. I haven't attempted to repro on other
distros.
# crash
crash> extend snap-rhel4-x86_64/snap.so
./snap-rhel4-x86_64/snap.so: shared object loaded
crash> snap mycore
mycore: [100%]
-rw-r--r-- 1 root root 4160684848 Sep 3 09:37 mycore
crash> quit
# free
total used free shared buffers
cached
Mem: 16319168 8065516 8253652 0 133060
6231128
-/+ buffers/cache: 1701328 14617840
Swap: 2097144 0 2097144
# uname -a
Linux *** 2.6.9-89.ELsmp #1 SMP Mon Apr 20 10:33:05 EDT 2009 x86_64
x86_64
x86_64 GNU/Linux
# 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"
Is that expected? Any idea what's going on?
It created at 4GB vmcore on a 16GB system, which is apparently the
problem. Try doing this (done on my 1GB RHEL4 box):
crash> !tty
/dev/pts/3
crash> set console /dev/pts/3
debug console [11505]: /dev/pts/3
console: /dev/pts/3
crash> extend snap.so
./extensions/snap.so: shared object loaded
crash> snap mycore
00000000-0009ffff : System RAM
00100000-3fe8abff : System RAM
ram_segments[0]: 0000000000000000 00000000000a0000 [00000000-0009ffff]
ram_segments[1]: 0000000000100000 000000003fe8a000 [00100000-3fe8abff]
mycore: [100%]
-rw-r--r-- 1 root root 1072210680 Sep 3 09:24 mycore
crash>
I'm guessing that the memory containing virtual address 0x1020009d024
(physical 0x20009d024) is not there for some reason.
Dave
9:21 a.m.
New subject: snap crash plugin on RHEL 4
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.
9:31 a.m.
New subject: snap crash plugin on RHEL 4
----- "Adrien Kunysz" <adk(a)redhat.com> 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
9:37 a.m.
New subject: snap crash plugin on RHEL 4
Dave Anderson wrote:
----- "Adrien Kunysz" <adk(a)redhat.com> 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.
f7ff0000-f7ffefff : ACPI Tables
f7fff000-f7ffffff : ACPI Non-volatile Storage
Just for sanity's sake, what does "cat /proc/iomem"
show?
00000000-00099bff : System RAM
00099c00-0009ffff : reserved
000a0000-000bffff : Video RAM area
000c0000-000c9fff : Video ROM
000ca000-000cafff : Adapter ROM
000cb000-000cbfff : Adapter ROM
000cc000-000ccfff : Adapter ROM
000cd000-000cdfff : Adapter ROM
000ce000-000cefff : Adapter ROM
000cf000-000d4bff : Adapter ROM
000f0000-000fffff : System ROM
00100000-f7feffff : System RAM
00100000-00318afa : Kernel code
00318afb-00469ec0 : Kernel data
f7ff0000-f7ffefff : ACPI Tables
f7fff000-f7ffffff : ACPI Non-volatile Storage
fbf00000-fbffffff : PCI Bus #01
fbf80000-fbf9ffff : 0000:01:02.1
fbf80000-fbf9ffff : e1000
fbfa0000-fbfbffff : 0000:01:02.0
fbfa0000-fbfbffff : e1000
fbfc0000-fbfdffff : 0000:01:01.1
fbfc0000-fbfdffff : e1000
fbfe0000-fbffffff : 0000:01:01.0
fbfe0000-fbffffff : e1000
fc000000-fc4fffff : PCI Bus #02
fc4e0000-fc4effff : 0000:02:03.0
fc4fc000-fc4fffff : 0000:02:03.0
fc500000-fe5fffff : PCI Bus #03
fd000000-fdffffff : 0000:03:03.0
fe5fd000-fe5fdfff : 0000:03:00.1
fe5fd000-fe5fdfff : ohci_hcd
fe5fe000-fe5fefff : 0000:03:00.0
fe5fe000-fe5fefff : ohci_hcd
fe5ff000-fe5fffff : 0000:03:03.0
fe6fe000-fe6fefff : 0000:00:02.1
fe6ff000-fe6fffff : 0000:00:01.1
fe700000-fe7fffff : PCI Bus #01
fe800000-fe8fffff : PCI Bus #02
feafe000-feafefff : 0000:04:02.1
feaff000-feafffff : 0000:04:01.1
ff700000-ffffffff : reserved
5492
days inactive
5492
days old
devel@lists.crash-utility.osci.io
3 comments
2 participants
participants (2)
-
Adrien Kunysz -
Dave Anderson