Just guessing, but a possible candidate...
https://github.com/torvalds/linux/commit/8cc7669355136f8952779e6f60053c1284d59c4d
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800752
Title:
Performance
FYI: Boiled it down to a simple ioctl() call.
= Start code =
/* Read an ioctl value */
#include
#include
#include
#include
#include
#include
#include
#include
int main(void) {
int eu_total;
drm_i915_getparam_t gp;
gp.value = &eu_total;
gp.param = I915_PARAM
And, just for confirmation, with the older Bionic 4.15.0-38-generic
kernel I get:
>> root@nuc:/local/users/gml4410/homework# ./gmltest
>> Got value: 48
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
>> BOINC running - haven't had sufficient time to check relative
processing speed yet.
I can confirm that it is back to "full speed". Jobs are taking ~12,000s
again.
I've rebooted to the previous Bioinc kernel (still there from the upgrade) and
when I run clinfo there I see:
kernel says 48 com
> I suppose the question now is why did teh code get 48 in Bionic, but only get
> 24 in Cosmic?
Agreed; I'll look into this later.
> And how to report the bug in the build logic for finding python...
Here is enough. (It's probably in beignet, not dpkg-buildpackage, and not new:
packages for dis
The dh_auto_configure reports this:
-- Found PythonInterp: /usr/bin/python (found version "2.7.15")
I've added a python symlink (to python3) in /usr/local/bin to get the
build to run.
but there's a bug in the build logic somewhere.
--
You received this bug notification because you are a membe
Built and installed beignet-opencl-icd_1.3.2-4_amd64.deb with the patch.
clinfo now reports (4 times):
kernel says 24 compute units, hardcoded says 48
Peak GFLOPS reported by BOINC now back at 384.
BOINC running - haven't had sufficient time to check relative processing
speed yet.
System has
Looks like there's a bug in dpkg-buildpackage!?!
There's a update_metainfo_xml.py which, from line1, expects to be run by
python3. but
a) it isn't marked as executable.
b) it produces an error when run by dpkg-buildpackage. A complaint about the
encoding= parameter, so it looks like it's being r
Well spotted - BOINC "GFLOPS peak" is the theoretical 8 * compute units
* max clock (not an actual speed measurement), and matches the 24
compute units clinfo reports, not the 48 compute units this GPU is
supposed to have.
Beignet can take this value from an internal hardcoded list (in
src/cl_devi
If it's any help here is the info from the last BOINC startup log under
Bionic and the first under Cosmic.
Bionic:
28-Oct-2018 11:12:30 [---] Starting BOINC client version 7.7.0 for
x86_64-pc-linux-gnu
28-Oct-2018 11:12:30 [---] This a development version of BOINC and may not
function properly
2
Just noticed that the logs in #4 show a difference in the reported GFLOPS peak.
Bioinc says 384, while Cosmic says 192.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800752
Title:
Performance degra
>> Was this report sent from the affected system?
No - sorry. I forgot about that
This is clinfo from the affected system:
Welcome to Ubuntu 18.10 (GNU/Linux 4.18.0-10-generic x86_64)
* Documentation: https://help.ubuntu.com
* Management: https://landscape.canonical.com
* Support:
Was this report sent from the affected system? as it says the CPU is an
i5-2500K, which is too old for beignet. (It shouldn't crash, but won't
be running the computations, so the slowdown is probably from some other
package.)
Please post the output of clinfo (from the clinfo package).
** Change
13 matches
Mail list logo
