WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-bugs

[Xen-bugs] [Bug 1624] New: Incorrect "cpu MHz" in /proc/cpuinfo

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1624] New: Incorrect "cpu MHz" in /proc/cpuinfo
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Mon, 7 Jun 2010 07:22:30 -0700
Delivery-date: Mon, 07 Jun 2010 07:22:39 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1624

           Summary: Incorrect "cpu MHz" in /proc/cpuinfo
           Product: Xen
           Version: unspecified
          Platform: x86-64
        OS/Version: Linux-2.6
            Status: NEW
          Severity: minor
          Priority: P2
         Component: Linux-pv_ops domU
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: major.hayden@xxxxxxxxxxxxx


I've tested 2.6.32.12 and 2.6.32.15 from kernel.org and both display the
incorrect cpu MHz in the /proc/cpuinfo output when compiled for the x86_64
arch.  The i386 kernels are unaffected and display the correct MHz for the CPU
in /proc/cpuinfo.

Kernel .config and /proc/cpuinfo output to follow.


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs

<Prev in Thread] Current Thread [Next in Thread>