linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: peterz@infradead.org (Peter Zijlstra)
To: linux-arm-kernel@lists.infradead.org
Subject: Tasks schedule/migration issue with CPU hotplug?
Date: Thu, 08 Sep 2011 14:55:48 +0200	[thread overview]
Message-ID: <1315486548.20256.4.camel@twins> (raw)
In-Reply-To: <CAOwKts8pXt6spknNfBV-wy4_KoSp-JaZsdbzOxxWTqu=f6X3Bg@mail.gmail.com>

On Thu, 2011-09-08 at 14:47 +0800, TAO HU wrote:
> > We seems got a schedule/migration issue in a OMAP4430 dual-core system.
> > The kernel base is 2.6.35.7 and we're using CFS.

step 1, try with a kernel that isn't quite as fossilized 
	(3.0 or even better 3.1-rc)
step 2, if no luck, report that
step 3, when sending email, 
     3a, don't wrap machine output
     3b, include .config like things

      parent reply	other threads:[~2011-09-08 12:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-07 14:22 Tasks schedule/migration issue with CPU hotplug? TAO HU
2011-09-08  6:47 ` TAO HU
2011-09-08  7:28   ` Yong Zhang
2011-09-08  7:39     ` Yong Zhang
2011-09-15  2:38       ` TAO HU
2011-09-08 12:55   ` Peter Zijlstra [this message]

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=1315486548.20256.4.camel@twins \
    --to=peterz@infradead.org \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).