From: Stefan Biereigel <security@biereigel-wb.de>
To: Donald Allen <donaldcallen@gmail.com>
Cc: john stultz <johnstul@us.ibm.com>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: PROBLEM: tickless scheduling
Date: Sun, 16 May 2010 18:14:07 +0200 [thread overview]
Message-ID: <4BF019CF.1030309@biereigel-wb.de> (raw)
In-Reply-To: <AANLkTinBPDY_WVGaq2LUuOzH0niRpgJ4LEpXWkwBxVqh@mail.gmail.com>
> 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.
>
> Hope this helps --
>
> /Don
>
Hello everyone,
I hope I can add something here, because I am experiencing the exact
same Problem as Don describes. I'm running a PackardBell EasyNote MB89
featuring a Core 2 Duo, 4 GB of RAM, Intel Chipset (Santa Rosa), SATA
HDD. My Machine even hangs at boot, absolutely doing nothing until i
wiggle the touchpad. This is definately reproduceable, but I think it
doesn't occur that often in X-Window-System, if X is off I can just wait
a couple of seconds and there I go.
I compiled other kernels myself with tickless disabled and Ticks set to
various values (250, 1000) which completely resolved my problem. If you
want, I can get you some Output/logs/whatever because I'm fixed to using
this kernel ATM (which doesn't really hurt because I use X and son't
shut down my Notebook that often).
Even though I don't know what exact kernel-version this problem brings
(using another machine ATM from vacation) I can say that I existed since
Opensuse 11.1 I guess, so maybe 2.6.30 and above.
Hope I can help --
Stefan
next prev parent reply other threads:[~2010-05-16 16:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 0:18 PROBLEM: tickless scheduling 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 [this message]
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
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=4BF019CF.1030309@biereigel-wb.de \
--to=security@biereigel-wb.de \
--cc=donaldcallen@gmail.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.