Re: 2.6.18-rc1-mm1

[Ingo Molnar]

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

> On 10/07/06, Michal Piotrowski <michal.k.k.piotrowski@xxxxxxxxx> wrote:
> >On 10/07/06, Ingo Molnar <mingo@xxxxxxx> wrote:
> >> 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.
> >
>
> When I set DEBUG_LOCK_ALLOC=n and CONFIG_PROVE_LOCKING=n everything is 
> ok. It maybe a gcc 4.2 bug.

well ... if you disable lockdep then you wont get lockdep messages - 
that's normal. Or did i miss what the bug is about?

	Ingo
-
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/