armel/versatile: unknown HZ value 94

Bug #364656 reported by Loïc Minier
6
Affects Status Importance Assigned to Milestone
procps (Debian)
Fix Released
Unknown
procps (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Hi

When installing Xubuntu in qemu with the armel versatile netboot images, I got some unknown hz values errors on boot.

attaching screenshot

Bye

Related branches

Revision history for this message
Loïc Minier (lool) wrote :
affects: linux (Ubuntu) → procps (Ubuntu)
Changed in procps (Debian):
status: Unknown → Confirmed
Paul Larson (pwlars)
tags: removed: arm
Loïc Minier (lool)
Changed in procps (Ubuntu):
assignee: nobody → David Sugar (dyfet)
Revision history for this message
David Sugar (dyfet-deactivatedaccount) wrote :

Does getconf CLK_TCK also report 94?

There is a relevant debian bug for this; http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=460331 which at least explains why this is reported as invalid.

A common way to compute this is to sleep 1 second and count the difference in timer interrupt events. procps similarly uses /proc/stat to get timer jiffy events, and /proc/uptime to get total system uptime. Roughly, by dividing jiffy events by uptime gives procps the tics per second value it uses, rather than any kernel HZ value actually set. In any case, however it is being derived, any HZ value between 66-94 ticks/second is currently considered invalid in procps, and any value between 95-105 is silently adjusted to 100. This 94 report could be some result of clock skewing under QEMU. The 2.6.30 arm kernel I use on qemu/versatile reports 100.

Revision history for this message
David Sugar (dyfet-deactivatedaccount) wrote :

Decided to patch procps for a relaxed tick range.

Changed in procps (Ubuntu):
status: New → In Progress
Revision history for this message
Oliver Grawert (ogra) wrote :

note that the same occurs on imx51

Revision history for this message
David Sugar (dyfet-deactivatedaccount) wrote :

There are reports of this happening native on i386 hw also. I extended the valid range from 95-105 to 90-105. This is not a great solution, because this really indicates the methodology presently used in procps is not sufficiently reliable, but it should be okay for those having this problem right now.

Revision history for this message
David Sugar (dyfet-deactivatedaccount) wrote :
Revision history for this message
David Sugar (dyfet-deactivatedaccount) wrote :
Revision history for this message
Loïc Minier (lool) wrote :

Looking at the Debian bug, two cleaner fixes seem to be proposed at the end of the bug trail. Let's try to use these instead of extending the HZ matching range.

Revision history for this message
David Sugar (dyfet-deactivatedaccount) wrote :

This is a patch, for Karmic procps 3.2.8-1ubuntu1, that fixes the issue the way suggested at the end of the debian bug list, by assuring the linux version detection actually occurs before init_libproc, hence removing the hack calculation for modern kernels with elf notes. Originally, both init_Linux_version() and init_libproc() were attribute constructor functions, and hence depended on elf loader side effects as to whether the linux version code would happen to be called first. This patch resolves that issue, and I have verified the elf note method returns correctly, and with the 100hz tick value, for ARM kernels. One will also have to use update-initramfs to update the boot ramdisk image with the correct copy of procps binaries.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package procps - 1:3.2.8-1ubuntu2

---------------
procps (1:3.2.8-1ubuntu2) karmic; urgency=low

  * New patch 60_linux_version_init, fixes linux version detection. This
    relied on a side-effect of the elf loader and previously hoped that
    constructors would be called in a certain order. That behavior was
    undefined and hence unreliable. For newer kernels, an elf note is now
    checked to extract HZ tick count. (LP: #364656).

 -- David Sugar <email address hidden> Thu, 06 Aug 2009 10:02:54 +0000

Changed in procps (Ubuntu):
status: In Progress → Fix Released
tags: added: iso-testing
Changed in procps (Debian):
status: Confirmed → Fix Released
Changed in procps (Debian):
status: Fix Released → Confirmed
Changed in procps (Debian):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.