Kernel Panic Occurred After Upgrade hpsa Version to 3.4.6

XenServer host freeze after applying??hpsa driver version 3.4.6.

To use version 3.4.6, complete the following steps:
??
Note: mkinitrd in XenServer 6.2 SP1 dom0 ignores /etc/modprobe.d/*

1. Enter menu from boot prompt.

2. Select fallback kernel to startup host.

3. Modify /etc/modprobe.conf, add "options hpsa hpsa_allow_any=1" to the end of the file on separate row. Save the file.

4. Backup the original XS62ESP1024 kernel initrd (init ram disk) in /boot.

5. Change directory to /boot: cd /boot.

6. mv initrd-2.6.32.43-0.4.1.xs1.8.0.861.170802xen.img initrd-2.6.32.43-0.4.1.xs1.8.0.861.170802xen.img.old

7. regenerate the initrd: mkinitrd initrd-2.6.32.43-0.4.1.xs1.8.0.861.170802xen.img 2.6.32.43-0.4.1.xs1.8.0.861.170802xen

8. Reboot host

Boot the default xe kernel (latest) should be successfully.
??
Note: For hosts that haven't got XS62ESP1024 applied, technically we just need to do step 1. Because when installing the new kernel images it should generate a new initrd and the changes in /etc/modprobe.conf are expected to be picked up.
??
To use previous version 3.4.4, complete the following steps:
??
1. Enter menu from boot prompt.
??
2. Select fallback kernel to startup host.
??
3. Modify /etc/modprobe.conf, add "options hpsa hpsa_allow_any=1" to the end of the file on separate row. Save the file.
??
4. Uninstall the driver, using the following commands:
==============
rpm -qa | grep hpsa
hpsa-modules-kdump-2.6.32.43-0.4.1.xs1.8.0.855.170800-3.4.6_170-1
hpsa-modules-xen-2.6.32.43-0.4.1.xs1.8.0.855.170800-3.4.6_170-1
rpm -e hpsa-modules-kdump-2.6.32.43-0.4.1.xs1.8.0.855.170800-3.4.6_170-1
rpm -e hpsa-modules-xen-2.6.32.43-0.4.1.xs1.8.0.855.170800-3.4.6_170-1
==============
??
5. Download and install previous version of hpsa driver v3.4.4 from following URL, the install script will re-create the boot images and during that procedure will read the /etc/modprobe.conf.
??
Driver Disk for HP hpsa v3.4.4_125-1 - For XenServer 6.2.0
http://support.ctx.org.cn/CTX140548.citrix
??
6. reboot

XenServer hang up issue occurred due to hpsa driver did not explicitly recognize the hardware

hpsa.hpsa_allow_any=1 give hpsa driver the option to handle any device it detect and not just the ones listed.

The cciss driver previously contained a feature which would enable it by default to run on Smart Array controllers which it did not explicitly recognize except so far as to be able to determine that they were some sort of Smart Array. This feature has been removed, as any Smart Arrays not known to cciss are now presumed to be claimed by the hpsa driver. The hpsa driver has the ability to claim unknown Smart Arrays, however this is turned off by default so that it does not try to claim older controllers meant to be claimed by the cciss driver. To enable this feature of hpsa, the module parameter hpsa.hpsa_allow_any=1 can be used.

Citrix Discussions -??Kernel panic on patching to 6.2 SP1