lkml.org 
[lkml]   [2006]   [Jul]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 2.6.18-rc1-mm1
On 10/07/06, Ingo Molnar <mingo@elte.hu> wrote:
>
> * Michal Piotrowski <michal.k.k.piotrowski@gmail.com> 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@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-07-10 12:05    [W:0.102 / U:0.012 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site