(usagi-users 03874) Re: sparc64 and mip6d

Masahide NAKAMURA <[email protected]> Fri, 6 Jul 2007 22:28:17 +0900
Newsgroups gmane.linux.ipv6.usagi.users
Message-ID <[email protected]>
Hello,

Sunday 24 June 2007 00:23, Alexander Clouter wrote:
> Well found out that compiling mip6d with gcc 4.1 on my sparc[1] it comes up 
> with a bus error but when using gcc 3.4[2] things are fine.  Annoying when 
> running the gcc 4.1 compiled code through gdb/strace or removing -O2 and 
> replacing with -O0 removed the problem. Just to sweeten the deal using gcc 
> 4.1 on i386[3] works fine also :-/

OK, thank you for the report. We've not tested on sparc64, but if you find a mip6d
code fix to cover several gcc versions (even it is just caused by gcc bugs), let us
know.


> Anyway, now I'm just down to the 'Failed to add policy' errors.  Any ideas, 
> I'm assuming a configuration issue now...

If that policy is the first one to be inserted to kernel, possibly it is caused by:

 o Kernel does not support XFRM for MIPv6 (EINVAL)
 o XFRM message between kernel and daemon is not matched (EINVAL)
    e.g. Kernel header was unmatched or wrong when building them.
 o The same policy is already inserted on kernel (EEXIST)
    e.g. the daemon ran correctly once and it died abnormally.


Cheers,

-- 
Masahide NAKAMURA