mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@it.uu.se>
To: linux-kernel@vger.kernel.org
Cc: netfilter@vger.kernel.org
Subject: [2.6.35 regression] iptables busted on Mac G5
Date: Thu, 5 Aug 2010 16:58:35 +0200	[thread overview]
Message-ID: <19546.53659.970308.750410@pilspetsen.it.uu.se> (raw)

The machine is a Mac G5 (ppc64) with Fedora 11 user-space,
most of it 32-bit.  Everything worked fine with kernel 2.6.34.

With kernel 2.6.35 however the machine comes up, seemingly with
networking operational according to the kernel log, but neither
NIC will actually send or receive anything including pings.  There
are no errors, just no traffic.

Initial investigation shows that 2.6.34-git5 was the last kernel
that worked, and from 2.6.34-git6 up to 2.6.35-git2 all kernels
malfunction as described (and 2.6.35-rc1 won't boot at all).

As a final experiment I disabled iptables (via chkconfig + reboot)
and that restored networking.  This is clearly not the solution.

I'll try to narrow it down further next week when I'm at the
machine's location again.  Meanwhile I would be grateful if
anyone has any ideas about what the issue might be.  I'll add
that a Mac G4 (ppc32) with similar kernel configuration and
user-space works fine with 2.6.35 and iptables.

/Mikael

--- config-2.6.34-git5	2010-08-05 16:02:30.000000000 +0200
+++ config-2.6.34-git6	2010-08-05 15:46:43.000000000 +0200
@@ -1,7 +1,7 @@
 #
 # Automatically generated make config: don't edit
-# Linux kernel version: 2.6.34-git5
-# Thu Aug  5 16:02:30 2010
+# Linux kernel version: 2.6.34-git6
+# Thu Aug  5 15:46:43 2010
 #
 CONFIG_PPC64=y
 
@@ -410,11 +410,22 @@
 # CONFIG_NF_CONNTRACK_SIP is not set
 # CONFIG_NF_CT_NETLINK is not set
 CONFIG_NETFILTER_XTABLES=m
-# CONFIG_NETFILTER_XT_TARGET_MARK is not set
+
+#
+# Xtables combined modules
+#
+# CONFIG_NETFILTER_XT_MARK is not set
+
+#
+# Xtables targets
+#
 # CONFIG_NETFILTER_XT_TARGET_NFLOG is not set
 # CONFIG_NETFILTER_XT_TARGET_TCPMSS is not set
+
+#
+# Xtables matches
+#
 CONFIG_NETFILTER_XT_MATCH_CONNTRACK=m
-# CONFIG_NETFILTER_XT_MATCH_MARK is not set
 CONFIG_NETFILTER_XT_MATCH_STATE=m
 # CONFIG_IP_VS is not set
 
@@ -436,6 +447,7 @@
 # CONFIG_RDS is not set
 # CONFIG_TIPC is not set
 # CONFIG_ATM is not set
+# CONFIG_L2TP is not set
 # CONFIG_BRIDGE is not set
 # CONFIG_NET_DSA is not set
 # CONFIG_VLAN_8021Q is not set
@@ -451,6 +463,7 @@
 # CONFIG_IEEE802154 is not set
 # CONFIG_NET_SCHED is not set
 # CONFIG_DCB is not set
+CONFIG_RPS=y
 
 #
 # Network testing
@@ -467,6 +480,11 @@
 # CONFIG_NET_9P is not set
 
 #
+# CAIF Support
+#
+# CONFIG_CAIF is not set
+
+#
 # Device Drivers
 #
 
@@ -778,6 +796,7 @@
 CONFIG_TIGON3=m
 # CONFIG_BNX2 is not set
 # CONFIG_CNIC is not set
+# CONFIG_XILINX_LL_TEMAC is not set
 # CONFIG_QLA3XXX is not set
 # CONFIG_ATL1 is not set
 # CONFIG_ATL1E is not set

             reply	other threads:[~2010-08-05 14:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-05 14:58 Mikael Pettersson [this message]
2010-08-23 12:11 ` [BISECTED][2.6.35 " Mikael Pettersson
2010-08-23 12:16   ` Florian Westphal
2010-08-23 12:34     ` Eric Dumazet
2010-08-23 13:14     ` Mikael Pettersson

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=19546.53659.970308.750410@pilspetsen.it.uu.se \
    --to=mikpe@it.uu.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netfilter@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 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®