On Sat, 01 Feb 2014 14:41:22 -0500 (EST), Henrique de Moraes Holschuh wrote:
> On Sat, 01 Feb 2014, Stephen Powell wrote:
>> On second thought, maybe I spoke too soon.  There is another place
>> where I can check the microcode levels:
>> 
>> /sys/devices/system/cpu/cpu0/microcode/version: 0x6000822
>> /sys/devices/system/cpu/cpu1/microcode/version: 0x600081c
>> /sys/devices/system/cpu/cpu2/microcode/version: 0x6000822
>> /sys/devices/system/cpu/cpu3/microcode/version: 0x600081c
>> 
>> What's going on here?
> 
> Kernel bug for sure.
> 
> The fact that sysfs conflicts with /proc/cpuinfo is a sure bet it is caused
> by broken caching of information inside the kernel somewhere, let's track it
> down.
> 
> What kernel are you using *exactly* to get that mismatch?  Is it one of the
> kernel.org kernels?

This is a stock Debian kernel.  The Debian package name is
linux-image-3.11-2-amd64, and the package version is 3.11.10-1.
It used to be the current kernel in Debian testing (jessie) but is now
one level back.  The current testing kernel is a 3.12 kernel, but I can't
even get that one to boot.  The kernel I'm using is available for download
on snapshot.debian.org, which is how I got my current copy of it.  This
is a binary kernel image package of course, not a source package.

The corresponding Debian kernel source package would be
linux-source-3.11, version 3.11.10-1, which should also be available on
snapshot.debian.org.  (Though it contains kernel source, this package is
still classified as a "binary" package, as far as the Debian package management
system is concerned; so you have to look for it on snapshot.debian.org as a
binary package, and you have to be root to install it.)
> 
> Can you resend the /proc/cpuinfo contents *for the kernel with the mismatch,
> while the mismatch is happening* just to make triple sure I don't look at
> the wrong one/forward the wrong one by mistake?

Yes, I'll do that; but I can't do it right now.  I've varied processors one
and three offline, and it has made my previously unstable system stable.
I'm in the middle of doing something long-running on it right now, and
once that is finished, I can vary those processors online again.  I can even
reboot if necessary.  But not right now.  I have to wait for the long-running
process to finish first.

-- 
  .''`.     Stephen Powell    
 : :'  :
 `. `'`
   `-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to