Home » Intel Manuals » Motherboards » Intel BB5000XALR » Manual Viewer

Intel BB5000XALR Specification Update - Page 30

Microsoft Windows* operating systems installed without a service pack, will display blue screen

Add to My Manuals
Save this manual to your list of manuals

Page 30 highlights

Enterprise Platforms and Services Marketing Monthly Specification Update Problem Implication Status Workaround When running certain Red Hat* Enterprise Linux on the Intel® Server Board S5000PAL with video driver ati_drv.o 6.5.6, the System Event Log (SEL) may report an IERR event. Additionally, the keyboard and mouse may not respond until an AC power cycle is applied to reboot the system. Stressing the video controller on the Intel® Server Board S5000PAL running RHEL3U8, RHEL4U4, and RHEL4U5 can induce timeout errors caused by the default video driver (ati_drv.o 6.5.6). These errors trigger IERRs, which cause the system to stop responding. You can obtain register dumps if the system is instrumented for NMI. This erratum is fixed in Red Hat* Enterprise Linux 5 and later releases. Users can load the VESA video driver rather than the ati_drv.o 6.5.6 video driver to prevent IERRs. 51. Microsoft Windows* operating systems installed without a service pack will display blue screen with BIOS 79 and 81 Problem If a user attempts to install a Microsoft Windows* operating system without an integrated service pack, it will display a blue screen during the installation process if BIOS 79 or BIOS 81 is on the server board. Conversely, if a user upgrades the system BIOS to BIOS 79 or 81 prior to installing the appropriate service pack, the system will display the blue screen. Starting in BIOS 79, support for enhanced sleep states was added. This addition to the BIOS requires that the Microsoft Service Pack* be integrated into the operating system installation process to understand the extended sleep state support. The following is a list of Microsoft* operating systems and required service packs: • Microsoft Windows 2003*, 32-bit and 64-bit, requires Service Pack 1 • Microsoft Windows 2003 SBS* requires Service Pack 1 • Microsoft Windows XP*, 32-bit and 64-bit, requires Service Pack 2 Implication Users cannot install Microsoft Windows* or upgrade the system BIOS to BIOS 79 or BIOS 81 without a service pack integrated into the installation process. Status This erratum was fixed in BIOS R0084. Users need to upgrade BIOS to R0084 or a later version, then disable Deep C-state Support in the BIOS setup (Advanced BIOS menu -> Processor sub menu) before installing or booting a Microsoft Windows* operating system without the required service pack. Workaround Users need to remain on BIOS 76, use a Microsoft Windows* installation process that includes the service pack integrated into the installation, or install Microsoft Windows* and the required service pack prior to updating to BIOS 79 or 81. Additionally, the R2 release versions of Microsoft Windows* do not exhibit this issue. Use of this version of Microsoft Windows*, if possible, is also another valid workaround. 24

