[OpenAFS-devel] Re: openafs linux-kernelmodule not buildable on sparc

Daniel J. Priem daniel@flexserv.de
Mon, 26 Feb 2007 05:44:02 +0100


...
> ...
>> 1021b904  c471c003  da246050  c25c2008
>> root@paulus:~#               \|/ ____ \|/
>
> What happens if you do "modprobe libafs" by hand?  Does it die when
> the module is loaded?  Or soon after when afsd is run?  I'm guessing
> it dies right away.

It dies when i load the modul

>
> I wonder what address the module loaded at?
> in theory "insmod" ought to tell you.  maybe try
> insmod -m /usr/src/openafs-1.4.3rc2/src/libafs/MODLOAD-2.6.18-3-sparc64-SP/libafs-2.6.18-3-sparc64.ko

I will try later

>
> or even before insmod, do
> sort /proc/ksyms
> and see what pattern other load modules and the base system follow.
> On i386, the base kernel might load at c0000000 & modules somewhere
> after f880d000.   sparc64 does something different.
>
> S390x & sparc64 use "32-bit" syscall tables.  s390x has
> "syscall_jump_code" which appears to be a stub which
> transfers to the real thing.  sparc64 doesn't check for
> problems and doesn't have jump code.  If code loads above
> 4Gb, it won't work.

How can i force to get code loaded about 4GB? if there is a way, then i
can try this on my e4500.

>
> 				-Marcus Watts

-- 
 .''`.
 : :' :      Daniel J. Priem
 `. `'       http://flexserv.de
   `-