All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaime Fordham <jaime.f@netcabo.pt>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] ipp2p: Unaligned access in search_all_ed2k on sparc64
Date: Mon, 03 Dec 2007 09:40:17 +0000	[thread overview]
Message-ID: <4753CF01.8060604@netcabo.pt> (raw)
In-Reply-To: <4752ED4E.1030005@netcabo.pt>

Hi,

ipp2p 0.8.2.-r4 is a Gentoo Linux "ebuild" which downloads
"http://www.ipp2p.org/downloads/ipp2p-0.8.2.tar.gz" and then compiles
the kernel+iptables module from source so I would assume that it is the
version you mention.

Any thoughts on the unaligned access?

Jaime.

Vaidas M wrote:
> Where did you get ipp2p 0.8.2-r4? What's the difference from release for
> version 0.8.2 27.09.2006 ?
>
>
> -----Original Message-----
> From: lartc-bounces@mailman.ds9a.nl [mailto:lartc-bounces@mailman.ds9a.nl]
> On Behalf Of Jaime Fordham
> Sent: Sunday, December 02, 2007 7:37 PM
> To: lartc@mailman.ds9a.nl
> Subject: [LARTC] ipp2p: Unaligned access in search_all_ed2k on sparc64
>
> Hey guys,
>
> I've just built a sparc64 (Ultra/5) based firewall with ipp2p compiled
> as a module and I'm constantly getting the following message in my logs:
>
> Kernel unaligned access at TPC[100f8490] search_all_edk+0x20/0x4c
> [ipt_ipp2p]
>
> I'm running the following versions:
>
> - Kernel 2.6.22
> - ipp2p 0.8.2-r4
> - iptables 1.3.8-r1
>
>
> Any thoughts?
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
>
>   
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  reply	other threads:[~2007-12-03  9:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-02 17:37 [LARTC] ipp2p: Unaligned access in search_all_ed2k on sparc64 Jaime Fordham
2007-12-03  9:40 ` Jaime Fordham [this message]
2007-12-03 10:21 ` Jaime Fordham
2007-12-03 13:39 ` Michele Petrazzo - Unipex srl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4753CF01.8060604@netcabo.pt \
    --to=jaime.f@netcabo.pt \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.