Users Guide

19–Troubleshooting
Kernel Debugging Over Ethernet
293 BC0054508-00 J
A software defect can cause the system to be unable to BFS boot to an iSCSI or
FCoE target if an iSCSI personality is enabled on the first partition of one port,
whereas an FCoE personality is enabled on the first partition of another port. The
MBA driver performs a check for this configuration and prompts the user when it is
found.
Solution: If using the 7.6.x firmware and driver, to workaround this error,
configure the NPAR block such that if iSCSI or FCoE is enabled on the first
partition, the same must be enabled on all partitions of all four ports of that device.
Kernel Debugging Over Ethernet
Problem: When attempting to perform kernel debugging over an Ethernet
network on a Windows 8.0 or Windows Server 2012 system, the system does not
boot. This problem may occur with some adapters on systems where the
Windows 8.0 or Windows Server 2012 OS is configured for unified extensible
firmware interface (UEFI) mode. You may see a firmware error indicating that a
Non Maskable Interrupt exception was encountered during the UEFI pre-boot
environment.
Solution: Refer to the Microsoft knowledge base topic number 2920163, Non
Maskable Interrupt error during boot on a system which has been configured for
kernel debugging over Ethernet.
Miscellaneous
Problem: The BCM57810 10GbE NIC does not support 10Gbps or 1Gbps WoL
link speed.
Solution: The BCM57810 10GbE NIC can only support 100Mbps WoL link speed
due to power consumption limitations.
Problem: iSCSI Crash Dump is not working in Windows.
Solution: After upgrading the device drivers using the installer, the iSCSI crash
dump driver is also upgraded, and iSCSI Crash Dump must be re-enabled from
the Advanced section of the QCS Configurations page.
Problem: In Windows Server 2008 R2, if the OS is running as an iSCSI boot OS,
the VolMgr error, “The system could not successfully load the crash dump driver,”
appears in the event log.
Solution: Enable iSCSI Crash Dump from the Advanced section of the QCC
Configurations page.
Problem: The QLogic BCM57xx and BCM57xxx adapter may not perform at
optimal level on some systems if it is added after the system has booted.
Solution: The system BIOS in some systems does not set the cache line size and
the latency timer if the adapter is added after the system has booted. Reboot the
system after the adapter has been added.