mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mikael Starvik" <mikael.starvik@axis.com>
To: "'Patrick McHardy'" <kaber@trash.net>,
	"Mikael Starvik" <mikael.starvik@axis.com>
Cc: "'Linux Kernel Mailing List'" <linux-kernel@vger.kernel.org>,
	"Edgar Iglesias" <edgar.iglesias@axis.com>,
	"'Netfilter Development Mailinglist'" 
	<netfilter-devel@lists.netfilter.org>
Subject: RE: Iptable loop during kernel startup
Date: Wed, 10 Jan 2007 14:00:05 +0100	[thread overview]
Message-ID: <BFECAF9E178F144FAEF2BF4CE739C668030B5909@exmail1.se.axis.com> (raw)
In-Reply-To: <BFECAF9E178F144FAEF2BF4CE739C668044DEB69@exmail1.se.axis.com>

The architecture is called CRIS. Its a straightforward 32-bit only arch. The

only special about this architecture that it doesn't force any alignment of 
data (so a packed struct and an unpacked struct is always the same).

/Mikael
-----Original Message-----
From: Patrick McHardy [mailto:kaber@trash.net] 
Sent: Wednesday, January 10, 2007 1:50 PM
To: Mikael Starvik
Cc: 'Linux Kernel Mailing List'; Edgar Iglesias; 'Netfilter Development
Mailinglist'
Subject: Re: Iptable loop during kernel startup


Mikael Starvik wrote:
>>Which iptables/kernel versions are you using?
> 
> 
> 2.6.19. After further testing it seams to be a compiler/CPU issue. The
exact
> 
> same kernelconfig works on ARM. So I have to dig some...

On which architecture did the error occur? It could be related
to 32 bit compat issues ..


       reply	other threads:[~2007-01-10 13:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BFECAF9E178F144FAEF2BF4CE739C668044DEB69@exmail1.se.axis.com>
2007-01-10 13:00 ` Mikael Starvik [this message]
     [not found] <BFECAF9E178F144FAEF2BF4CE739C668044DEB07@exmail1.se.axis.com>
2007-01-10 11:29 ` Mikael Starvik
2007-01-10 12:49   ` Patrick McHardy
2007-01-10 12:58   ` Mikael Starvik
2007-01-10 13:05     ` Patrick McHardy
2007-01-10 10:01 Mikael Starvik
2007-01-10 10:57 ` Patrick McHardy

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=BFECAF9E178F144FAEF2BF4CE739C668030B5909@exmail1.se.axis.com \
    --to=mikael.starvik@axis.com \
    --cc=edgar.iglesias@axis.com \
    --cc=kaber@trash.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netfilter-devel@lists.netfilter.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®