Description of problem:
Kdump failed with be2net when using NFS as dump target:
Scanning logical volumes
Reading all physical volumes. This may take a while...
Found volume group "vg_hpbl465cg701" using metadata type lvm2
Activating logical volumes
3 logical volume(s) in volume group "vg_hpbl465cg701" now active
Free memory/Total memory (free %): 76872 / 119672 ( 64.2356 )
mapping eth0 to eth0
be2net 0000:04:00.0: mccq poll timed out
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2.Config Kdump target as NFS
From developer, please try if this could be a workaround.
1) boot the system
2) rmmod be2iscsi
3) touch /etc/kdump.conf ; service kdump restart
4) perform crash
Created attachment 524195 [details]
Kdump with be2iscsi loaded
This is situation when kdump image is created with be2iscsi loaded -> kdump image also loads be2iscsi.
Result: Kernel hangs
Created attachment 524196 [details]
Kdump without be2iscsi
This is situation when kdump image is created with be2iscsi unloaded -> kdump image does not load be2iscsi.
Result: Image successfully created
CCing Mike as the problem will be with be2iscsi.
Jay, this was supposed to be fixed with the patches from here https://bugzilla.redhat.com/show_bug.cgi?id=688076 right? But it looks like the kernel in this bz 196 has the patches (688076 indicates the patches went into 195).
Yes and I had verified it works.
I am wondering if there can be anything to do with NFS because there is a kernel crash in be2iscsi and Redhat was able to save the vmcore
(In reply to comment #7)
> Jay, this was supposed to be fixed with the patches from here
> https://bugzilla.redhat.com/show_bug.cgi?id=688076 right? But it looks like the
> kernel in this bz 196 has the patches (688076 indicates the patches went into
This is kdump issue not kexec. In kexec case be2iscsi_shutdown is called, but in kdump case not... So the patches in bug #688076 cannot fix this issue.
(In reply to comment #8)
> Yes and I had verified it works.
> I am wondering if there can be anything to do with NFS because there is a
> kernel crash in be2iscsi and Redhat was able to save the vmcore
I don't know, but the vmcore was probably saved through different NIC...
After several testing rounds I found that be2iscsi could be loaded in kdump initrd, but it has to be loaded *BEFORE* be2net. When the be2iscsi is loaded in kdump environment it is in "crashdump mode" (according source code) and calls the function beiscsi_pci_soft_reset.
Jay, could it be possible that after this reset that the already initialized NIC part of the adapter becomes unresponsive?
Great find. It is possible , I will look into the NIC part and get back
This is happening because I am resetting the chip in kdump mode. So, the be2net is left hanging to resources the chip doesn't recognize.
I have reworked the code to do Function Level Reset ,so, only a particular function is reset. Am compiling it now, will try it out and update
Created attachment 525853 [details]
Fix for kdump failure
This patch should fix the issue.
Now, doing function level reset instead of chip reset when in crash dump mode
Jay, good work... your patch fixes this issue. I'm reassigning this BZ to Mike as the patch is for be2iscsi and not be2net.
Created attachment 526597 [details]
The patch that was submitted to kernel
This is the patch I submitted to the kernel list
Patch(es) available on kernel-2.6.32-209.el6
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.