linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Boyce <gboyce@rakis.net>
To: Roger Larsson <roger.larsson@norran.net>
Cc: Matthew Dharm <mdharm-kernel@one-eyed-alien.net>,
	<linux-kernel@vger.kernel.org>
Subject: Re: Machines misreporting Bogomips
Date: Thu, 31 Jan 2002 19:11:14 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.42.0201311910170.25129-100000@egg> (raw)
In-Reply-To: <200201312333.g0VNXnZ11421@maile.telia.com>

The machine reporting cache size of 0KB is the one that's behaving
normally.  The misbehaving machine is the one reporting 512K cache.

> > > cache size        : 512 KB
...
> > > bogomips  : 4.06

On Fri, 1 Feb 2002, Roger Larsson wrote:

> On Fridayen den 1 February 2002 00.21, Matthew Dharm wrote:
> > I don't know if this will help much, but I have seen that type of
> > performance drop on systems when the entire cache is disabled.
> >
> > Matt
>
> >From the report below...
> > > cache size	: 0 KB
>
> /RogerL
>
> >
> > On Thu, Jan 31, 2002 at 05:55:57PM -0500, Greg Boyce wrote:
> > > kernel folk,
> > >
> > > I've got a strange issue that I've been struggling to find the solution
> > > to for some time now.
> > >
> > > I work in a group that assists in the managing of large numbers of
> > > deployed linux boxes running variants of the 2.2 kernel on them.  The
> > > machines themselves are all pretty standard.  There are slight variances
> > > on vendors, cpu speeds, etc., but they're all running from the same
> > > motherboards.
> > >
> > > Every once in a while we come across single machines which are running a
> > > lot slower than they should be, and are misreporting their speed in
> > > bogomips under /proc/cpuinfo.  Reinstalling the OS and changing versions
> > > of the kernel don't appear to affect the machines themselves at all.
> > >
> > > I was wondering if anyone would be able to provide me with a starting
> > > point to hunt this down.  The only solution we had found in the past was
> > > to replace the machines, but some of them are located out of the country
> > > and that would be expensive.
> > >
> > > Here is the output from /proc/cpuinfo for machines.  The first machine is
> > > normal, the second is affected by this bug.  They're both running the
> > > same hardware, although the first machine's CPU is 650mhz instead of
> > > 500mhz.
> > >
> > > Machine 1:
> > > processor	: 0
> > > vendor_id	: GenuineIntel
> > > cpu family	: 6
> > > model		: 8
> > > model name	: Pentium III (Coppermine)
> > > stepping	: 3
> > > cpu MHz		: 645.676332
> > > cache size	: 0 KB
> > > fdiv_bug	: no
> > > hlt_bug		: no
> > > sep_bug		: no
> > > f00f_bug	: no
> > > coma_bug	: no
> > > fpu		: yes
> > > fpu_exception	: yes
> > > cpuid level	: 3
> > > wp		: yes
> > > flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
> > > cmov pat pse36 psn mmx osfxsr kni
> > > bogomips	: 643.89
> > >
> > > Machine 2:
> > > processor	: 0
> > > vendor_id	: GenuineIntel
> > > cpu family	: 6
> > > model		: 7
> > > model name	: Pentium III (Katmai)
> > > stepping	: 3
> > > cpu MHz		: 496.677416
> > > cache size	: 512 KB
> > > fdiv_bug	: no
> > > hlt_bug		: no
> > > sep_bug		: no
> > > f00f_bug	: no
> > > coma_bug	: no
> > > fpu		: yes
> > > fpu_exception	: yes
> > > cpuid level	: 2
> > > wp		: yes
> > > flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
> > > cmov pat pse36 mmx osfxsr kni
> > > bogomips	: 4.06
> > >
> > > Let me know if there's anything else I can provide to help with the
> > > diagnosis.  The machine itself is an IBM Netfinity 4000R.
> > >
> > > --
> > > Gregory Boyce
> > >
> > >
> > > -
> > > To unsubscribe from this list: send the line "unsubscribe linux-kernel"
> > > in the body of a message to majordomo@vger.kernel.org
> > > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > > Please read the FAQ at  http://www.tux.org/lkml/
>
> --
> Roger Larsson
> Skellefteå
> Sweden
>


  reply	other threads:[~2002-02-01  0:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-31 22:55 Machines misreporting Bogomips Greg Boyce
2002-01-31 23:21 ` Matthew Dharm
2002-01-31 23:30   ` Roger Larsson
2002-02-01  0:11     ` Greg Boyce [this message]
2002-02-01  9:59 ` Horst von Brand
2002-02-01 17:11   ` Greg Boyce
2002-02-01 12:59     ` gmack
2002-02-01 20:53       ` Greg Boyce
2002-02-01 23:41         ` Alan Cox
2002-02-01 23:34           ` Greg Boyce
2002-02-01 23:59             ` Alan Cox
2002-02-03 22:05             ` Juhan Ernits
2002-02-03  7:39   ` watermodem
2002-02-08 17:13 ` Andrew Scott
     [not found] <no.id>
2002-02-03 21:40 ` Barry K. Nathan

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=Pine.LNX.4.42.0201311910170.25129-100000@egg \
    --to=gboyce@rakis.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mdharm-kernel@one-eyed-alien.net \
    --cc=roger.larsson@norran.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;
as well as URLs for NNTP newsgroup(s).