linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Donald Allen <donaldcallen@gmail.com>
Cc: linux-kernel@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: PROBLEM: tickless scheduling
Date: Wed, 12 May 2010 13:52:03 -0700	[thread overview]
Message-ID: <1273697523.2856.3.camel@localhost.localdomain> (raw)
In-Reply-To: <AANLkTilb_CGBolyv5Ps9VuhNxFZKtjck4om4G21ICaif@mail.gmail.com>

On Wed, 2010-05-12 at 15:54 -0400, Donald Allen wrote:
> Before doing what you asked, I ran my home-brew backup script, which
> tars up the whole machine, save my home directory, to a big sata drive
> in a usb shoebox. I did so by booting the most recent Arch Linux
> install/live CD (while I use Slackware, the Slackware install CDs are
> not suitable for this sort of thing, having very old versions of
> things like tar). While doing so, I observed exactly the same symptoms
> I did with the Slackware 13.1 install, which I described in the bug
> report. So rather than messing with the hard-won custom kernel that I
> now have installed on the netbook, I am attaching the various things
> from /proc gathered with the Arch kernel running. Yes, it's a somewhat
> older kernel (2.6.30), but I'm hoping that things haven't changed much
> in tickless land. If that's not the case, then I will attempt to
> reproduce this with the newer kernel on the Slackware 13.1 install
> DVD. Let me know if you need me to do this. The attached tar file is
> bzip2-compressed, so you want xjf to extract.

Hmm.. Sorry, but I have another quick request. Could you send
your /proc/interrupts output from the kernel having the problem?

thanks
-john



  reply	other threads:[~2010-05-12 20:52 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 [this message]
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=1273697523.2856.3.camel@localhost.localdomain \
    --to=johnstul@us.ibm.com \
    --cc=donaldcallen@gmail.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 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).