[Crash-utility] bt: cannot determine starting stack pointer

[Dave Anderson]

----- Original Message -----
> On Tue, Feb 14, 2012 at 1:18 PM, Dave Anderson <anderson at redhat.com> wrote:
> >> I don't actually know what the acquisition method was.
> >
> > Enter "help -n"
> 
> Here ya go.  Doesn't mean much to me.  Hope you didn't want 32 hash
> tables....

It means that it's an LKCD-generated dumpfile, or some derivative thereof.

I personally haven't done any LKCD support for many years now, given that
LKCD as a dumping mechanism has pretty much been superceded by kdump.
But every so often somebody forwards an LKCD-related patch that I take
in as long as it compiles.

That being said, it's news to me that backtraces cannot be generated
for the active tasks from LKCD dumpfiles, unless it's some kind of
"live dump" or something?  Was there a panic or oops?  What's the 
last thing shown by the "log" command?

Dave 
 
> crash> help -n
>      total_pages: 212168
>           hashed: 2566
>       compressed: 1783 (69%)
>              raw: 783 (30%)
>     cached_reads: 50377 (90%)
>     hashed_reads: 2615 (4%)
>      total_reads: 55558 (hashed or cached: 94%)
> page_hash[32]:
> [......]
> page_cache_hdr[16]:
>  INDEX   PG_ADDR  PG_BUFPTR        PG_HIT_COUNT
>   [ 0] 3fd849000  1a00a30  48
>   [ 1] 1fd3a6000  1a01a30  1
>   [ 2] 2053cf000  1a02a30  1
>   [ 3] 2075ca000  1a03a30  64
>   [ 4] 2023f5000  1a04a30  16
>   [ 5] 3fd84e000  1a05a30  1
>   [ 6] 405f77000  1a06a30  31
>   [ 7] 3fd910000  1a07a30  1
>   [ 8] 405f74000  1a08a30  31
>   [ 9] 3fd99d000  1a09a30  1
>   [10] 405f6c000  1a0aa30  35
>   [11] 1fd456000  1a0ba30  1
>   [12] 204f65000  1a0ca30  15
>   [13] 405d7e000  1a0da30  31
>   [14] 3fd83d000  1a0ea30  1
>   [15] 405f79000  1a0fa30  31
>   mb_hdr_offsets: NA
>        num_zones: 20 / 128
>    zoned_offsets: 210313
>   dumpfile_index: (null)
>              ifd: -1
>     memory_pages: 4134481
>  page_offset_max: 442278774
>   page_index_max: 0
>     page_offsets: 0
>