SCIENTIFIC-LINUX-USERS Archives

January 2012

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Fumihito YOSHIDA <[log in to unmask]>
Reply To:
Fumihito YOSHIDA <[log in to unmask]>
Date:
Sat, 7 Jan 2012 11:42:50 +0900
Content-Type:
text/plain
Parts/Attachments:
text/plain (23 lines)
On Fri, Jan 06, 2012 at 12:29:50PM -0800,[log in to unmask] wrote:
> > Is the problem only on 64-bit machines? The one I have at 252 days
> > uptime is 32-bit.
> 
> According to what I've read, (1) the bug occurs on both 32-bit and
> 64-bit machines;  (2) virtual machines are not affected; (3) only the
> Intel CPU (Pentium4 or newer) is relevant.

IMHO, (2) is not true. Real condition is "using TSC". 

In old days(-2008?), virtual machines use jiffies or pit 
implementations. So, they are not affected. However, in 
our time, many vm use PV and virtual TSC, their systems 
are affected.

e.g. Case of VMware, VMware ESX 4.0 / ESXi 4.0 / VMware
     Workstation 7.0 PV systems use virtual TSC.

In ubuntu[1], kernel 2.6.32(ubuntu) crashed out with
suspicious behavior of this bug, that running on vSphere.

[1] https://bugs.launchpad.net/bugs/805341

ATOM RSS1 RSS2