From: Jurriaan <thunder7@xs4all.nl>
To: Christoph Pohl <christoph.pohl@inf.tu-dresden.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Low bogomips on IBM x445 (kernel 2.6.5)
Date: Wed, 28 Apr 2004 12:28:27 +0200 [thread overview]
Message-ID: <20040428102827.GB14817@middle.of.nowhere> (raw)
In-Reply-To: <408F4632.2090705@inf.tu-dresden.de>
From: Christoph Pohl <christoph.pohl@inf.tu-dresden.de>
Date: Wed, Apr 28, 2004 at 07:50:42AM +0200
> >cat /proc/mtrr
>
> reg00: base=0x00000000 ( 0MB), size=2048MB: write-back, count=1
> reg01: base=0x80000000 (2048MB), size=1024MB: write-back, count=1
> reg02: base=0xc0000000 (3072MB), size= 512MB: write-back, count=1
> reg03: base=0xe0000000 (3584MB), size= 256MB: write-back, count=1
> reg04: base=0x100000000 (4096MB), size=4096MB: write-back, count=1
> reg05: base=0x200000000 (8192MB), size=8192MB: write-back, count=1
> memory:
> 8192MB (8GB), plus 2GB swap space.
> Does memory size somehow affect bogomips calculation?
>
> There are however some noteworthy lines in syslog during reboot:
> (...)
> Apr 26 14:25:40 x445 kernel: Using local APIC timer interrupts.
> Apr 26 14:25:40 x445 kernel: calibrating APIC timer ...
> Apr 26 14:25:40 x445 kernel: ..... CPU clock speed is 2993.0654 MHz.
> Apr 26 14:25:40 x445 kernel: ..... host bus clock speed is 99.0788 MHz.
> Apr 26 14:25:40 x445 kernel: checking TSC synchronization across 8 CPUs:
> Apr 26 14:25:40 x445 kernel: BIOS BUG: CPU#0 improperly initialized, has
> 7358270 usecs TSC skew! FIXED.
> Apr 26 14:25:40 x445 kernel: BIOS BUG: CPU#1 improperly initialized, has
> 7358270 usecs TSC skew! FIXED.
> Apr 26 14:25:40 x445 kernel: BIOS BUG: CPU#2 improperly initialized, has
> -7358271 usecs TSC skew! FIXED.
> Apr 26 14:25:40 x445 kernel: BIOS BUG: CPU#3 improperly initialized, has
> -7358271 usecs TSC skew! FIXED.
> Apr 26 14:25:40 x445 kernel: BIOS BUG: CPU#4 improperly initialized, has
> 7358271 usecs TSC skew! FIXED.
> Apr 26 14:25:40 x445 kernel: BIOS BUG: CPU#5 improperly initialized, has
> 7358270 usecs TSC skew! FIXED.
> Apr 26 14:25:40 x445 kernel: BIOS BUG: CPU#6 improperly initialized, has
> -7358269 usecs TSC skew! FIXED.
> Apr 26 14:25:40 x445 kernel: BIOS BUG: CPU#7 improperly initialized, has
> -7358271 usecs TSC skew! FIXED.
> Apr 26 14:25:40 x445 kernel: Brought up 8 CPUs
> (...)
>
> I don't know if that's any help.
I recall some earlier messages where some crucial part of memory was
marked 'non-cacheable' in /proc/mtrr, and linux ran very slow. But on
re-reading, your problem is more that linux isn't slow, but bogomips
(and only bogomips) don't seem right?
In that case, you may need the help of a real kernel hacker, not a
piddling amateur like me :-)
Good luck,
Jurriaan
--
Nothing is a waste of time if you use the experience wisely.
Rodin
Debian (Unstable) GNU/Linux 2.6.6-rc2-mm2 2x6062 bogomips 0.07 0.02
next prev parent reply other threads:[~2004-04-28 10:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-27 11:01 Christoph Pohl
2004-04-27 18:01 ` Jurriaan
2004-04-28 5:50 ` Christoph Pohl
2004-04-28 10:28 ` Jurriaan [this message]
2004-04-28 20:36 ` john stultz
2004-04-28 21:11 ` Chris Friesen
2004-04-28 21:33 ` john stultz
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=20040428102827.GB14817@middle.of.nowhere \
--to=thunder7@xs4all.nl \
--cc=christoph.pohl@inf.tu-dresden.de \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®