<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
Dave,<br><br>Thanks for your response. Just in case anyone else hits the same problem. The more recent kernel built was built with CONFIG_KALLSYMS=y but CONFIG_KALLSYMS_ALL was not set. Setting CONFIG_KALLSYMS_ALL=y solved the problem.<br><br>-Thomas<br><br><br>> Date: Mon, 1 Nov 2010 15:15:38 -0400<br>> From: anderson@redhat.com<br>> To: crash-utility@redhat.com<br>> Subject: Re: [Crash-utility] core file contents<br>> <br>> <br>> ----- "tom anderson" <xentoma@hotmail.com> wrote:<br>> <br>> > I have two different core files generated from two different kernels.<br>> > I noticed one contains all segments<br>> > <br>> > crash> sym -m dpm_kstat<br>> > ffffffffa00c4000 MODULE START: my_kstat<br>> > ...<br>> > ffffffffa00c5290 (t) kstat_numrange_create<br>> > ffffffffa00c55a0 (r) __func__.41073<br>> > ...<br>> > ffffffffa00c5ddb (r) __kstrtab_kstat_numrange_iter_init<br>> > ffffffffa00c5e60 (d) dprintflevel_kstat<br>> > ...<br>> > ffffffffa00c5f40 (d) __this_module<br>> > ffffffffa00c61a0 (b) kstat_spinlock<br>> > ...<br>> > ffffffffa00c6e5e MODULE END: my_kstat<br>> > <br>> > <br>> > <br>> > while the other contains only text segments. Is there some define in<br>> > the kernel config or in core file generation which causes this?<br>> > <br>> > <br>> > crash> sym -m dpm_kstat<br>> > ffffffffa00b9000 MODULE START: dpm_kstat<br>> > ffffffffa00b9000 (t) kstat_cmd_gettbl<br>> > ffffffffa00b9930 (t) kstat_exit<br>> > ffffffffa00b9930 (t) cleanup_module<br>> > ffffffffa00b9a20 (t) kstat_init<br>> > ffffffffa00b9a20 (t) init_module<br>> > ffffffffa00b9bb0 (t) kstat_unregister_provider<br>> > ffffffffa00b9c90 (t) kstat_register_provider<br>> > ffffffffa00b9dc0 (t) kstat_numrange_dprintf<br>> > ffffffffa00b9fa0 (t) kstat_numrange_match<br>> > ffffffffa00b9fe0 (t) kstat_numrange_iter_init<br>> > ffffffffa00ba060 (t) kstat_numrange_destroy<br>> > ffffffffa00ba0a0 (t) kstat_numrange_addentry<br>> > ffffffffa00ba1e0 (t) kstat_numrange_create<br>> > ffffffffa00bb5af MODULE END: dpm_kstat<br>> <br>> I'm not exactly sure.<br>> <br>> Typically if you display the module contents by getting the module<br>> address from the "mod" command output, and dump it like so:<br>> <br>> crash> module <address><br>> <br>> the "num_symtab" field will be roughly equal to the symbol count:<br>> <br>> crash> mod | grep ext4<br>> ffffffffa020e260 ext4 353979 (not loaded) [CONFIG_KALLSYMS]<br>> crash> module.num_symtab ffffffffa020e260<br>> num_symtab = 1080, <br>> crash> sym -m ext4 | wc -l<br>> 1081<br>> crash><br>> <br>> When you do the "mod" command on the two different kernels,<br>> does it show "[CONFIG_KALLSYMS" on the end of each module's<br>> line? If not, that may have something to do with it.<br>> <br>> And if you run the "mod" command to load the debuginfo<br>> data of that module, it's possible that a subsequent<br>> "sym -m <module>" command may show additional symbols.<br>> <br>> Dave<br>> <br>> <br>> <br>> --<br>> Crash-utility mailing list<br>> Crash-utility@redhat.com<br>> https://www.redhat.com/mailman/listinfo/crash-utility<br> </body>
</html>