Your message dated Mon, 15 Jan 2018 15:07:59 +0000
with message-id <[email protected]>
and subject line Bug#856806: fixed in i7z 0.27.2+git2013.10.12-g5023138-4
has caused the Debian Bug report #856806,
regarding i7z: Possible wrong output with Nehalem
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
856806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856806
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: i7z
Version: 0.27.2+git2013.10.12-g5023138-3
Severity: normal

Dear Maintainer,

Running i7z in i7-870 Nehalem, it prints "i7z DEBUG: Detected a
nehalem (i7/i5/Xeon) - 45nm" first and "i7z DEBUG: guessing Haswell"
near the end. Haswell is a different newer family (i7-4170 eg, Sandy
and Ivy are generations between it and Nehalem).

The file helper_functions.c around line 420 has:

            *nehalem = true;
            *sandy_bridge = false;
            *ivy_bridge = false;
            *haswell = true;

And other blocks always set one to true and the other three to false.
Could that be a bug and the reason for the mixed reports? Just setting
last to false could fix it, if no more tests needed to differentiate.

The program also reports two conflicting values once running, first
"True Frequency (without accounting Turbo) 2942 MHz" and below "Max
Frequency without considering Turbo 3075.73 MHz (133.73 x [23])".

The official value is ~2.9 GHz, the 23 multiplier is between official
normal max (22) and minimum turbo (24 and up).

Again I looked at the code, and in i7z_Single_Socket.c below line 285
I see it adds one when TURBO_MODE is 1. Maybe wrong? Maybe it should
use another string to explain why? In other similar part of the file,
below line 944, it says "True Frequency" instead (safety margin to
allow transitions to/from turbo modes?). That function seems to be
commented out.

Other than those two, all looks OK. It even let me notice a bug in
"cpupower frequency-info -n", which seems to be confused too and
reports turbo levels as X * 100 instead of X * 133 (Nehalem vs newer),
with the absurd result of normal max being well above the single core
turbo.

Thanks,
GSR
 

-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.7.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages i7z depends on:
ii  libc6                         2.24-9
ii  libncurses5                   6.0+20151024-2
ii  libtinfo5                     6.0+20151024-2
ii  msr-tools                     1.3-2
ii  ruby                          1:2.1.0.4
ii  ruby1.8 [ruby-interpreter]    1.8.7.358-7
ii  ruby1.9.1 [ruby-interpreter]  1.9.3.194-8.1+b1
ii  ruby2.1 [ruby-interpreter]    2.1.2-3

i7z recommends no packages.

i7z suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: i7z
Source-Version: 0.27.2+git2013.10.12-g5023138-4

We believe that the bug you reported is fixed in the latest version of
i7z, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann <[email protected]> (supplier of updated i7z package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Mon, 15 Jan 2018 15:01:52 +0100
Source: i7z
Binary: i7z
Architecture: source
Version: 0.27.2+git2013.10.12-g5023138-4
Distribution: unstable
Urgency: medium
Maintainer: Andreas Beckmann <[email protected]>
Changed-By: Andreas Beckmann <[email protected]>
Description:
 i7z        - reporting tool for i7, i5, i3 CPUs
Closes: 800323 856806 874909
Changes:
 i7z (0.27.2+git2013.10.12-g5023138-4) unstable; urgency=medium
 .
   * Stop building and shipping the Qt4 GUI.  (Closes: #874909, #800323)
   * nehalem.patch: Fix some nehalem detected as haswell, too.
     (Closes: #856806)
   * Set Priority to optional.
   * Bump Standards-Version to 4.1.3.
   * Use https:// URLs.
   * Switch to debhelper compat level 11.
Checksums-Sha1:
 35cf81d2269eceeeb50f9b66b2540ae4347ac2ad 2026 
i7z_0.27.2+git2013.10.12-g5023138-4.dsc
 4a40fe72843fc7e44262e158553348d515e44b49 6288 
i7z_0.27.2+git2013.10.12-g5023138-4.debian.tar.xz
 67ecf4808a332a3967ef388dacd0bb089b00ab0a 5769 
i7z_0.27.2+git2013.10.12-g5023138-4_source.buildinfo
Checksums-Sha256:
 7be52119214209187e29125f08ba97707b7a53812168c21b59affc1750f61698 2026 
i7z_0.27.2+git2013.10.12-g5023138-4.dsc
 a440c8a5c83063b0db7c2127d999525306c9f50bdb3113db34e81a0b8a0be2cb 6288 
i7z_0.27.2+git2013.10.12-g5023138-4.debian.tar.xz
 aa775cee63e280e1d072f9a21e764b6e3c5b2d53e897087fa2dfbbdc25720ab7 5769 
i7z_0.27.2+git2013.10.12-g5023138-4_source.buildinfo
Files:
 179288736bca3f583ae85815f94b31a5 2026 admin optional 
i7z_0.27.2+git2013.10.12-g5023138-4.dsc
 a1c27098bea5de97c23e5679c7e5c90d 6288 admin optional 
i7z_0.27.2+git2013.10.12-g5023138-4.debian.tar.xz
 85891e0e02306f7bf13ea2fdbba8147a 5769 admin optional 
i7z_0.27.2+git2013.10.12-g5023138-4_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAlpcuGAQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCEk1D/9abmuBRy4t4QzIY/QZ5GRl5GkEUcPv0+kj
0Zg5kgyad20eFlQOtXSQtS9jhAfQur+ab43cUbTeZmfgzMldJzFMHozDqH043dJR
qvrwTp6WxT7CQEd0PdgejeRfD/PPVkiBbPN9AtK/5x3swHGkuL5ln/iv/gfdEoes
E6QNaUqNjYI36/+fAuETDoV7JM2PHr0j9aDt7H5b5eqU6Xw3elm+rzOKH+OPRCLl
hh7QSUFrkvW3bdqHPbFOP/iYFZ6GgQLsxKz2BuFDFIQ1S0Hl2qfAvk458Ym6Ymae
RYZWFHjhq05pQZvV28CNVHVOuLKTq+Kat+MQP03jbGQs1PAisZsXaQSQVSrFnKHk
5FpZLKWln1Ine1sqr6xjs1236FnJJdeHXfOd8yMpDaG7bpC8vE1coo1ZNJ0iG5Nb
5eYLomg00iOv/pVul+xR19+aUkPudK2mAZC4gKaxbuzlpU5P6hL0OC1bYK8fhlY/
AFbZXUxFcZEuv5lT3CAZPwgX48VHQQK9XMxv+/occ4vnNXFdD232m/CbIDOdZ9j7
S5lC/QEJgbT51nAlHg+xPQ23Os9cwcCaZM58VqrunQLJoxE4JFDCmgdLffApH/Lw
mWY1VoRKyu8n3Hj8EK9EJuoLzkH6FVmEv9Da91DnP4wfsQ7vL/dQYavo0uOfMpzP
syL087dCzQ==
=I+tW
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to