public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Hockin <thockin@hockin.org>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Andi Kleen <ak@suse.de>, Erick Turnquist <jhujhiti@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Lost Ticks on x86_64
Date: Sun, 7 Aug 2005 14:24:25 -0700	[thread overview]
Message-ID: <20050807212425.GA7926@hockin.org> (raw)
In-Reply-To: <1123440679.12766.5.camel@mindpipe>

On Sun, Aug 07, 2005 at 02:51:19PM -0400, Lee Revell wrote:
> > It's most likely bad SMM code in the BIOS that blocks the CPU too long
> > and is triggered in idle. You can verify that by using idle=poll
> > (not recommended for production, just for testing) and see if it goes away.
> > 
> 
> WTF, since when do *desktops* use SMM?  Are you telling me that we have
> to worry about these stupid ACPI/SMM hardware bugs on the desktop too?

SMM is how BIOSes do legacy support (which stops at OS-handover).  It's
also how some BIOSes do ECC reporting and logging.

We just do pci tweaks to turn it off in the OS.

  parent reply	other threads:[~2005-08-07 21:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5348b8ba050806204453392f7f@mail.gmail.com.suse.lists.linux.kernel>
2005-08-07 11:36 ` Lost Ticks on x86_64 Andi Kleen
2005-08-07 17:07   ` Erick Turnquist
2005-08-07 17:48   ` Tim Hockin
2005-08-07 18:46     ` Erick Turnquist
2005-08-07 20:14       ` Tim Hockin
2005-08-08 12:01     ` Andi Kleen
2005-08-08 16:47       ` Tim Hockin
2005-08-08 16:51         ` Andi Kleen
2005-08-08 18:09       ` Lee Revell
2005-08-07 18:51   ` Lee Revell
2005-08-07 20:04     ` Zwane Mwaikambo
2005-08-07 21:24     ` Tim Hockin [this message]
2005-08-07 14:29 Parag Warudkar
2005-08-07 16:19 ` Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2005-08-07  3:44 Erick Turnquist

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=20050807212425.GA7926@hockin.org \
    --to=thockin@hockin.org \
    --cc=ak@suse.de \
    --cc=jhujhiti@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.com \
    /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