Kdump kernel panics in a RHEV hypervisor having traces associated with bnx2fc driver
Issue
-
Upon testing kdump, there are kernel panic traces observed on the console as below:
Kernel panic - not syncing: Fatal exception Pid: 988, comm: insmod Tainted: G D --------------- 2.6.32-431.40.2.el6.x86_64 #1 Call Trace: [<ffffffff81528987>] ? panic+0xa7/0x16f [<ffffffff8152ccc4>] ? oops_end+0xe4/0x100 [<ffffffff81010d3b>] ? die+0x5b/0x90 [<ffffffff8152c7a2>] ? do_general_protection+0x152/0x160 [<ffffffff8152bf75>] ? general_protection+0x25/0x30 [<ffffffff8112fd5f>] ? __free_pages+0x1f/0xa0 [<ffffffff8112fda0>] ? __free_pages+0x60/0xa0 [<ffffffff8112fe29>] ? free_pages+0x49/0x50 [<ffffffff81014880>] ? nommu_free_coherent+0x30/0x40 [<ffffffffa05e9aab>] ? bnx2fc_cmd_mgr_free+0x6b/0x1f0 [bnx2fc] [<ffffffff81528a90>] ? printk+0x41/0x49 [<ffffffffa05eb763>] ? bnx2fc_cmd_mgr_alloc+0x343/0x440 [bnx2fc] [<ffffffffa05e2cae>] ? bnx2fc_ulp_init+0x13e/0x420 [bnx2fc] [<ffffffffa03e0766>] ? cnic_register_driver+0x106/0x170 [cnic] [<ffffffffa05f7224>] ? bnx2fc_mod_init+0x224/0x281 [bnx2fc] [<ffffffffa05f7000>] ? bnx2fc_mod_init+0x0/0x281 [bnx2fc] [<ffffffff8100204c>] ? do_one_initcall+0x3c/0x1d0 [<ffffffff810bc291>] ? sys_init_module+0xe1/0x250 [<ffffffff8100b072>] ? system_call_fastpath+0x16/0x1b
Environment
- Red Hat Enterprise Virtualization Hypervisor (RHEV-H) release 6.5
- bnx2x network driver
- 1 TB RAM
- crashkernel=128M
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
