> > hm, in case this is GCC 2.7.2.3, were you untarring the kernel source on a
> > slightly overclocked box maybe?
>
> The system is not overclocked but after I had sent the message I
> remembered that I had changed the bios settings a little bit. Reversing
> those changes seems to help. But I had several oops with plain 2.1.131
> which were in find_buffer too, so I did not suspect my hardware first
> (Those oops happened even with the slow memory timings).
find_buffer() is typically a good crash-candidate for slightly buggy
hardware (memory), because it goes through a potentially large number of
randomly placed buffer heads with a high frequency. I've also seen it
crash more often in connection with IDE-DMA related bugs, so maybe
running for a while with disabled DMA (hdparm -d0) helps finding the
problem too.
-- mingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/