From: Frede Feuerstein <Frede_Feuerstein@gmx.net>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ben Hutchings <benh@debian.org>, Ingo Molnar <mingo@elte.hu>,
603229@bugs.debian.org, LKML <linux-kernel@vger.kernel.org>,
Tejun Heo <tj@kernel.org>
Subject: Re: Scheduler grouping failure; division by zero in select_task_rq_fair
Date: Mon, 29 Nov 2010 14:58:13 +0100 [thread overview]
Message-ID: <1291039093.26937.9.camel@localhost> (raw)
In-Reply-To: <1291031425.32004.16.camel@laptop>
On Mon, 2010-11-29 at 12:50 +0100, Peter Zijlstra wrote:
> On Sun, 2010-11-28 at 20:14 +0000, Ben Hutchings wrote:
>
> > [ 0.856002] Pid: 2, comm: kthreadd Not tainted 2.6.32-5-amd64 #1 W1100z/2100z
>
> What's in that kernel? is that simply the latest .32-stable?
It was the latest stable .32 contained in the official "squeeze".
Today a new one arrived. I shall try that tomorrow on today late night,
since i cannot reset the mill right now.
Additional remark:
When i said, that the cores contained in each chip do not share any
resources, i forgot about the clock source:
The clock is set globally for each whole chip, i.e. CPU0 and CPU1 are
always running on the same clock, as well as CPU2 and CPU3 do.
Best regards
Tilo Hacke
next prev parent reply other threads:[~2010-11-29 13:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1290449310.3868.13.camel@localhost>
[not found] ` <1290470134.6770.929.camel@localhost>
[not found] ` <1290514638.3892.16.camel@localhost>
[not found] ` <1290900814.3292.84.camel@localhost>
[not found] ` <1290920436.4255.1025.camel@localhost>
2010-11-28 20:14 ` Scheduler grouping failure; division by zero in select_task_rq_fair Ben Hutchings
2010-11-29 11:50 ` Peter Zijlstra
2010-11-29 13:58 ` Frede Feuerstein [this message]
2010-11-29 16:26 ` Ben Hutchings
2010-11-29 18:06 ` Ingo Molnar
2010-12-14 10:07 ` Frede Feuerstein
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=1291039093.26937.9.camel@localhost \
--to=frede_feuerstein@gmx.net \
--cc=603229@bugs.debian.org \
--cc=benh@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tj@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