From: Peter Seiderer <ps.report@gmx.net>
To: Steve <sleepy_dog@gmx.de>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] htop - "No btime in /proc/stat: Success"
Date: Wed, 20 Oct 2021 20:10:53 +0200 [thread overview]
Message-ID: <20211020201053.0a88c199@gmx.net> (raw)
In-Reply-To: <trinity-37320d19-a174-46c4-9f92-823a8454c4d5-1634734547955@3c-app-gmx-bap28>
Hello Steve, Arnout,
On Wed, 20 Oct 2021 14:55:47 +0200, Steve <sleepy_dog@gmx.de> wrote:
>
> > I don't understand how btime can be 0 though. Is the uptime (in /proc/uptime) also 0?
Most Raspberry Pi's are delivered without RTC and /proc/stat btime is set to
'...the time read off the RTC. This is represented in Unix time (aka POSIX time
or Epoch time).' (see [1]) and so will always be '0' (until you change the
date per cmdline or ntp)...
The htop misleading error message is fixed upstream by [2] and the current version
used on buildroot git master (htop-3.1.1) already contains the fix...
Regards,
Peter
[1] https://support.cumulusnetworks.com/hc/en-us/articles/204364887-Error-Message-Seen-missing-btime-in-proc-stat-
[2] https://github.com/htop-dev/htop/commit/7433bf4b18278080fb2ac22c5828490883066570
>
> No, it's now "11014.58 22892.09"
>
> Von: "Arnout Vandecappelle" <arnout@mind.be>
>
> On 20/10/2021 14:29, Steve wrote:
> > > Is /proc mounted?
> > if "mount" outputting a line, among others, saying "proc on /proc type proc
> > (rw,relatime)" means that, then yes
> >
> > > What is the contents of /proc/stat?
> >
> > # cat /proc/stat
> > cpu 75 0 917 3631474 47 0 4 0 0 0
> > cpu0 26 0 336 907872 1 0 2 0 0 0
> > cpu1 23 0 536 907241 17 0 0 0 0 0
> > cpu2 19 0 22 908242 7 0 0 0 0 0
> > cpu3 7 0 23 908117 21 0 2 0 0 0
> > intr 123556 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 169 2275 0 3 0 0 0 0 0 0 0 0 0
> > 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 60 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 644 0 0 0 0
> > 0 0 0 0 553 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
> > 0 0 0 257 45046 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
> > 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
> > 0 0 0 0 0 0 0 0 74548 0 0 0
> > ctxt 184781
> > btime 0
>
> Ah, so btime is there, but it's zero, and htop apparently doesn't like that.
>
> I don't understand how btime can be 0 though. Is the uptime (in /proc/uptime)
> also 0?
>
>
> Regards,
> Arnout
>
>
> > processes 184
> > procs_running 1
> > procs_blocked 0
> > softirq 156657 0 70619 33 535 553 0 10351 72206 0 2360
> > *Von:* "Arnout Vandecappelle" <arnout@mind.be>
> >
> > On 20/10/2021 13:22, Steve wrote:
> > > Hello,
> > > a Linux image built with a recently downloaded buildroot, starting with the
> > > defconfig for RaspberryPi3 and adding some things (htop if it wasn't already,
> > > nano, openssh, openvpn; also the linux-menuconfig was altered, concerning USB
> > > driver stuff).
> > >
> > > When, in menuconfig, I search with / for htop, it shows that htop and all
> > > dependencies are met (all positive dependencies are [=y] and the one negative
> > > (static libs) is [=n].
> > > But when I call htop on the running system, I only get the line given in the
> > topic.
> > > What could be the problem?
> >
> > This is squarely in the "this shouldn't happen" domain...
> >
> > Is /proc mounted?
> >
> > What is the contents of /proc/stat?
> >
> >
> > Regards,
> > Arnout
> >
> > _______________________________________________
> > buildroot mailing list
> > buildroot@buildroot.org
> > https://lists.buildroot.org/mailman/listinfo/buildroot
> > <https://lists.buildroot.org/mailman/listinfo/buildroot>
> >
> > _______________________________________________
> > buildroot mailing list
> > buildroot@buildroot.org
> > https://lists.buildroot.org/mailman/listinfo/buildroot
> >
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
>
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2021-10-20 18:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 11:22 [Buildroot] htop - "No btime in /proc/stat: Success" Steve
2021-10-20 11:54 ` Arnout Vandecappelle
[not found] ` <trinity-925a029f-87a5-4638-b533-9c4c46e363cc-1634732988358@3c-app-gmx-bap28>
2021-10-20 12:40 ` Arnout Vandecappelle
2021-10-20 12:55 ` Steve
2021-10-20 18:10 ` Peter Seiderer [this message]
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=20211020201053.0a88c199@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@buildroot.org \
--cc=sleepy_dog@gmx.de \
/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