Cyrill Gorcunov wrote: > [Udo van den Heuvel - Sat, Dec 01, 2007 at 12:00:53PM +0100] > | I only had teh bug once, that was the reason for my post. > | Since then the system has been busy, with intervals, doing kernel > | compiles and no repeat of the BUG yet... > | It's a VIA EN12000 with 1GB of RAM. How could I increase the chances of > | hitting it? > > if my guessing is right - the only chance to hit it faster - is to increase > files' activity i.e. compiling the kernel involves a lot of file being readed > thru dcache system. First we have to locate the bug on a pure kernel > and 'case it's a rare thing to happen... well I don't really know how to > get it up to known point. So i think you could play with a pure kernel > by compiling it or run several copies of 'grep' thru kernel searching > the same pattern like "grep -r -n for ./*" in kernel sources. But Udo, > I'm not a kernel specialist so my suggestions could be not really usefull ;)
Ok, maybe someone else can improve on this: I now have 12 screen'ed sessions running in /usr/src/linux with: while true; do grep -r -n for ./*; done Every now and then I can check dmesg. Would that be enough? Udo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/