mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Donald Allen <donaldcallen@gmail.com>
Cc: john stultz <johnstul@us.ibm.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Arjan van de Ven <arjan@infradead.org>
Subject: Re: PROBLEM: tickless scheduling
Date: Mon, 17 May 2010 01:36:06 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.00.1005170123090.3368@localhost.localdomain> (raw)
In-Reply-To: <AANLkTinBPDY_WVGaq2LUuOzH0niRpgJ4LEpXWkwBxVqh@mail.gmail.com>

Donald,

On Sat, 15 May 2010, Donald Allen wrote:
> Attached. This is from the 2.6.30 kernel on the Arch Linux install cd.
> 
> Here's another bit of data. As I've said previously, the problems I'm
> reporting were observed on a Toshiba NB310-305 netbook with a
> single-core Atom 450 processor. I just built myself a mini-ITX system
> using the Intel D510MO motherboard, which provides a dual-core D510
> Atom processor. The other hardware on the board is similar to the
> Toshiba. I installed the same Slackware snapshot I used on the
> Toshiba, and did the home directory transfer without any problem at
> all with the default tickless kernel. The hardware isn't identical,
> and while I don't know the internals of the Linux kernel at all, my
> gut, backed up by many years of OS development work in scheduling and
> memory management, is telling me that the key difference is dual- vs.
> single-core. Just a guess.

I fear you are wrong. 

The key difference is almost certainly that the BIOS of your netbook
tries to be overly clever vs. power management and is not aware of the
fact that the Linux kernel uses timer hardware in a very different way
than the other OS which comes preinstalled on that machine. 

The overly clever BIOS power management which works nicely with the
vendor provided "drivers" for the other OS is just interfering with
the kernels way of dealing with the problem.

Can you please boot with "hpet=disable" on the kernel command line ?

Thanks,

	tglx

  parent reply	other threads:[~2010-05-16 23:36 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-11  0:18 Donald Allen
2010-05-11  0:27 ` Robert Hancock
2010-05-11  0:34   ` Donald Allen
2010-05-11  0:38     ` Robert Hancock
2010-05-11  0:53       ` Donald Allen
2010-05-11  0:54 ` john stultz
2010-05-11  0:59   ` Donald Allen
2010-05-11  1:12     ` john stultz
2010-05-11  1:52       ` Donald Allen
2010-05-12 19:54         ` Donald Allen
2010-05-12 20:52           ` john stultz
2010-05-15 17:11             ` Donald Allen
2010-05-16 16:14               ` Stefan Biereigel
2010-05-16 20:41                 ` Arjan van de Ven
2010-05-17 15:26                 ` Donald Allen
2010-05-17 16:15                   ` Stefan Biereigel
2010-05-16 23:36               ` Thomas Gleixner [this message]
2010-05-17 13:44                 ` Donald Allen
2010-05-17 14:02                   ` Donald Allen
2010-05-17 14:04                   ` Arjan van de Ven
2010-05-17 14:11                     ` Donald Allen
2010-05-17 14:29                       ` Arjan van de Ven
2010-05-17 14:45                         ` Donald Allen

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=alpine.LFD.2.00.1005170123090.3368@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=arjan@infradead.org \
    --cc=donaldcallen@gmail.com \
    --cc=johnstul@us.ibm.com \
    --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®