> > I started to look into the problem why we get the > > WARNING: Out of order unwind entry! > warning messages at kernel bootup in dmesg. > > It's related to a binutils/linker bug, that ld does not correctly > removes unlink information for unused weak symbols, which have been > replaced by their non-weak ones. > > In my kernel I could track it down to 2 symbols: > - arch_mod_section_prepend() from kernel/module.c, and > - save_stack_trace_tsk(). > > Here is the extract of the readelf output on vmlinux: > ... > <inb>: [0x1011fbd4-0x1011fc48] > Entry_GR=1 Save_SP Save_RP Total_frame_size=8 > <arch_mod_section_prepend>: [0x1011fc4c-0x1011fc74] > Entry_GR=1 Save_SP Total_frame_size=8 > <arch_mod_section_prepend>: [0x1011fc4c-0x10167cf4] > Entry_GR=1 Save_SP Total_frame_size=8 > <module_arch_cleanup>: [0x1011fc78-0x1011fcb8] > Entry_GR=2 Save_SP Save_RP Total_frame_size=8 > ... It might be useful to know the actual location arch_mod_section_prepend and whether it follows inb in its .o. From my understanding of things, it shouldn't be necessary to remove the unwind info for unused weak symbols if they aren't garbage collected. A simple testcase would be helpful. Dave -- J. David Anglin dave.anglin@xxxxxxxxxxxxxx National Research Council of Canada (613) 990-0752 (FAX: 952-6602) -- To unsubscribe from this list: send the line "unsubscribe linux-parisc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