Section	Page
Preface	7
Summary Tables of Changes	8
Errata	11
1. IPMI over serial direct connect not supported	11
2. Serial over LAN and IPMI over LAN connections may terminate unexpectedly under certain conditions	11
3. Intermittent beep code 1-5-2-1 when booting with two processors	11
4. Power supply population errors may not display in the SEL	11
5. Fan 5 may report a reading of 0 RPM after the BMC is updated	12
6. The BMC may not respond to the IPMI command, Send Message sent via LAN	12
7. Fans may take a long time to slow down after fan boosting	13
8. System requires ~35 seconds after AC power is applied before the power button responds	13
9. SEL events for Hot-swap Controller (HSC) may appear after a DC cycle	13
10. Fans may run faster than expected after exiting BIOS setup	13
11. System fault LED may report incorrect status for some events	14
12. Fan removal does not generate a SEL event	14
13. Power supply redundancy state is misleading when only one power supply is installed	15
14. Hot-swap Controller (HSC) and Local Control Panel (LCP) updates may take a long time	15
15. Console Redirection Baud Rate Setting auto changing to 19.2K with Serial Over LAN (SOL) active	15
16. Serial Over LAN (SOL) unable to redirect DOS output	16
17. Password on boot not supported	16
18. Intel® Embedded Server RAID Technology II option is not enabled in initial BIOS release	16
19. HSC and BMC versions intermittently not seen in BIOS setup	16
20. Intel® Server Boards S5000PAL/S5000XAL and Intel® Server System SR1500AL show a “Changes in Hardware or Drivers Detected” error message during WHQL ACPI stress testing	17
21. POST LEDs do not turn off after operating system loads	17
22. Checkup7.exe (microcode update utility) is not storing microcode in BIOS	18
23. Intel® RAID Controller SRCSAS144E causes systems to reset multiple times before completing POST	18
24. Change Logo Utility does not save modified BIOS capsule files with correct extension	19
25. PS/2 keyboards and mice may stop functioning after Red Hat* Enterprise Linux is installed	19
26. Failures seen installing to a SATA drive when SATA is set to “Legacy” in the BIOS setup	20
27. System hangs after disabling on-board video in the BIOS setup	20
28. The SMBIOS entry point may not be visible under certain hardware configurations	20
29. Intel® Embedded Server RAID Technology II and I/O module IRQ routing conflict	21
30. SuSE* Linux Enterprise Server may not install successfully with Intel® Embedded Server RAID Technology II enabled	21
31. Red Hat* Enterprise Linux 4 and BIOS setup display a different L2 cache size for the Quad-Core Intel® Xeon® processor 5300 Series	22
32. Change Logo Utility causes BIOS corruption	22
33. Microsoft Windows System Event Viewer* may record Error Event with ID 11	22
34. After the system reboots, the POST screen may generate \	23
35. Intel® RAID Web Console 2 utility displays “Unexpected Sensor” warning message in Microsoft Windows* operating system	23
36. Random drives may go offline when a sixth drive is installed and Intel® Embedded Server RAID Technology II is enabled in the Intel® Server System SR2500ALBRP	24
37. Intel recommends enterprise-class hard drives for use with Intel® Server Systems	24
38. Dual Gigabit Expansion Module may not properly reset	24
39. SAS drive in a ROMB RAID 5 may drop offline during a reboot in the Intel® Server System SR2500PALLX	25
40. Intel® Server System SR2500ALLX sixth hard drive filler panel is difficult to remove	25
41. SuSE* Linux Enterprise Server unable to boot after basic installation	26
42. Drives may not be detected or may go offline in the Intel® Server System SR2500ALBRP when operating at SATA 3GB/s data rate	26
43. New versions of BMC firmware with previous versions of BIOS cause system POST failure	27
44. Intel® Server System SR2500ALLX may operate louder than expected	27
45. Red Hat* Enterprise Linux may report the wrong processor speed	27
46. The SuSE* Linux Enterprise Server 10 driver for SAS HW RAID causes unwanted error logs during installation	27
47. IERR or thermal trip event reported in System Event Log (SEL) after system power on	28
48. USB device generates “The following boot-start or system-start driver(s) failed to load: i8042prt\	29
49. Microsoft Windows* and Intel® RAID Web Console II report an error when the ASR2500SATAPE kit is used	29
50. System may log IERRs when running certain Red Hat* Enterprise Linux versions on the Intel® Server Board S5000PAL with video driver ati_drv.o 6.5.6	29
51. Microsoft Windows* operating systems installed without a service pack will display blue screen with BIOS 79 and 81	30
52. Sluggish system performance may be experienced with BMC 60	31
53. Downgrading the firmware of the Integrated RAID (ROMB), Intel® Embedded Server RAID Technology II, or SAS may cause system damage	31
54. In the Intel® Server Systems SR2500ALLX and SR1550ALSAS, flashing of SAS firmware 1.22 and SAS BIOS 06.16.00 makes hard drive #1 (upper left drive tray) undetected during SAS controller scanning	31
55. Microsoft Windows 2003 R2 SP2* may display blue screen during an operating system boot or shutdown with a specific version of Intel( I/OAT driver	32
56. Server System Event Log (SEL) time may be one day later than BIOS time after entering year 2008.	33
57. Performance Power Management Error in Microsoft Windows Server 2008*	33
58. Midplane2 hardware RAID produces unexpected beep sounds during system POST	34
59. Platform Confidence Test (PCT) fails with BIOS 89/91 on Intel® Server Board S5000PAL/S5000XAL	34
60. USB mouse may hang in BIOS 94 RAID Console	34
61. PCI IBIST Error with BIOS 84	35
62. System May Hang during Login or Shutdown	35
63. Hard Disks Are Difficult to Install in Intel® Server System SR2500AL and Intel® Server Chassis SR2500	35
64. System May not Boot After Multiple DC power Cycles with BIOS Revision R0098	36
65. System will not skip CD/DVD drive with BIOS Revision R0098 when RMM2 installed	36
66. Please use AXXMINIDIMM512 as the replacement solution for AXXMINIDIMM which is EOLed	37
67. Minus “year” number to go past “2000” at BIOS “system date” set up interface will cause the server system to hang	37
68. Please do not downgrade BIOS from factory shipped BIOS 101 to any previous version	37
69. The Serial Port Console Redirection displays the Adaptec® 5805 RAID Configuration Utility incorrectly	38
Documentation Changes	39
1. The SMBUS block diagram (Figure #16) provided in Rev. 1.1 of the Intel® Server Board S5000PAL/S5000XAL TPS requires changes to accurately reflect production hardware design	39
2. The power block diagram (Figure #25) as provided in Rev. 1.1 of the Intel® Server Board S5000PAL/S5000XAL TPS does not reflect the final, production-level baseboard design	40
3. SAS/SAS RAID midplane board (Figure #22) as provided in Rev.1.0 of the Intel® Server System SR2500AL TPS should swap the descriptions of items A and K	41

Match case Limit results 1 per page

Enterprise Platforms and Services Marketing

Monthly Specification Update

Problem

When running certain Red Hat* Enterprise Linux on the Intel

Server Board

S5000PAL with video driver ati_drv.o 6.5.6, the System Event Log (SEL) may

report an IERR event. Additionally, the keyboard and mouse may not respond

until an AC power cycle is applied to reboot the system.

Implication

Stressing the video controller on the Intel

Server Board S5000PAL running

RHEL3U8, RHEL4U4, and RHEL4U5 can induce timeout errors caused by the

default video driver (ati_drv.o 6.5.6). These errors trigger IERRs, which cause

the system to stop responding. You can obtain register dumps if the system is

instrumented for NMI.

Status

This erratum is fixed in Red Hat* Enterprise Linux 5 and later releases.

Workaround Users can load the VESA video driver rather than the ati_drv.o 6.5.6 video

driver to prevent IERRs.

51.

Microsoft Windows* operating systems installed without a service pack

will display blue screen with BIOS 79 and 81

Problem

If a user attempts to install a Microsoft Windows* operating system without an

integrated service pack, it will display a blue screen during the installation

process if BIOS 79 or BIOS 81 is on the server board. Conversely, if a user

upgrades the system BIOS to BIOS 79 or 81

prior

to installing the appropriate

service pack, the system will display the blue screen. Starting in BIOS 79,

support for enhanced sleep states was added. This addition to the BIOS

requires that the Microsoft Service Pack* be integrated into the operating

system installation process to understand the extended sleep state support.

The following is a list of Microsoft* operating systems and required service

packs:

•

Microsoft Windows 2003*, 32-bit and 64-bit, requires Service Pack 1

•

Microsoft Windows 2003 SBS* requires Service Pack 1

•

Microsoft Windows XP*, 32-bit and 64-bit, requires Service Pack 2

Implication

Users cannot install Microsoft Windows* or upgrade the system BIOS to BIOS

79 or BIOS 81 without a service pack integrated into the installation process.

Status

This erratum was fixed in BIOS R0084. Users need to upgrade BIOS to R0084

or a later version, then disable Deep C-state Support in the BIOS setup

(Advanced BIOS menu -> Processor sub menu) before installing or booting a

Microsoft Windows* operating system without the required service pack.

Workaround Users need to remain on BIOS 76, use a Microsoft Windows* installation

process that includes the service pack integrated into the installation, or install

Microsoft Windows* and the required service pack prior to updating to BIOS 79

or 81. Additionally, the R2 release versions of Microsoft Windows* do not

exhibit this issue. Use of this version of Microsoft Windows*, if possible, is also

another valid workaround.