Hi Neil, On 9/30/07, Neil Romig <[EMAIL PROTECTED]> wrote: > I would suspect a memory problem but memtest86+ gives no errors despite > numerous > passes, and I get no errors in older kernels. Does anyone have any idea what > changed in > 2.6.18 to cause such an error?
I don't but you can try to isolate the changeset introducing the corruption with git-bisect: http://kernel.org/pub/software/scm/git/docs/v1.3.3/howto/isolate-bugs-with-bisect.txt So, in your case, you do: <clone Linux mainline git repository> # git bisect start # git bisect bad v2.6.18 # git bisect good v2.6.17 then <recompile and test> <git bisect [good|bad] depending on results> <repeat until you've narrowed down the changeset> Also, please remember to send your .config when reporting bugs as described in REPORTING-BUGS. Pekka - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
