Bug#652119: Bad pagetable 000f
On Thu, 22 Dec 2011, Jonathan Nieder wrote:
Can you reproduce this on demand?
Yes. It seems to take about two hours to fail. Thinking about it, par2 was
accessing about 1400 independent areas of memory on a loop, so it would be
causing cache thrash and TLB thrash. I'm thinking it might almost be worth
having a look at the par2 program to see if it could improve its memory
access pattern. But as it stands, it is probably a pretty good TLB
management stress test.
- was this a regression? (I.e., do you know of any older kernel
versions without this bug?)
I have seen this happen before on an older kernel. Not sure exactly which
one - maybe 2.6.26?
- can you reproduce it with a recent kernel from sid or experimental?
(The only packages from outside squeeze you should need in order to
test this aside from the kernel image itself are linux-base and
initramfs-tools.)
I'll have to physically attend the machine to do this, which won't happen
until January. Even then, testing will involve crashing my machine a few
times, so it won't be the first thing I do.
If this is reproducible with newish kernels, we can get help from
upstream. If it isn't, we can try to find what change fixed it and
try applying the same fix to squeeze.
Sure. How out of date is the squeeze kernel anyway?
Matthew
--
People who love sausages, respect the law, and work with IT standards
shouldn't watch any of them being made. -- Peter Gutmann
Reply to: