Users Guide

18–Troubleshooting
Kernel Debugging Over Ethernet
301 BC0054508-00 M
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: The Marvell 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.
Problem: Cannot configure Resource Reservations in QCC after SNP is
uninstalled.
Solution: Reinstall SNP. Prior to uninstalling SNP from the system, ensure that
NDIS is enabled by selecting the check box on the Resource Configuration
window, available from the Resource Reservations section of the Configurations
page. If NDIS is disabled and SNP is removed, there is no access to re-enable the
device.
Problem: A DCOM error message (event ID 10016) appears in the System Even
Log during the installation of the Marvell adapter drivers.
Solution: This problem is a Microsoft issue. For more information, see Microsoft
knowledge base KB913119 at http://support.microsoft.com/kb/913119
.