mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Pekka Enberg" <penberg@cs.helsinki.fi>
To: "Neil Romig" <neil@romig.demon.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: File corruption when using kernels 2.6.18+
Date: Sun, 30 Sep 2007 19:29:35 +0300	[thread overview]
Message-ID: <84144f020709300929t6aafd98at23d810d4460e898a@mail.gmail.com> (raw)
In-Reply-To: <46FFC371.9040805@romig.demon.co.uk>

Hi Neil,

On 9/30/07, Neil Romig <neil@romig.demon.co.uk> 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

  reply	other threads:[~2007-09-30 16:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-30 15:40 Neil Romig
2007-09-30 16:29 ` Pekka Enberg [this message]
2007-10-02 21:05   ` Neil Romig
2007-10-03  5:18     ` Pekka Enberg
2007-10-03 18:42       ` Neil Romig
2007-10-03 18:48         ` Pekka Enberg
2007-10-03 19:22           ` Linus Torvalds
2007-10-03 19:35             ` Pekka Enberg
2007-10-03 19:54               ` Linus Torvalds
2007-10-04  1:11                 ` Hiro Yoshioka
2007-10-03 20:30               ` Alan Cox
2007-10-04 18:34                 ` Neil Romig
2007-10-02 22:30 ` Chuck Ebbert
     [not found] <fa.VCoGTwbB+qeNlkBJ24MiuXcGSRA@ifi.uio.no>
     [not found] ` <fa.R+FhT6IGmV/dDweUt/MdSeA5YbQ@ifi.uio.no>
     [not found]   ` <fa.7MxTIt/ik0uRFN/lMWUasYV/JyE@ifi.uio.no>
     [not found]     ` <fa.YJ4uCPzXT5TQElSosyz98cpuMSc@ifi.uio.no>
     [not found]       ` <fa.Tp9UUX9EYprQyLg0shgH1YG9DDM@ifi.uio.no>
     [not found]         ` <fa.PzpJEEoLXfC+eOQZjTWjdf9vdnE@ifi.uio.no>
2007-10-04  2:59           ` Robert Hancock
2007-10-04  3:39             ` Linus Torvalds

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=84144f020709300929t6aafd98at23d810d4460e898a@mail.gmail.com \
    --to=penberg@cs.helsinki.fi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neil@romig.demon.co.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®