[lkcd-devel] Re: [lkcd-general] lcrash problems with ipf(a.k.a ia64)

[Piet/Pete D. <pi...@sg...>]

On Thu, Jan 17, 2002 at 05:11:11PM -0800, S. Chandra Sekharan wrote:
> Hello all,
> 
> 	I am trying to use lkcd in ipf/ia64 platforms, the dump is saved
> 	properly, when I am trying to analyse the dump I got into following
> 	two problems.
> 
> 	I don't know whether it is specific to ia64/ipf platforms.
> 
> 	1. In kl_cmp.c when the index file is created, it uses all 64 bits
> 	   to generate the hash, but while accessing, the address is made
> 	   physical by removing the offset(0xe000000000000000) in kl_virtop()
> 	   and the hash generated in __cmppindex() is not in the table,
> 	   so it fails.
> 
> 	   I added the offset to the address in __cmppindex() before
> 	   generating the hash value and it succeeds. 
> 
> 	   I am not suggesting this as a fix, but giving all information
> 	   I have about the problem.
> 
> 	2. When a kernel which has some loadable module panics, lcrash
> 	   fails while loading ksyms. Debugging it, I found that when
> 	   looking up for "module_list" in kl_get_module(), it gets the
> 	   address of the module at the head of the "module_list", which
> 	   turned out to be 0xa0000000000dc000, and doesn't go any further.
> 	   I tried to dump that address and it failed too.
> 
> 	   I was able to proceed my debugging by changing the addr to point
> 	   to "kernel_module"(again, I this is not a suggestion for a  fix).
> 
> 	Has anybody seen these problems ?
> 	
> 	If anybody gives me a patch for this, I will be glad to try it out.

I'll likely be there tomarrow. Today I was sorting out a problem with dumping 
memory that appears not to be accessable (EFI_RUNTIME_SERVICES_DATA).

I appear to still have two problem that I'll fix tomarrow:

  1.	[root@monica lcrash]# ./lcrash -s /dev/vmdump /var/log/dump
	Error: dump flags in dumpdev page index invalid!
	[root@monica lcrash]#

  2. 	lcrash  /boot/System.map  dump.0 /boot/Kerntype
	map = /boot/System.map, dump = dump.0, outfile = stdout, kerntypes = /boot/Kerntype
	
	Please wait...
	        Initializing vmdump access ................... Done.
	        Loading system map ................................. Done.
	        Loading type info (Kerntypes) ...
	Could not open namelist file: /boot/Kerntype
	 Failed.
	        Initializing arch specific data ... Failed.
	/boot/System.map: not found in dump file

Are your systems also NUMA arch? What's ipf an acronym for?

-piet