hi Greg,
On Fri, Nov 07, 2003 at 09:31:13AM +1100, Keith Owens wrote:
> On Thu, 06 Nov 2003 14:22:29 -0500,
> Greg Whynott <greg@xxxxxxxxxxxxxxxxxx> wrote:
> >Warning (compare_maps): ksyms_base symbol
> >create_bounce_R__ver_create_bounce not found in System.map. Ignoring
> >ksyms_base entry
> >Warning (compare_maps): ksyms_base symbol
> >highmem_start_page_R__ver_highmem_start_page not found in System.map.
> >Ignoring ksyms_base entry
> >Warning (compare_maps): ksyms_base symbol kmap_high_R__ver_kmap_high not
> >found in System.map. Ignoring ksyms_base entry
> >Warning (compare_maps): ksyms_base symbol kmap_prot_R__ver_kmap_prot not
> >found in System.map. Ignoring ksyms_base entry
> >Warning (compare_maps): ksyms_base symbol kmap_pte_R__ver_kmap_pte not
> >found in System.map. Ignoring ksyms_base entry
> >Warning (compare_maps): ksyms_base symbol kunmap_high_R__ver_kunmap_high
> >not found in System.map. Ignoring ksyms_base entry
>
> Those ksymoops messages indicate an incomplete kernel build. At some
> stage you switched the value of CONFIG_HIGHMEM and rebuilt but the
> kernel build process did not get it right, one of the many known kbuild
> 2.4 bugs.
>
> It has probably not caused any problems, OTOH it cannot be ruled out as
> a possible cause of your problem. Can you do a complete kernel build
> starting from make mrproper and see if the problem still exists?
And if you have a reproducible test case showing this problem,
I would _really_ like to hear the details, please -- an exact
recipe, from go (mkfs) to woe would be extremely helpful.
Thanks for reporting the problem, btw.
cheers.
--
Nathan
|