From: Neil Romig <neil@romig.demon.co.uk>
To: linux-kernel@vger.kernel.org
Subject: File corruption when using kernels 2.6.18+
Date: Sun, 30 Sep 2007 16:40:33 +0100 [thread overview]
Message-ID: <46FFC371.9040805@romig.demon.co.uk> (raw)
I am using kernel 2.6.17.14, and would like to use newer versions for the wireless code but I get file corruption with any kernel
more recent than this. My system uses a SiS645DX chipset (it is a rebadged CLEVO D400E) with 5513 IDE.
I get this corruption with read/writes, i.e using "cp", "dd", when compiling software, writing to CD, etc etc. An example:
cp ../Changelog-2.6.18 .
diff Changelog-2.6.18 ../Changelog-2.6.18
16377c16377
< LD .top_vmlinux1
---
> LD .tmp_vmlinux1
23954c23954
< Date: Mon Jul 1% 04:45:11 2006 -0700
---
> Date: Mon Jul 10 04:45:11 2006 -0700
24955c24955
< This is generally useful, but partacularly helps see if it is the same sector
---
> This is generally useful, but particularly helps see if it is the same sector
31879c31879
< [MMC] sdhci: version bump cdhci
---
> [MMC] sdhci: version bump sdhci
42955c42955
< Replace `he temp makefile hacks with proper CONFIG entries, which are also
---
> Replace the temp makefile hacks with proper CONFIG entries, which are also
49050c49050
< and this task is(already holding:
---
> and this task is already holding:
[output clipped]
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 have tried some obvious things (see thread on linuxquestions.org:
http://www.linuxquestions.org/questions/showthread.php?t=578200), but I don't understand enough about the kernel to get any further.
Neil.
next reply other threads:[~2007-09-30 15:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-30 15:40 Neil Romig [this message]
2007-09-30 16:29 ` File corruption when using kernels 2.6.18+ Pekka Enberg
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=46FFC371.9040805@romig.demon.co.uk \
--to=neil@romig.demon.co.uk \
--cc=linux-kernel@vger.kernel.org \
/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