Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 6626] New: procps Unknown HZ value! (XX) Assume 100.
Date: Tue, 29 Oct 2013 01:51:06 +0000 (UTC)	[thread overview]
Message-ID: <bug-6626-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=6626

           Summary: procps Unknown HZ value! (XX) Assume 100.
           Product: buildroot
           Version: 2013.08
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: minor
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: cassiano at idbinfo.com.br
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Procps suite is goes nuts with my mips64 board. the problem seem harmless, as I
read from the gentoo forums. All binaries included in procps suite show the
same message "Unknown HZ value! (XX) Assume 100.", like top, ps, uptime, et
all.

Attached is a patch from the gentoo, which seems to solve this. it works fine
for x86 and mips64 as I tested.

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2013-10-29  1:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-29  1:51 bugzilla at busybox.net [this message]
2013-10-29  1:51 ` [Buildroot] [Bug 6626] procps Unknown HZ value! (XX) Assume 100 bugzilla at busybox.net
2013-11-13 23:36 ` bugzilla at busybox.net
2013-11-16 12:28 ` bugzilla at busybox.net
2013-11-16 12:28 ` bugzilla at busybox.net
2014-02-07  8:43 ` bugzilla at busybox.net
2014-06-08 20:40 ` bugzilla at busybox.net

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-6626-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox