Bug#652119: Bad pagetable 000f

2012-01-09 Thread Jonathan Nieder
Matthew Wakeling wrote: > Thanks. I tried GhostBSD, which didn't have par2 included and > couldn't run executables from my hard drive, and Knoppix which was > an i386 kernel (albeit very recent 3.0.something), so also couldn't > run my amd64 par2 from my hard drive. A rescue environment may be > t

Bug#652119: Bad pagetable 000f

2012-01-08 Thread Matthew Wakeling
On Sun, 8 Jan 2012, Jonathan Nieder wrote: Could you point me in the direction of such a livecd please? It looks like no one is making an official Debian livecd with kFreeBSD any more (alas). But it should be possible to grab par2 and its dependencies and run them in the debian-installer[1] re

Bug#652119: Bad pagetable 000f

2012-01-08 Thread Jonathan Nieder
Hi Matthew, Matthew Wakeling wrote: > On Thu, 22 Dec 2011, Jonathan Nieder wrote: >> Other tests that would be useful might include >> (1) running memtest86+ and (2) trying the same workload using a livecd >> with some other kernel, like the kernel of FreeBSD, to see if

Bug#652119: Bad pagetable 000f

2012-01-08 Thread Matthew Wakeling
On Thu, 22 Dec 2011, Jonathan Nieder wrote: 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. No problem; we can wait. Other tests that would be useful m

Bug#652119: Bad pagetable 000f

2011-12-22 Thread Jonathan Nieder
Matthew Wakeling wrote: > On Thu, 22 Dec 2011, Jonathan Nieder wrote: >> - 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? Thanks. [...] >> If this

Bug#652119: Bad pagetable 000f

2011-12-22 Thread Matthew Wakeling
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

Bug#652119: Bad pagetable 000f

2011-12-22 Thread Jonathan Nieder
Hey Matthew, Matthew Wakeling wrote: > Running the par2 program causes a bad pagetable fault which has > killed the process and killed the machine on two different > occasions. The machine is completely stable running other programs. > > The problem occurs when running par2 to generate 13.5GB of