Issue

• Machines boot up in around +10 minutes due to bnx2x related issue. Prints huge number of bnx2x / firmware related traces on console.
• Few of the logs as seen on console and/or dmesg are;

[  243.133668] INFO: task events/1:148 blocked for more than 120 seconds.
[  243.133673]       Not tainted 2.6.32-573.1.1.el6.x86_64 #1
[  243.133675] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  243.133678] events/1      D 0000000000000001     0   148      2 0x00000000
[  243.133683]  ffff881068c6bd30 0000000000000046 ffff881068c6bfd8 ffff8810b8818708
[  243.133688]  ffff881068c6bd60 ffffffff81066053 ffff8810b8815a28 ffff881068c3cae8
[  243.133692]  ffff881068c6bce0 ffffffff8106f193 ffff881068c3d068 ffff881068c6bfd8
[  243.133696] Call Trace:
[  243.133708]  [<ffffffff81066053>] ? perf_event_task_sched_out+0x33/0x70
[  243.133714]  [<ffffffff8106f193>] ? dequeue_entity+0x113/0x2e0
[  243.133721]  [<ffffffff8100969d>] ? __switch_to+0x7d/0x340
[  243.133728]  [<ffffffff81539b06>] __mutex_lock_slowpath+0x96/0x210
[  243.133733]  [<ffffffff8153817e>] ? thread_return+0x4e/0x7d0
[  243.133764]  [<ffffffffa00691b0>] ? bnx2x_sp_rtnl_task+0x0/0x700 [bnx2x]
[  243.133769]  [<ffffffff8153962b>] mutex_lock+0x2b/0x50
[  243.133773]  [<ffffffff8147ba45>] rtnl_lock+0x15/0x20
[  243.133786]  [<ffffffffa00691e0>] bnx2x_sp_rtnl_task+0x30/0x700 [bnx2x]

[  602.933395]  [<ffffffff810a101e>] kthread+0x9e/0xc0
[  602.933400]  [<ffffffff8100c28a>] child_rip+0xa/0x20
[  602.933405]  [<ffffffff810a0f80>] ? kthread+0x0/0xc0
[  602.933408]  [<ffffffff8100c280>] ? child_rip+0x0/0x20
[  642.290303] bnx2x: [bnx2x_init_firmware:12991(eth1)]Can't load firmware file bnx2x/bnx2x-e2-7.10.51.0.fw
[  642.290308] bnx2x: [bnx2x_func_hw_init:5521(eth1)]Error loading firmware
[  642.290319] bnx2x: [bnx2x_nic_load:2679(eth1)]HW init failed, aborting