On Monday 26 March 2012, Uwe Kleine-König wrote: > On Mon, Mar 26, 2012 at 08:37:04AM +0100, Russell King - ARM Linux wrote: > > On Sun, Mar 25, 2012 at 07:59:44PM -0400, Jon Masters wrote: > > > As to longer term, I am happy to work up something that will spot this > > > particular kind of failure (symbol changes type) and output something > > > more useful during the kallsyms generation if you would like. > > > > > > Are you planning to pull in either of the fixes you mention? > > > > I'm not, because those are all sub-optimal - I don't see why we should > > bloat the kernel image just for the sake of working around kallsyms. > > > > The best I've come up with so far which avoids that is to force > > KALLSYMS_EXTRA_PASS to always be set on ARM. > Just to let you know: I even saw failures with KALLSYMS_EXTRA_PASS set. > Not so in the recent past and sometimes not even reproducible IIRC. > I will save the build results next time it happens now that I saw what > to look for. Yes, I saw these too in my randconfig builds some time ago. Maybe a handful of builds among 50000 configurations. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
