Re: File corruption when using kernels 2.6.18+

Hi Neil,

On 9/30/07, Neil Romig <neil@xxxxxxxxxxxxxxxxx> 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 majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: 2.6.22-ck1
    ... and thanks for all the fish ... changeset: 73:75c3084835f6 ... it's been at least 73 patches i kept track of in a mercurial ... kernels. ...
    (Linux-Kernel)
  • Re: nmi_watchdog=2 regression in 2.6.21
    ... does the same thing (watchdog stuck after check) happen with ... ie. those before Stephane's changeset that made it use ... PERFCTR1? ... In older kernels it's very slow, ...
    (Linux-Kernel)