From: Patrick McHardy <kaber@trash.net>
To: Meelis Roos <mroos@linux.ee>
Cc: Andrew Morton <akpm@osdl.org>,
bugme-daemon@bugzilla.kernel.org, netdev@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 6613] New: iptables broken on 32-bit PReP (ARCH=ppc)
Date: Thu, 01 Jun 2006 19:44:39 +0200 [thread overview]
Message-ID: <447F2787.8010203@trash.net> (raw)
In-Reply-To: <Pine.SOC.4.61.0606011002180.13777@math.ut.ee>
Meelis Roos wrote:
>> Meelis, it would really help if you could try 2.6.16 and in case
>> that doesn't work 2.6.15 to give an idea about whether this is a
>> recent regression or an old problem. We had a number of changes
>> in this area in the last two kernel versions that could be related.
>
>
> Have not gotten 2.6.15 to work with one evening of tinkering - the irq
> patch was not sufficent, there is something more broken in booting that
> I dodn't figure out yet. So no test results for 2.6.15 yet.
Then lets try something different. Please enable the
DEBUG_IP_FIREWALL_USER define in net/ipv4/netfilter/ip_tables.c and
post the results, if any.
next prev parent reply other threads:[~2006-06-01 17:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200605251004.k4PA4Lek007751@fire-2.osdl.org>
2006-05-25 14:03 ` [Bugme-new] [Bug 6613] New: iptables broken on 32-bit PReP (ARCH=ppc) Andrew Morton
2006-05-25 18:52 ` Patrick McHardy
2006-05-25 19:12 ` Meelis Roos
2006-05-25 20:15 ` Meelis Roos
2006-05-26 7:11 ` Meelis Roos
2006-05-26 12:29 ` Safe remote kernel install howto (Re: [Bugme-new] [Bug 6613] New: iptables broken on 32-bit PReP (ARCH=ppc)) Ingo Oeser
2006-05-26 12:34 ` Meelis Roos
2006-05-31 20:25 ` Bill Davidsen
2006-05-26 12:42 ` Michael Tokarev
2006-05-26 12:42 ` Andi Kleen
2006-05-26 13:21 ` Ingo Oeser
2006-06-01 7:03 ` [Bugme-new] [Bug 6613] New: iptables broken on 32-bit PReP (ARCH=ppc) Meelis Roos
2006-06-01 17:44 ` Patrick McHardy [this message]
2006-06-01 20:50 ` Meelis Roos
2006-06-02 13:08 ` Patrick McHardy
2006-06-02 13:18 ` Meelis Roos
2006-06-02 13:56 ` Patrick McHardy
2006-06-04 12:39 ` Meelis Roos
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=447F2787.8010203@trash.net \
--to=kaber@trash.net \
--cc=akpm@osdl.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=mroos@linux.ee \
--cc=netdev@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.