Comment 49 for bug 1561019

I cannot reproduce this with 3.16.0-0.rc3.git2.1.fc21.x86_64

I suspect the kernel has been modified to workaround buggy
CPUID.

Previously:

[ 5.150258] async_tx: api initialized (async)
[ 5.152459] xor: automatically using best checksumming function:
[ 5.153064] invalid opcode: 0000 [#1] SMP

Now:

[ 2.198939] async_tx: api initialized (async)
[ 2.201931] xor: measuring software checksum speed
[ 2.212021] prefetch64-sse: 16340.000 MB/sec
[ 2.222012] generic_sse: 15188.000 MB/sec
[ 2.222856] xor: using function: prefetch64-sse (16340.000 MB/sec)
[ 2.239949] md: raid6 personality registered for level 6
[ 2.241063] md: raid5 personality registered for level 5
[ 2.242168] md: raid4 personality registered for level 4
[ 2.244093] md/raid:md127: device sda operational as raid disk 0
[ 2.247075] md/raid:md127: allocated 0kB
[ 2.247939] md/raid:md127: raid level 5 active with 1 out of 2 devices, algorithm 2
[ 2.249726] md127: detected capacity change from 0 to 103809024
[ 2.253250] md: recovery of RAID array md127
[ 2.255054] md: minimum _guaranteed_ speed: 1000 KB/sec/disk.
[ 2.256554] md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery.
[ 2.258584] md: using 128k window, over a total of 101376k.
mdadm: array /dev/md/md started.