From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754302Ab0ERE6H (ORCPT ); Tue, 18 May 2010 00:58:07 -0400 Received: from mail-px0-f174.google.com ([209.85.212.174]:53617 "EHLO mail-px0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752068Ab0ERE6E (ORCPT ); Tue, 18 May 2010 00:58:04 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=jt/ZP4lwtD+r/LkHTrNTIvgTw7bqFESFs0fiaGsi1HjZw1vjZ8TLWkB72faRx9OptD fHkUUktj+EKnGp2mBfvgg6e0yIO7nPVvSQMj5M5VrvOSMYEt/VnpGbRl7n1rATJ6Kq2w Pmu5qDO5hQld3Pcxte2QyMn8RFweg8jcg1OLQ= Message-ID: <4BF21DAD.6050609@gmail.com> Date: Tue, 18 May 2010 10:25:09 +0530 From: senthilkumaar2021 User-Agent: Thunderbird 2.0.0.21 (X11/20090320) MIME-Version: 1.0 To: "Justin P. Mattock" CC: linux-kernel@vger.kernel.org Subject: Re: kernel panic References: <4BF21646.60008@gmail.com> <4BF21BD3.60901@gmail.com> In-Reply-To: <4BF21BD3.60901@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Thanks for the reply Initially i was using kernel 2.6.28.5 and kernel panic occurred in that version too tproxy is not supported in linux 2.6.32 http://wiki.squid-cache.org/Features/Tproxy4 kindly guide me how to proceed Regards senthil Justin P. Mattock wrote: > On 05/17/2010 09:23 PM, senthilkumaar2021 wrote: >> HI >> >> >> I am using iptables version 1.43 and getting the following error in >> machine while using squid in tproxy.we are using Linux machine as bridge >> too >> >> i was able to capture part of the error only please help me in solving >> the issue >> >> >> [] ? nf_nat_fn+0x138/0x14e [iptable_nat] >> [] ? nf_nat_in+0x2f/0x6e [iptable_nat] >> [] ? br_nf_pre_routing_finish+0x0/ >> 0x2c4 [bridge] >> [] br_nf_pre_routing_finish+0x50/ >> 0x2c4 [bridge] >> [] ? br_nf_pre_routing_finish+0x0/ >> 0x2c4 [bridge] >> [] ? nf_hook_slow+0x68/0xc8 >> [] ? br_nf_pre_routing_finish+0x0/0x2c4 [bridge] >> [] br_nf_pre_routing+0x5a8/0x5c7 [bridge] >> [] nf_iterate+0x48/0x85 >> [] ? br_handle_frame_finish+0x0/0x154 [bridge] >> [] nf_hook_slow+0x68/0xc8 >> [] ? br_handle_frame_finish+0x0/0x154 [bridge] >> [] br_handle_frame+0x1b1/0x1db [bridge] >> [] netif_receive_skb+0x316/0x434 >> [] napi_gro_receive+0x6e/0x83 >> [] e1000_receive_skb+0x5c/0x65 [e1000e] >> [] e1000_clean_rx_irq+0x1e1/0x28f [e1000e] >> [] e1000_clean+0x99/0x24a [e1000e] >> [] ? _spin_unlock_irqrestore+0x2c/0x43 >> [] net_rx_action+0xb8/0x1b4 >> [] __do_softirq+0x99/0x152 >> [] call_softirq+0x1c/0x30 >> [] do_softirq+0x52/0xb9 >> [] irq_exit+0x53/0x8d >> [] do_IRQ+0x135/0x157 >> [] ret_from_intr+0x0/0x2e >> [] ? mwait_idle+0x9e/0xc7 >> [] ? mwait_idle+0x95/0xc7 >> [] ? atomic_notifier_call_chain+0x13/0x15 >> [] ? enter_idle+0x27/0x2> >> >> Regards >> senthil >> -- >> To unsubscribe from this list: send the line "unsubscribe >> linux-kernel" in >> the body of a message to majordomo@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html >> Please read the FAQ at http://www.tux.org/lkml/ >> > > > if you can.. find the last good kernel, then > do a bisect. > (if you need help doing a bisect, there's plenty > of people to help you out). > > Justin P. Mattock >