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 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? The 2.6.32.y series stabilized for about a year and a couple of months before squeeze was released. (v2.6.33 was released on 24 February 2010.) Since then, the 2.6.32.y kernel has received lots of fixes, so in that sense it is up to date. Upstream developers prefer to debug something closer to the codebase they are working on day-to-day. [...] > 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 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 this is likely to be a hardware bug or a kernel bug. Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
