All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockrwd@gmail.com>
To: Donald Allen <donaldcallen@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: tickless scheduling
Date: Mon, 10 May 2010 18:27:35 -0600	[thread overview]
Message-ID: <4BE8A477.9080703@gmail.com> (raw)
In-Reply-To: <AANLkTin6D2GP0yJJbPYGH1AcAM9-g219rAxSyW_ZlrXV@mail.gmail.com>

On 05/10/2010 06:18 PM, Donald Allen wrote:
> 1. Network file transfers and fscks stop on Toshiba netbook unless
> system receives external events
> 2. I have a new Toshiba NB305 on which I installed the beta release of
> Slackware 13.1, which provides a 2.6.33.3 kernel with the tickless
> option enabled. With this machine on my ethernet, I attempted to rsync
> my home directory to it, about 9 Gb, from a workstation that is my
> primary system (running Slackware 13). The transfer proceeded normally
> for awhile and then stopped, which I could see in the xterm on the
> workstation. I went to the netbook to see what was going on there and
> when I began typing, the transfer resumed. I ran 'top' on the netbook
> and it would freeze after a few updates, coinciding with the file
> transfer pausing again. Typing would get things moving. At another
> point, I tested pm-suspend on the netbook. Suspending worked, but
> awakening did not, so I had to power-cycle the machine. I use ext2 for
> reasons which I won't attempt to justify here, so when the machine
> came back up, it fsck'ed the root filesystem. Here again I saw things
> grind to a halt -- the progress meter stopped and the there was no
> disk activity. But if I moved my finger on the touchpad, things would
> get moving again. The only way to get the fsck to complete was to
> constantly be tickling the touchpad. I corresponded with Patrick
> Volkerding, telling him I suspected a scheduling problem and he
> informed me that the 13.1 kernel had tickless enabled, unlike 13. So I
> built a 2.6.33.3 kernel (from the Slackware-supplied kernel sources)
> with tickless disabled. With that kernel running, I power-cycled the
> machine to force a fsck of the root filesystem. This one proceeded to
> completion normally -- no external stimuli needed.
> 3. Tickless, scheduler
> 4. 2.6.33.3
> 7.1 ver_linux output attached
> 7.2 /proc/cpuinfo attached
> 7.3 /proc/modules attached
> 7.4 /proc/ioports, /proc/iomem attached
> 7.5 lspci attached
> 7.6 /proc/scsi/scsi attached

Can you post dmesg output from bootup?

  reply	other threads:[~2010-05-11  0:27 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 [this message]
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
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=4BE8A477.9080703@gmail.com \
    --to=hancockrwd@gmail.com \
    --cc=donaldcallen@gmail.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 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.