Re: 2.6.18-rc1-mm1

From: Michal Piotrowski
Date: Mon Jul 10 2006 - 06:00:37 EST


On 10/07/06, Ingo Molnar <mingo@xxxxxxx> wrote:

* Michal Piotrowski <michal.k.k.piotrowski@xxxxxxxxx> wrote:

> >> rofl. You broke lockdep.
> >
> >ouch! the lock identifications look quite funny :-| Never saw that
> >happen before,
>
> :)
>
> >i'm wondering what's going on. Michal, did this happen
> >straight during bootup? Or did you remove/recompile/reinsert any modules
> >perhaps?
>
> It's happening while /etc/init.d/cpuspeed execution.
>
> I forgot about "make O=/dir/ clean". When new -mm is out I always
> remove kernel directory and create new one.

ah, ok. So i'll put this under the 'unclean-build artifact' section,
i.e. not a lockdep bug for now, it seems. Please re-report if it ever
occurs again with a clean kernel build.

Unfortunately "make O=/dir clean" doesn't help. I'll disable lockdep,
and see what happens.


Ingo


Regards,
Michal

--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/wiki/)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/