* Jay Lan <[EMAIL PROTECTED]> [2008-09-09]:
>
> I talked to Jack Steiner about this problem. He said:
> The memory at 0xe0600010 is part of Altix "fetchop" space
> (AKA mspec). The memory supports only uncached attributes. A normal
> "cached" access may cause MCAs.
>
> The kernel
Bernhard Walle wrote:
> * Jay Lan <[EMAIL PROTECTED]> [2008-09-08]:
>
>> Any input helping me speed up debugging is appreciated.
>
> I would start with comparing the ELF program headers of /proc/vmcore
> which you get with "readelf -l /proc/vmcore" in kdump environment and
> the /proc/iomem whic
* Jay Lan <[EMAIL PROTECTED]> [2008-09-08]:
> Any input helping me speed up debugging is appreciated.
I would start with comparing the ELF program headers of /proc/vmcore
which you get with "readelf -l /proc/vmcore" in kdump environment and
the /proc/iomem which kexec uses to set up the ELF core
When trying to do 'cp /proc/vmcore ...', the kdump kernel MCA'ed.
KDB showed me this backtrace: (it is really nice to have kdb working
with kdump :))
Entering kdb (current=0xe0303257, pid 3519) on processor 0 due
to KDB_ENTER()
[0]kdb> bt
Stack traceback for pid 3519
0xe0303257
