FW82371EB Intel, FW82371EB Datasheet - Page 26

• Manufacturer Part Number: FW82371EB
• Manufacturer: Intel

Specifications of FW82371EB

• Lead Free Status / RoHS Status: Not Compliant

Intel
18.
Problem:
Implication: The Operating System will think that it is safe to enter a C3 state and will then disable the arbiter and
Workaround: In the OS power management code (ACPI.SYS) include a test of the BMIDE status register in code that
Status:
19.
Problem:
Implication: The host controller response to this is a non acknowledge with a CRC/Timeout status communicated to
Workaround: There are two possible workarounds.
Status:
26
®
82371EB (PIIX4E)
C3 Power State/BMIDE & Type-F DMA Livelock Errata
The PIIX4E does not always correctly reflect BMIDE and Type-F DMA activity on the BMSTS bit in
the Power Management Status Register (PMSTS) of PIIX4 Function 3.
then perform a PLVL3 register read to enter the C3 state, causing LIVELOCK to occur and resulting in a
system hang.
does the entry to C3. If a BMIDE transfer is in progress, do not enter C3. In the OS initialization code,
mDISABLE Type-F DMA is BIOS indicates C3 support. If BIOS indicates that C3 is not supported,
leave Type-F DMA enabled.
This will not be fixed in the PIIX4E. This will be incorporated into the PIIX4/PIIX4E datashet as a
change to the specification. This should be corrected for in ACPI aware operating systems. Contact your
Operating System vendor forn schedule and release information.
USB Dribble Errata
A USB receive packet with a bitstuff following then transmission of CRC, coupled with a dribble bit due
to prop delays through cables and HUBs may be incorrectly interpreted by the USB host controller state
machine as a poorly formed EOP.
the software. If this condition persists the error count associated with this packet will be exceeded and an
interrupt can be generated to software. This will stall the USB device. Current software reports a device
error to the user via a pop up window. Another implication is that the installed base may have limited
USB expandablility via HUBs.
1.
2.
This will not be fixed in the PIIX4E. This will be fixed in future implementations of the UHCI host
controller.
Hardware: Try plugging the USB device into a USB port closer to the root hub.
Software: Detect the CRC/Timeout error and count exceeded and attempt to requeue the packets
while changing the length of the packets. Changing the length of the packets will change the CRC
and thus potentially (likely) remove the combination of the two events causing the failure.
Specification Update
R