Another kernel panic. As before kernel panics is a problem with the kernel, not Squid. 2.6.30.5 is also a very old kernel. May be worth trying a newer one. I also recommend attaching a serial console to the server so you can capture the kernel panic in full. This is needed for reporting the kernel issue to the kernel folks. From what it looks the problem is still in the same area (bridge-netfilter/iptables integration) Regards Henrik fre 2010-05-14 klockan 09:28 +0530 skrev senthilkumaar2021: > Hi , > > Thank you very much for the reply > > We are using squid in interception -tproxy > > As you suggested we changed the lan card and the kernel version from > 2.6.28.5 to 2.6.30.5. > > After running for more than 2 days again crash occurred and the > following error occurred (Attached as image) > > In bridge setup the traffic is about 100MBps > > We are using the following iptable and ebtables rules > > iptables -t mangle -N DIVERT > iptables -t mangle -A DIVERT -j MARK --set-mark 1 > iptables -t mangle -A DIVERT -j ACCEPT > > iptables -t mangle -A PREROUTING -p tcp -m socket -j DIVERT > > iptables -t mangle -A PREROUTING -p tcp --dport 80 -j TPROXY --tproxy-mark 0x1/0x1 --on-port 3129 > > ebtables -t broute -A BROUTING -i $CLIENT_IFACE -p ipv4 --ip-proto tcp > --ip-dport 80 -j redirect --redirect-target DROP > > > ebtables -t broute -A BROUTING -i $INET_IFACE -p ipv4 --ip-proto tcp --ip-sport 80 -j redirect --redirect-target DROP > > > > please help me in solving the issue > > Regard > senthil > > Henrik Nordström wrote: > >> On Tue, May 11, 2010 at 1:35 PM, senthilkumaar2021 > >> <senthilkumaar2021@xxxxxxxxx> wrote: > >> > > > > > >>> part of kernal panic message:this message was obtained in kernal 2.6.28.5 > >>> > >>> <ffffffffa0152a4b>] bnx2_poll_work+0xea0/0xfb9 [bnx2] > >>> [<ffffffff81029713>] enqueue_task+0x50/0x5b > >>> [<ffffffff8104d2ab>] getnstimeofday+0x53/0xb2 > >>> [<ffffffffa0152f31>] bnx2_poll+0xd1/0x1ae [bnx2] > >>> [<ffffffff8120724a>] net_rx_action+0x9d/0x158 > >>> [<ffffffff8103af44>] __do_softirq+0x7a/0x13d > >>> [<ffffffffa0151b6e>] bnx2_msi+0x40/0x47 [bnx2] > >>> [<ffffffff8100cf5c>] call_softirq+0x1c/0x28 > >>> [<ffffffff8100ddc0>] do_softirq+0x2c/0x68 > >>> [<ffffffff8103ae84>] irq_exit+0x3f/0x85 > >>> [<ffffffff8100e06f>] do_IRQ+0x14a/0x16b > >>> [<ffffffff8100c216>] ret_from_intr+0x0/0xa > >>> <EOI> <0> [<ffffffff81174711>] acpi_idle_enter_bm+0x2a3/0x30e > >>> [<ffffffff81174707>] acpi_idle_enter_bm+0x299/0x30e > >>> [<ffffffff8106bac3>] rcu_needs_cpu+0x35/0x44 > >>> [<ffffffff811e8269>] cpuidle_idle_call+0x7f/0xbe > >>> [<ffffffff8100abd4>] cpu_idle+0x4a/0x6d > >>> Code: 5e 5b 5d 31 c0 c3 41 55 41 54 55 53 48 89 fb 48 83 ec 68 4c 8b a7 98 > >>> 00 00 > >>> 00 4c 8b 6f 20 48 8b b7 d0 00 00 00 8b 8f bc 00 00 00 <41> f6 44 24 18 01 74 > >>> 12 > >>> 8a 47 7d 83 e0 f8 83 c8 03 88 47 7d 41 > >>> RIP [<ffffffffa02c405f>] br_nf_pre_routing_finish+0x25/0x2af [bridge] > >>> RSP <ffffffff8155fb40> > >>> CR2: 0000000000000018 > >>> Kernel panic - not syncing: Fatal exception in interrupt > >>> > > > > This suggests issues in Bridge-Netfilter/iptables integration, or > > alternatively related to the network interface driver. > > > > Are you running your Squid in intercepting bridge configuration? > > > > Regards > > Henrik > > > > > > >
