From: Diego Calleja <diegocg@gmail.com>
To: linux-acpi@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: CONFIG_ACPI_PROCESSOR=y confuses the cpu scheduler
Date: Sun, 22 Jan 2006 20:16:06 +0100 [thread overview]
Message-ID: <20060122201606.5d335156.diegocg@gmail.com> (raw)
In-Reply-To: <20060119012040.733335f4.diegocg@gmail.com>
El Thu, 19 Jan 2006 01:20:40 +0100,
Diego Calleja <diegocg@gmail.com> escribió:
> If I compile CONFIG_ACPI_PROCESSOR in the kernel, one of the two cpus
> doesn't get scheduled any process. The CPU works and everything, it
> services interrupts and I can force processes to run on that CPU
> with taskset, but they won't get scheduled in that CPU no matter
> how much processes and load you put on the machine.
This has been reported by another person who found the culprit
commit: http://bugzilla.kernel.org/show_bug.cgi?id=5930
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2006-01-22 20:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 0:20 CONFIG_ACPI_PROCESSOR=y confuses the cpu scheduler Diego Calleja
2006-01-22 19:16 ` Diego Calleja [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=20060122201606.5d335156.diegocg@gmail.com \
--to=diegocg@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--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