linux-kernel - Re: kernel panic

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 18 May 2010 10:25:09 +0530
From:	senthilkumaar2021 <senthilkumaar2021@...il.com>
To:	"Justin P. Mattock" <justinmattock@...il.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: kernel panic

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
>>
>>
>> [<ffffffffa03933c2>] ? nf_nat_fn+0x138/0x14e [iptable_nat]
>> [<ffffffffa0393585>] ? nf_nat_in+0x2f/0x6e [iptable_nat]
>> [<ffffffffa027edaa>] ? br_nf_pre_routing_finish+0x0/
>> 0x2c4 [bridge]
>> [<ffffffffa027edfa>] br_nf_pre_routing_finish+0x50/
>> 0x2c4 [bridge]
>> [<ffffffffa027edaa>] ? br_nf_pre_routing_finish+0x0/
>> 0x2c4 [bridge]
>> [<ffffffff81339a50>] ? nf_hook_slow+0x68/0xc8
>> [<ffffffffa027edaa>] ? br_nf_pre_routing_finish+0x0/0x2c4 [bridge]
>> [<ffffffffa027f616>] br_nf_pre_routing+0x5a8/0x5c7 [bridge]
>> [<ffffffff813399ab>] nf_iterate+0x48/0x85
>> [<ffffffffa027a931>] ? br_handle_frame_finish+0x0/0x154 [bridge]
>> [<ffffffff81339a50>] nf_hook_slow+0x68/0xc8
>> [<ffffffffa027a931>] ? br_handle_frame_finish+0x0/0x154 [bridge]
>> [<ffffffffa027ac36>] br_handle_frame+0x1b1/0x1db [bridge]
>> [<ffffffff8131d54b>] netif_receive_skb+0x316/0x434
>> [<ffffffff8131dbfb>] napi_gro_receive+0x6e/0x83
>> [<ffffffffa0125bfe>] e1000_receive_skb+0x5c/0x65 [e1000e]
>> [<ffffffffa0125de8>] e1000_clean_rx_irq+0x1e1/0x28f [e1000e]
>> [<ffffffffa012730e>] e1000_clean+0x99/0x24a [e1000e]
>> [<ffffffff813bcfc5>] ? _spin_unlock_irqrestore+0x2c/0x43
>> [<ffffffff8131ba62>] net_rx_action+0xb8/0x1b4
>> [<ffffffff8104ed43>] __do_softirq+0x99/0x152
>> [<ffffffff8101284c>] call_softirq+0x1c/0x30
>> [<ffffffff81013a02>] do_softirq+0x52/0xb9
>> [<ffffffff8104e969>] irq_exit+0x53/0x8d
>> [<ffffffff81013d1a>] do_IRQ+0x135/0x157
>> [<ffffffff81011f93>] ret_from_intr+0x0/0x2e
>> <EOI> [<ffffffff81017e20>] ? mwait_idle+0x9e/0xc7
>> [<ffffffff81017e17>] ? mwait_idle+0x95/0xc7
>> [<ffffffff813bfd20>] ? atomic_notifier_call_chain+0x13/0x15
>> [<ffffffff810102f4>] ? 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@...r.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
>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/