On Fri, 2 Dec 2005, Ryan Richter wrote: > On Thu, Dec 01, 2005 at 08:21:57PM +0000, Hugh Dickins wrote: > > If the problem were easily reproducible, it'd be great if you could > > try this patch; but I think you've said it's not :-( > > I can throw this in and test it for sure. I'll run the backups every > day for a while to speed up the testing also. Thanks - though everyone seems to have agreed that the patch is needed whatever: so although it would be interesting to know if it has fixed your problem, we're not waiting on you to go forward with it (James already invited Linus to pull). > Could someone please tell me exactly which patches I should include in > the kernel I will boot tomorrow? You hit the problem with 2.6.14.2. My own opinion would be to apply just that patch to that release, or to 2.6.14.3 if you prefer. Linus was suggesting 2.6.15-rc4 because there's some debug there which might have helped identify the offending driver: but your backtrace had already showed us the offending driver. Well, not proven: if a page is doubly freed, the one that suffers is not necessarily the one that's guilty; but it's a reasonable expectation. I don't think his debug would tell us anything more. > I haven't played with -rc for ages, so > I'm no longer sure which kernel I should start with (2.6.14 or > 2.6.14.3?). If you do want 2.6.15-rc4, then it's 2.6.14 + patch-2.6.15-rc4. > Are the MPT-fusion performance fix patches in -rc4, or if > not will they still apply? I don't know it myself. Is that the one about the module performing much better than the builtin? I'd expect that to be in. If you have it, suggest you look at your 2.6.15-rc4 source to see if it's there. Hugh - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
