- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Problems have been found in an LAPACK internal function in Intel MKL 11.0 update 3 (available in Intel® Composer XE 2013 update 3) which can cause many other LAPACK functions to crash or provide incorrect results. The problem is related to an operation that divides work among threads for a certain class of LAPACK functions that are bandwidth limited, but can still benefit from some parallelism. The problem occurs when a thread count greater than 4 and not divisible by 4 is chosen. For a list of all affected functions, please refer to our knowledgebase article on this topic.
A patch is available from the knowledgebase article or the download pages at the Intel registration center site.
Workaround: explicitly set the number of threads to 1,2,3, or 4n (where n is an integer greater than 1)
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Workaround does not work for 4n (n > 1). http://software.intel.com/en-us/forums/topic/390568
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Are you using a system with less than 8 physical (as opposed to HT virtual cores)? I see you reference "i7-990x" which has six cores, so if this a single socket system, Intel MKL is probably dialling your 8 threads setting back to 6 threads and you're back into the problem case.
I'll double check, but it seems the the extra information I should add on this workaround is that 4n should be less than the number of 'physical' cores on your system.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We've uploaded a patch that you can access from the knowledgebase article or the download pages at the Intel registration center site.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
the fix of the problem available in 11.0 update 4 which released the last week.

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page