Description of problem: On a RHEL4.8 GASnapshot3 host with QLogic FC HBA, kernel panics when the QLogic FC HBA driver is reloaded after mapping few LUNs from NetApp Storage Controller. Version-Release number of selected component (if applicable): OS - RHEL4.8 GASnapshot3 kernel - 2.6.9-86.ELsmp QLogic FC HBA driver version: v.8.02.09.01.04.08-d How reproducible: Always Steps to Reproduce: 1. Install RHEL4.8 GASnapshot3 on a host with QLogic FC HBA 2. Map LUNs from a NetApp storage controller 3. Reload the qla2400 module (as it is 4GB FC HBA) # modprobe -r qla2400 # modprobe -v qla2400 4. kernel panics after reloading the QLogic FC HBA driver Actual results: kernel panics after reloading the QLogic FC HBA driver when LUNs are mapped to the host.(Attached the log collected during kernel panic). Expected results: kernel should not panic. Additional Info: This issue was not seen in RHEL4.8 GASnapshot2 or earlier(Previous Releases).
Created attachment 339681 [details] Attaching the kernel panic message Attaching the kernel panic message
There is a fix in snap 4, kernel -87, that may be relevant. The fix removes some qla sysfs values that cause hangs when they are read (like at boot time and module load). Can you try snap 4, or just switch to the -87 kernel?
I concur with Tom C. Please try the -88 kernel. You could also apply the patch in BZ 476704. The patch removed the sysfs entries which were causing a locking problem. These entries were unsupported and when other fixes were made to the driver they became broken. These entries are read in an automated fashion and are not required ( board nvram contents ).
This issue is not seen in snap4(kernel v2.6.9-87).