Thus spake Richard Henderson:
> Which module?  This relocation should never EVER show up in kernel code.

Well, it was happening on anything I attempted to make a module.

> (It will show up in dwarf2 debug info, so make sure you're not looking at
> objects compiled with -g, but debug sections ought to be ignored by the
> module loading code.)

I think that may have been the root cause of this; I had
CONFIG_DEBUG_INFO enabled from debugging attempts related to a past
problem.  With that enabled, -g is used for the compile, so the
relocations were added, and module loading failed.  After disabling it,
R_ALPHA_REFLONG did not appear in any of the object files.  So I suppose
my next question is if this is a known/intended side effect -- enabling
CONFIG_DEBUG_INFO means that modules cannot be used?


-- 
Nathan Poznick <kraken@drunkmonkey.org>

My school colors were clear. We used to say, "I'm not naked, I'm in the
band." -Stephen Wright