From: Pavel Machek <pavel@ucw.cz>
To: kernel list <linux-kernel@vger.kernel.org>
Cc: gnomes@lxorguk.ukuu.org.uk, x86@kernel.org, hpa@zytor.com,
mingo@redhat.com, tglx@linutronix.de
Subject: v4.18-rc6 on thinkpad x60: 72000 bogomips?
Date: Fri, 3 Aug 2018 23:47:55 +0200 [thread overview]
Message-ID: <20180803214754.GA9063@amd> (raw)
[-- Attachment #1: Type: text/plain, Size: 567 bytes --]
Hi!
I know bogomips are supposed to be bogus, but 72000 of them? On
Genuine Intel(R) CPU T2400 @ 1.83GHz ? I could live with
1830 bogomips, or maybe 500, or maybe 6000, but 72k is a bit
much. 32-bit kernel.
(And no, it does not break anything AFAICT, but it looks weird.)
4.18.0-rc5 on Intel(R) Core(TM)2 Duo CPU E7400 @ 2.80GHz shows
5599.82 bogomips. 64-bit kernel.
Any ideas?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
reply other threads:[~2018-08-03 21:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180803214754.GA9063@amd \
--to=pavel@ucw.cz \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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