On Tue, May 11, 2010 at 1:35 PM, senthilkumaar2021
<senthilkumaar2021@xxxxxxxxx> wrote:
> Thanks for the reply
>
> I tried kernel 2.6.28.5 and 2.6.30.5 but same result
>
> I was using squid2.7stable6 with tproxy in bridge mode .My network traffic
> is 100 MBps and request rate around 400-450req/sec.At evening time it causes
> kernel panic
>
> 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
> Regards
> senthil
>
> Kinkie wrote:
>
>> On Tue, May 11, 2010 at 12:54 PM, senthilkumaar2021
>> <senthilkumaar2021@xxxxxxxxx> wrote:
>>
>>>
>>> I also also using squid 2.7stable 6 on 64 bit but it causing kernel panic
>>>
>>
>> Now THIS is weird.
>> NOTHING in squid should be able to cause a kernel panic.
>>
>> What are you running it on?
senthil, it seems that you're hitting a bug in the driver of your
network interface. Squid has nothing to do with it, but since it
causes lots of network traffic, it triggers the bug. If you try
googling for "bnx2_poll" you'll find quite a few reports of kernel
panics caused by that driver.
Suggesstions include trying alternate drivers or alternate kernels in general.
(or trying with a different NIC, if possible)
--
/kinkie
