The last update of the "Squeeze" kernel has not altered anything. The
problem still exists.
Tilo Hacke
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1295289769.
Hello !
> We definitely want to robustify scheduler init code to not crash and to (if
> possible) print a warning about the borkage.
I just tested the last 2.6.32-5 update and it still crashes in the same
manner.
Best regards
Tilo Hacke
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lis
On Mon, 2010-11-29 at 12:50 +0100, Peter Zijlstra wrote:
> On Sun, 2010-11-28 at 20:14 +, 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
Hi !
> The error message about 'domain->cpu_power' does not refer to power
> management, but to the scheduler's estimation of the processing power of
> each group of processor threads.
>
> The scheduler is trying to group the processor threads by:
>
> - NUMA node (NODE; sharing a connection to R
Hi !
> This shows something about what's going wrong. Could you please try
> adding 'debug' to the kernel parameters? That will show some more
> context for these errors.
I booted 2.6.32-5 with the debug option on, and for comparison did the
same with 2.6.30-2.
The errors concerning the power
5 matches
Mail list logo
