32-bit kernel, this is a Motorola Powerstack II macine with 604e. PReP
subarch, only buildable from the old ARCH=ppc code (not yet migrated to
ARCH=powerpc).
Ah OK, I thought it was related to the new compat code, but that isn't
the case. Your trace doesn't give much clues, except that it shows
Iptables seems to be broken on ppc for me. Kernel 2.6.17-rc3 (currently
compiling rc4+git). 32-bit ppc, ARCH=ppc with PReP target. Iptables
userland binary is from the latest Debian unstable (1.3.3-2).
The symptoms: iptables usually just tells Invalid Argument on any
modification attempt. I'm
Meelis Roos wrote:
Iptables seems to be broken on ppc for me. Kernel 2.6.17-rc3 (currently
compiling rc4+git). 32-bit ppc, ARCH=ppc with PReP target. Iptables
userland binary is from the latest Debian unstable (1.3.3-2).
The symptoms: iptables usually just tells Invalid Argument on any
This should already be fixed in -rc4.
Unfortunately it was still there with yesterdays rc4+git.
I may have misinterpreted your report - are you running a 32bit or 64bit
kernel?
32-bit kernel, this is a Motorola Powerstack II macine with 604e. PReP
subarch, only buildable from the old
Meelis Roos wrote:
This should already be fixed in -rc4.
Unfortunately it was still there with yesterdays rc4+git.
I may have misinterpreted your report - are you running a 32bit or 64bit
kernel?
32-bit kernel, this is a Motorola Powerstack II macine with 604e. PReP
subarch, only
Meelis Roos wrote:
Iptables seems to be broken on ppc for me. Kernel 2.6.17-rc3 (currently
compiling rc4+git). 32-bit ppc, ARCH=ppc with PReP target. Iptables
userland binary is from the latest Debian unstable (1.3.3-2).
The symptoms: iptables usually just tells Invalid Argument on any
