Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I spoke to an AMD engineer at the Microsoft Build conference about this error, and showed him my repro. He emailed me this morning:</p> <blockquote> <p>We have investigated and found that this is due to a known errata in the Llano APU family. It can be fixed via a BIOS update depending on the OEM – if possible please recommend it to your customers (even though you have a workaround).</p> <p>In case you’re interested, the errata is 665 in the Family 12h Revision Guide (see page 45): <a href="http://support.amd.com/TechDocs/44739_12h_Rev_Gd.pdf#page=45" rel="nofollow noreferrer">http://support.amd.com/TechDocs/44739_12h_Rev_Gd.pdf#page=45</a></p> </blockquote> <p>Here's the description of that erratum:</p> <h1>665 Integer Divide Instruction May Cause Unpredictable Behavior</h1> <h2>Description</h2> <p>Under a highly specific and detailed set of internal timing conditions, the processor core may abort a speculative DIV or IDIV integer divide instruction (due to the speculative execution being redirected, for example due to a mispredicted branch) but may hang or prematurely complete the first instruction of the non-speculative path.</p> <h2>Potential Effect on System</h2> <p>Unpredictable system behavior, usually resulting in a system hang.</p> <h2>Suggested Workaround</h2> <p>BIOS should set MSRC001_1029[31].</p> <p>This workaround alters the DIV/IDIV instruction latency specified in the <em>Software Optimization Guide for AMD Family 10h and 12h Processors</em>, order# 40546. With this workaround applied, the DIV/IDIV latency for AMD Family 12h Processors are similar to the DIV/IDIV latency for AMD Family 10h Processors.</p> <h2>Fix Planned</h2> <p>No</p>
    singulars
    1. This table or related slice is empty.
    1. POIs this "should not happen" crash an AMD Fusion CPU bug?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USBradley Grainger
    1. USBradley Grainger
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POIs this "should not happen" crash an AMD Fusion CPU bug?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIts funny how division instructions always seen to get bugged on x86...
      singulars
      1. PO
      1. USNecrolis
    2. COThe "665 Integer Divide" problem is discussed in the Passmark forums: http://www.passmark.com/forum/showthread.php?3656-AMD-llano-A-series-benchmark-and-CPU-bug A comment there says the problem only happens with dual-channel RAM. So a computer with one 4GB RAM stick and a Llano CPU will probably be fine without the BIOS fix. But if you spend $20 to upgrade to 8 GB, you'll have problems -- which you'll probably (wrongly!) blame on the RAM. Unfortunately, the BIOS "fix" causes a >80% slowdown in Passmark's integer math benchmark, and a >30% reduction in the Passmark score.
      singulars
      1. PO
      1. USDave Burton
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload